Comment Re:Documentation Shitty so Developers Turn to Web (Score 1) 418
I can typically agree with this.
If I'm just looking up a single API call or two, MSDN is typically enough. Maybe I end up on StackOverflow, etc. if that fails and I can't figure out why on my own without too much effort, but MSDN is typically first and last.
However, if it is some odd part of the Win32 API that requires a significant set of functions in specific orders, and I'm not well versed in that specific set of functions, I end up at StackOverflow or the like first and MSDN second. Jogging my memory--it's been a while since I wasn't even remotely familiar with the parts I've ended up using--I recall working with COM with MinGW, "docking" a window to the side of the screen, and some others putting me in this position when I first began needing that information. Typically, though, StackOverflow and the like is a "Just give me an example that I can read and then look up on MSDN for what the hell I'm doing." All that followed by messing around with code and typically having to look up other pieces that those completely missed. I think that matches what you're saying, though.
Either way, the Win32 API is where I use StackOverflow more than any other API, though. (Except there are a couple of odd libraries I code with that I wish there was more information on the likes of StackOverflow for, because I instead spend hours reading header files, experimenting, ending up rebooting, etc., repeat until I maybe get what they're on about with their obscure descriptions.)