You cannot just google your way through it. There are times when you don't even know what to google. I remember as an early beginner being stuck with something that had to do with closures. I had no idea what was going on and didn't know what to google and when I asked questions on stackoverflow and reddit please started saying things about decorators and whatnot!!! It is only when I sat down and went through some kinds of structured tutorials that I knew what had stomped me. Sometimes, you ight just have to be aware of some problems even if you'd don't understand them properly but you are aware of their existence and what they are called.
I’m the complete opposite; I’ve yet to encounter a problem I couldn’t Google or bug someone in IRC about (and that’s the key).
Sometimes you have to engage with someone else to solve a problem, but there are hundreds of people willing to do just that at literally any given time of day.
Yes, as a last resort, googling simply the error or part of error gets one on the way to solution. Very rarely I had to face a search term which doesn't point or advance me towards solution.
For context, I use javascript & basic html css to make simple apps for my own use. apps.bydav.in
Usually I just take a quick glance at, and/or try of the main features of a language in some REPL or toy program, _then_ will jump straight to developing something to it and Google/DDG my way through. I do agree that just Googling your way through without having a basic grasp of the general philosophy and main tools a language puts at your disposal can be counterproductive.
If you're new to programming, yeah. If you're an experienced programmer, and you've used multiple languages, you're more likely to just write something that's not idiomatic than to get totally lost like that.
