Is there a way to write Q&A so it don't bother users whom don't faced the problem, and only for users whom really suffer from the problem?
As SO FAQ says its fine to answer your own question. But if you write the solution as a question, which is understandable by ones whom faced the problem and the answer for the problem in a post, then other user, which didn't faced the problem, complain that the question is not complete as they cannot understand how to reproduce the situation.
Sometimes you find a nontrivial solution for some problem and you want to share it on SO as it really may be of interest for others whom faced with the same.
Ex: You have made a lot of changes to some library and gcc gives you some errors. You have found the solution to this problem, but you don't know which of your changes were reasons for the problem.
I know there is a human factor. I just want to contribute and I don't want to "socialize" here. I can support my solution for users who suffer from problem, but not for a clot of spectators who don't want to get bored.
Answer: After spending time examining other posts related to the subject, I can conclude that the idea of self-answering posts "just to share solution for ones who need help" fits SO idea of "With your help, we can build good answers to every imaginable programming question together". But community doesn't accept such posts as there is no fun in such posts.
My own post (which I deleted due to "peer pressure") had something like +4 -9 votes in a day. So if read it directly 4 found it useful and voted up, but 9 found it useless and voted it down. It wasn't misinformation, it wasn't useless for ones who need help - it was not understandable for others.
There is uselessly to struggle with majority. Even I made it CW my reps still falling. However some tips extracted from other posts:
- you can skip falling your reps (I hope I wouldn't banned from site and however you can earn some reps by other ways)
- you can follow procedure - "post Question" ... "wait" ... "wait more" ... "voila! you "luckily" found answer" from Peter Mortensen answer in post (Posting and answering questions you have already found the answer to). I know its a bit stupid, but I think I will use it in future to save my nerve cells
- make some short directions in question body how to reproduce the situation. I think that it can defend your questions against "just spectators"
and use these tips only for "complete solutions" answers, not ones that probably really need discussion. Then it is reasonable to write detailed context to save time for ones to whom you appeal for help.