5 ms·
I usually turn to SO in hopes of a quick and easy answer, but a lot of the time your specific use case isn't going to be well covered as the stackoverflow threa
by asdff 5y ago
I usually turn to SO in hopes of a quick and easy answer, but a lot of the time your specific use case isn't going to be well covered as the stackoverflow threads sometimes have some bespoke requirements from the asker.
What I find is that it can be faster to just look at the documentation that comes with the tooling. Usually a good stack overflow answer is just regurgitation of something that's already covered in the documentation that the asker clearly didn't read a lick of. When you start using a new tool, just skimming the documentation end to end can but you at such an advantage and set you up to get working with the tool in the correct way with a decent understanding of some of the caveats that might be at play with your particular use case (which is rarely something that can be gleamed from a terse stack overflow answer). Even just a pdf covering a language can be handy to thumb through the chapters and revisit common patterns like for loops that can vary in different languages, once again its easier to trod down a familiar pdf textbook than it is to try and trench up something relevant from google search these days.
- jmchuster 5y agoIt's coming at the problem from different directions. The documentation gives you the general bottom up approach, but lacks details and examples. SO shows what it should look like at the end, and adds details on edge cases that the documentation just glosses over. But you can never find exactly what you want, so you combine those two, a working end result, then modified using the documentation, to get what you want in the end. If you already have a working pattern that you're just modifying, you might get away with just looking up documentation. If you already have a strong foundation and know exactly what you want to do, then you're just looking up the syntax. Maybe another analogy might be, learning vocab to better express your thoughts, vs looking up the exact spelling of a word you already know.
- asdff 5y agoPersonally I've replaced a lot of my stack overflow usage with hacking along with test cases and using the documentation to help develop those tests. Imo, its a lot easier to figure out how something works by figuring it out with your two hands fiddling around vs hoping you find someone who writes well and understandably about this specific niche thing on stack overflow. Sometimes on stack overflow the answer is a very lazy "just install another package" vs developing a solution with the base tooling that's probably more performant anyhow, if a little bit more verbose.