3 ms·
It'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
by jmchuster 5y ago
It'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.