> [4] This is not the same as researching the issue and trying as many things as you can think of, which is definitely helpful in any context of question asking
It would help showing that in your question. Often questions lack the necessary information to discern whether the asker has actually covered the basics
> [...] how you know there are other ways you could do it but you're constrained toward this direction for various reasons
Answerers are also programmers that like to apply best practices whenever possible. If you want to do something unusual which might smell a little without explanation your colleagues, code reviewers or similar would probably also ask "is this really necessary?". So you either have to write defensively from the start or deal with the patronizing-but-wellmeaning-comment-downvote-edit-reopen ordeal.
It's unfortunate, but there is an information asymmetry. The answerers can only see what you write, while you have all the background information specific to your case.
It would help showing that in your question. Often questions lack the necessary information to discern whether the asker has actually covered the basics
> [...] how you know there are other ways you could do it but you're constrained toward this direction for various reasons
Answerers are also programmers that like to apply best practices whenever possible. If you want to do something unusual which might smell a little without explanation your colleagues, code reviewers or similar would probably also ask "is this really necessary?". So you either have to write defensively from the start or deal with the patronizing-but-wellmeaning-comment-downvote-edit-reopen ordeal.
It's unfortunate, but there is an information asymmetry. The answerers can only see what you write, while you have all the background information specific to your case.