The author is specifically advocating deliberate practice. In fact, it's amusing reading the article, as it seems he thinks deliberate "practice" isn't actuall

The author is specifically advocating deliberate practice. In fact, it's amusing reading the article, as it seems he thinks deliberate "practice" isn't actually "doing" something productive. The article supports, in every way, deliberate practice. I mean, this says it all: "This is compared to us developers learning to touch-type or learning the keyboard shortcuts of our IDEs." No. Deliberate practice for programmers is not limited to just touch-typing or keyboard shortcuts. It's actively learning to use new tools and environments, learning new languages, and learning different ways to program, such as functional or object-oriented programming. It's practicing coding in ways like coding katas. It's digging into code that isn't yours and making the software do new things, and issuing a pull request upstream. Deliberate practice isn't just "practicing." It isn't just mechanical. It's challenging, it's hard, and it improves you. If you think deliberate practice is just practicing mechanics, you are ignorant on the subject.