Earlier quoted context omitted.
It's not a problem when you look up the spelling or the order of arguments in the reference. It's a problem when you search for the solution to every problem with a search engine. So many answers on the internet are written by absolute beginners, who happened to have the same problem, and then blogged about the solution after spending 5 minutes of googling. Sometimes these answers are alright, but often they are shal…
> It's a problem when you search for the solution to every problem with a search engine Why? I'd fire an engineer who took on problems and refused to spend 10 minutes googling around and looking for solutions first. I have no interest in humoring someone who dismisses the entire internet because it is written by "dumb people." Buying and reading books is how you draw out a project you don't want to work on.
"Why spend time learning all this useless background information when I can just find the answer on google in 10 minutes".
It was obvious that people just cobbled together dirty workarounds that they must have found somewhere on the internet. They used runtime hacks to circumvent limitations in a library API, even though the library was developed by someone else at the same startup, and the runtime hacks were not necessary if the developer had any clue about what they were doing.
Sometimes you get stuck, and searching the web can help you get unstuck.
But the problem is when people just search for the solution to EVERY problem they encounter and never learn the basics because they don't want to "draw out the project".
(Addendum: I'm not dismissing the internet. You can find good information on the internet. But it takes time. The problem is that people take shortcuts, and instead of learning everything they need to know, they just google for the answer to their specific problem because it seems more productive in the short term. Buying and reading books will take longer than copying an answer from Stack Overflow, but it will not take longer than learning sufficiently in depth about a topic by reading blog posts, documentation, etc)