I think this quote might benefit from a little bit of context:
"Often, they're looking things basic things up and referencing them as often as newbies are, because they never took the time to really master their work."
In my experience, looking up basic things is not really a sign of lack of mastery, it seems to me, the the thing you gain with years of programming experience is a sense of "what to do" and not necessarily "what is the exact command in this language to do it".
There might also be something to be said around general mastery vs. specific mastery.
All this said, I am in complete agreement with the idea of "directed or correct practice". Practicing bad habits does not "make perfect" in any sense but being really good at doing the thing you were practicing badly.
Please know that I write this not to be critical of your article, rather I wanted to add some of my perspective.
Thanks for your thoughts!
I agree. But on interviews I get asked questions like what's the difference between let and var? And I'm like really? Or what does a for each loop do. As opposed to presenting me with a problem where using said loop is the best or most efficient way to do it. Programming of about problem solving, not knowing every language or framework. Because after you've used a few, you realize they all do the same things. Just some better than others. And no matter the framework or library, the underlying technology and protocols and the same.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.