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 »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on How will you balance demanding high quality questions with maximising the number of users?

Parent

How will you balance demanding high quality questions with maximising the number of users?

+12
−1

There is a well know trade-off between a site aiming for questions/answers that are of a high quality and useful for people who arrive from Google and a site being nice to new users who often only care about someone doing their homework for them, so they can complete a programme course, with no intention of ever writing software again or learning more than what is needed to pass.

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?

1 comment thread

General comments (1 comment)
Post
+6
−0

The question is not "what will you do", but "what will we do?"

This site is community-run. While of course there are a few rules that we need to impose to be able to host a community, for the most part, every community gets to choose its own way. That includes things like this - this community can choose for itself how it wants to handle things like homework questions and quality management. We're more than happy to advise and guide, but ultimately - it's up to you!

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

1 comment thread

General comments (10 comments)
General comments
Ringi‭ wrote about 4 years ago · edited about 4 years ago

At the our last home "you" decided that "we" were not allowed to do anything that made people we did not welcome feel unwelcome.

luap42‭ wrote about 4 years ago

@Ringi as Art said, "we" will not impose any, but the lightest rules on the community. There are some safeguards for "you" (open-source; we plan to create a non-profit organization with community board seats; ...). However we do require some basic amount of decency. See our minimal Code of Conduct. Normal use of the site should not interfere with that CoC though.

ArtOfCode‭ wrote about 4 years ago

@Ringi I'm not sure what you mean. This site is not run by Stack Exchange, if that's what you're worried about - the folks who run this site are not the same people as those who can make decisions on Stack Exchange sites.

Lundin‭ wrote about 4 years ago

But shouldn't at least some things get narrowed down before launching the site? As it sits now, the scope seems incredibly broad and nobody has a clue what's on-topic - everything vaguely programming-related? I'm not sure what this site is for or how to use it. Nor am I particularly interested in contributing to a "everything programming" site. How's that different from Reddit, Quora et al?

Lundin‭ wrote about 4 years ago · edited about 4 years ago

If we make a "super site" because we fear low contribution on specialized sites, it might very well have the opposite effect: scaring away technical specialists, whom are absolutely necessary for a programming site to flourish.

ArtOfCode‭ wrote about 4 years ago

@Lundin this site has an initial scope, which was hammered out on Meta.CD in the site proposal - it's in the welcome post and at the top of the Q&A category. That can be changed here on Meta if that's useful.

Lundin‭ wrote about 4 years ago

Yeah I read it, it's apparently everything vaguely programming related... I very much doubt there will much in the way of quality posts with such a huge scope. And no attention is given to the usual hot potatoes: homework questions, career advise, tool recommendations etc. Are these on-topic or not? Code reviews? Code golf? And so on...

ArtOfCode‭ wrote about 4 years ago

@Lundin This is much like a private beta for a new SE site; those things have not been defined yet, because they can and should be decided here on Meta by the folks who want to participate here - this community belongs to those people.

jrh‭ wrote about 4 years ago

I think it's important for a QA site to continue to focus on documentation as a purpose instead of "please answer my question"; that immediately would make homework, career advice, tool recommendations, code golf, and overly broad questions off topic. However the path to that probably requires making it very obvious that you do not get help as a user from the "Ask Question" form, you get it by searching, and you should probably bury the Ask Question button like the advanced user feature it is.

jrh‭ wrote about 4 years ago · edited about 4 years ago

The other thing I think would be necessary if you went that route is either establish a clear scope of what is/isn't ok to document here (I see Excel formula questions getting downvoted even though I can't find a reason why that'd be off topic here), or if you don't know right now, either disable question downvoting or give it no penalties, because you're pretty much saying "please determine this experimentally, at your own risk".