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
Downvote them for now. If it becomes a common problem, then create a close reason of no-research, and close them. Such questions should not be "answered" in comments. First, comments aren't for ...
Answer
#1: Initial revision
Downvote them <b>for now</b>. If it becomes a common problem, then create a close reason of no-research, and close them. Such questions should <b>not</b> be "answered" in comments. First, comments aren't for content. Using a comment to answer subverts the peer-review process. Real information on this site shouldn't be hidden in comments where it is easily missed. Users should be encouraged to leave a comment explaining how some minimum research should be done, asking what research was done, or even suggesting specific research. If such questions are actually answered too often, then that's another reason to create the no-research close reason. If people dump low-quality questions here and get the desired result, they'll be back doing the same thing again and again. Even worse, others will see that it works, and they'll be here doing it too. As Elsewhere has so profusely demonstrated, guidelines and even explicitly telling people to stop unwanted behavior has little effect. There have to be negative consequences, else there is no reason not to just ignore all the guidance.