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
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...
Answer
#1: Initial revision
> 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.