So nice article, so poorly titled on HN. Kind of irony here.
Missing tip: when creating a new question on Stack or traditional forum: make your question topic describe the root of the problem. Be concise.
You will increase chance that somebody that potentially knows the answer will come to help.
Titling your topic "problem", "need help", "my app doesn't work" isn't going to help you and will frustrate others, usually dealing with people breaking half of the tips from the article.
Sorry for the title, I preferred keeping the original one. Mike's blog has quite interesting stuff!
As for your other point, yes, with all the negativity that StackOverflow sometimes exhibits, I really feel that the pressure/urge for users to create a "Minimal, Complete, Verifiable" example [0] is part of the site's appeal, and part of the reason of the high quality of responses you sometimes find there.
Missing tip: when creating a new question on Stack or traditional forum: make your question topic describe the root of the problem. Be concise. You will increase chance that somebody that potentially knows the answer will come to help.
Titling your topic "problem", "need help", "my app doesn't work" isn't going to help you and will frustrate others, usually dealing with people breaking half of the tips from the article.