Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on What is "clutter" in the context of Codidact?

Parent

What is "clutter" in the context of Codidact?

+4
−0

It's common to hear comments about QA sites being "cluttered", "clogged", "spammed" etc. with types of questions that the commenter doesn't want.

What does this actually mean? Is there a definition of "clutter"?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+2
−1

I think of clutter primarily in terms of how it impacts community norms.

If your programming language Q&A site has an about page that says, ‘We welcome questions about all programming languages,’ but out of the last 100 questions, 97 of them were about SQL, you have a de facto SQL Q&A site. For a new user with a Julia question, do you think they're going to look at the about page first, conclude that this is a site where their Julia question is likely to get a good response, and ask it? Do you think they'll quickly reach for the tags feature to hide all the SQL-related questions and use that view to form their opinion of the site? Or do you think they'll conclude that the written policy is less salient than the self-evident norm that participants here are focused on SQL, and bounce off?

This likely bad outcome is despite the fact that SQL questions are on-topic for the site, as intended and as written! What to call this problem? I call it clutter.

The same concept applies to other community norms, like the one we're discussing in your post about research effort. If the last 97 questions out of 100 are low-effort and unresearched, a new user won't read our guidelines for how to write a good question; they'll just ask a low-effort, unresearched question themselves, because they correctly perceive that this is the norm. Any remaining users who would prefer a different norm will find that this is no longer the community they were originally interested in joining; no amount of tagging or AI filtering will restore to them the flow of new users who are now being trained to the low-effort norm. They have been cluttered out.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

So you're saying that, if someone opens the front page of software.codidact.com, and sees that the to... (3 comments)
So you're saying that, if someone opens the front page of software.codidact.com, and sees that the to...
matthewsnyder‭ wrote about 1 year ago

So you're saying that, if someone opens the front page of software.codidact.com, and sees that the top 20 questions are python, they would assume only python is on topic even though the site is called "Software Engineering"?

r~~‭ wrote about 1 year ago

They might not assume that only Python is on topic, but I think they would assume that the community is made of people who focus on Python.

This happens all the time in the real world. You go to join A/V club because you're very interested in film soundtracks, but everyone there is focused on producing the school news videos, so the equipment they have is focused on that, and when you propose using club funds to buy a digital audio workstation they shrug and say, well, sure, that's technically an A/V thing, but you're the only one here interested in that and we can't really justify the expense. ‘But it's called A/V club!’ Too bad, kid, you need to read the room to determine the actual focus of the club, which can be narrower than the declared focus, or in some cases altogether different.

matthewsnyder‭ wrote about 1 year ago

I think this assertion is contrary to my experience.