| Exactly. This is the worst advice I have seen on entering coding, maybe ever: The answer to every question is out there. Engineers know that better than anyone. Even the best engineers ask Google questions all the time. The biggest difference between you and an engineer is the mindset. After you have the right mindset, here is how the execution will go: You start asking Google questions, which leads you to all sorts of resources on StackExchange and Quora and a million blogs and other websites. You find twelve tutorials on HTML and nine on CSS, and you bounce around between them to find the best ones Unless you're a pretty amazing auto-didact this is terrible advice. The author posits his advice as learning how to learn on your own (which is good to a certain degree), but what this advice requires is to first become an expert in querying Google and not only sorting results but going through all the different recommendations? How would someone without programming experience effectively evaluate which are 'the best ones' from the spam and the outright wrong articles? Over the last few years < 10 people have asked me "how would i become a programmer" or "what's the best way to learn SQL", or something similar. The first questions I ask are 'what do you want to do' and 'why do you want to be a programmer'. I'd never really considered "go google some keywords, read everything on the first page, and let me know how that works out for you" |