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.

Post History

75%
+4 −0
Meta How much research effort is expected from the asker by the community?

Should someone be warned when their question lacks for effort? Actually, we don't know about their effort. Nor do we actually need effort, itself. What we need are particular results of effort...

posted 3y ago by meriton‭

Answer
#1: Initial revision by user avatar meriton‭ · 2021-07-26T16:04:44Z (over 3 years ago)
> Should someone be warned when their question lacks for effort? 

Actually, we don't know about their effort. Nor do we actually need effort, itself. What we need are particular results of effort, and for these to be clearly communicated through the question.

Thus, we should never write something to the tone of "I am hereby warning you to put in more effort (or face the wrath of our downvotes!)", because:

* we may be mistaken about the effort (they might just not have communicated it)
* it doesn't clarify the kind of effort required, nor what this effort should achieve

Instead, we should inquire after the outcome of the expected effort. For instance:

> * What did the manual say?
> * What did the error message say?
> * What happened when you stepped through this in a debugger?

This should take care of the innocent mistakes.

If that doesn't work, a moderator should state site policy:

> On Codidact, we expect that ...

and enforce it by closing the question.