To add to MichaelHampton's answer, the SE network encourages this style of information sharing, which is why it was made possible a while back to ask a question and post an answer at the same time. (this wasn't always available)

**Update**

Also see [this SE blog post][1] on why this ability was added. In short, they *want* to take the good parts of blogging, which you kind of despised judging by your question.

Some of us have been doing this lately to stay active on main, and also to 'centralize' more and more scattered technical information on the internet into a single place, which can be authoritative. For example, there have been times I've had to scour social technet and found here-says and maybes, and the OP never confirms if proposed solution works or not. If I try it and find it working, posting on SF with a relevant title has the benefits of helping someone else who googles the problem (since SF posts have a super high google ranking), and I potentially gain reputation, and SF potentially recruits a new member.

Also, what happens when you pose a question on SF, no one answers, and you *finally* figure it out after weeks/months/years of troubleshooting? Go ahead and answer your own question. It floats back to the front page, and you may even earn magical internet points for your efforts. People may not have *known* the answer, but they do know good troubleshooting when they see it.

Several of my self answered questions:

https://serverfault.com/questions/606160/vm-freezing-during-winpe-boot-up/606447#606447

https://serverfault.com/questions/606788/sccm-task-sequence-error-0x8007000e

https://serverfault.com/questions/606265/ensure-drive-is-mapped-at-login-on-laptop-with-strictly-wireless/606849#606849

  [1]:http://blog.stackoverflow.com/2014/04/putting-the-community-back-in-wiki/