I'm very much from the opposite camp. I learned to code in C in vi and didn't really have anyone to ask other than the manpages and the K&R book, I'm pretty sure I didn't even use syntax highlighting.
I do think this has shaped my programming even later to where I stubbornly stick to boring but stable programming languages like C, C++ and Java, and these languages I've used for in some cases almost 25 years and where I virtually never have to look anything up. It's not like I haven't dabbled in other languages and paradigms, like python and haskell and whatever; but it's not those languages I use when I need to build something. I just don't see the value in constantly learning all this flavor-of-the-month stuff. When the dust settles, most hyped upcoming programming languages become footnotes when the history of programming is written.
I do agree that quickly jumping to an online reference because you can't remember the order of the parameters for a particular method is a crutch that if you were forced to remember would remove that slow down. But at least I'm able to remember the correct method vs having to search for which method is needed and when.
I don't really know what the take-away is. This isn't a fast way to learn to program, or an easy way, and I'm not even sure I'd recommend anyone learn this way, but I also can't deny it's brought some very tangible benefits.
Everyone learns differently.
I am not surprised changing your approach helped you to improve your skills. But if someone were to use online search to say... find the library code, and read the manual, they'd likely get similar results to yours, right? ;-)
https://youtu.be/h1t14GnnQhc?t=20m15s
INAZUMA KICK!!!
n.b. I program like this too, just plain Emacs and I try to remember API and package names before consulting Dr. Google. The IDE trying too hard to help me is hugely distracting.
When I had to actively memorize I paid way more attention to what I was doing. I think the online search multitasking is honestly very bad for sustained attention and very passive. As an alternative I started to look up library code directly and just read and I feel like I learned more about how python worked in a few weeks than I did in months or so of just typing things into google.