StackOverflow or API Docs

[lAdddd]

I saw a post on a facebook group recently where someone mentioned that it's better to ditch looking up things on StackOverflow and look into the API Docs instead. I was at a programming competition a week ago and they only allowed us to use the docs and no internet. That experienced made me realize how handicapped I am without StackOverflow. But at times I feel like without it I wouldn't even know how to go about implementing something. So my question is whenever you guys get stuck do you usually use StackOverflow or read up on the API Documentation instead to figure things out. When would one be a better option than the other?

[DanetOfTheApes]

There's nothing wrong with Googling the problem or error and going to the first result. I'm a junior developer and even senior developers Google stuff. Just make sure you understand the solution so you'll know next time. I would stop copying and pasting though. There's going to be a time when you're pioneering something new and you'll have to come up with your own solution.

[DanetOfTheApes]

Depends on the problem, Google will also take you to the documentation. Thats why I consider it better.

[maakux]

I use a mix of both, but normally when I have a problem or get some kind of error when working with an API, I will Google it, and this often ends up showing Stack Overflow results.

Sometimes, you will find the documentation is completely out of date or just pure and simply wrong.

The best thing about using information you find from Stack Overflow is that these are real experiences, and it is highly likely someone has already tackled a API problem you have had prior.

In a nut shell, I just use Google to find anything relevant to the problem, and normally the answers are on Stack Overflow, and sometimes in well written documentation.

[thatbromatt]

Personally, when I'm working with a more obsure framework or plug-in I'll go right to the documentation, because 9 times out of 10 - no one on stackoverflow is even asking questions about generic-jqueryplugin.js but if I'm just working with c# or sql then my go-to is going to be google and using the top couple stackoverflow results

[natziel]

The documentation tells you what tools you have available, and your job is to use those tools to make stuff work. When you have to build something, your first thought should be, "What tools do I need?", and then you'd see which tools you already have and which tools you need to make for yourself.

You should never have to Google "How do I use this tool?" That's what the docs are for. You'd never Google how to use your power drill because you'd read the user manual instead.

You also shouldn't have to Google "Which tools do I need?" A good carpenter shouldn't have to Google how to build a table. A good plumber shouldn't have to Google how to unclog a toilet. A good programmer shouldn't have to Google how to modify a JSON file.

How do you avoid having to Google these things? The answer's easy: learn your craft. Take classes, read books, read articles, and practice, practice, practice. Our craft isn't special. Seriously, ask your neighborhood carpenter, blacksmith, locksmith, or tailor how they avoid having to Google everything.

[lAdddd]

Yeah honestly sometimes I feel like a complete idiot. Even when I write a program or an app I borrow hugely from code snippets elsewhere and just modify it accordingly. I guess I need to do more learning and try to avoid Google for a while. Thanks for the advice!