The Friction I Don't Want to Lose

I love learning and am always curious. In the past I’ve been known to not just dive into the docs of a third party package, but also the source code. Not just so how I can learn to use something, but also to know how it works and learn new techniques that I can apply elsewhere. I may role my eyes when the Curious George moniker is applied, but I also acknowledge the merit behind the sentiment. However, more and more I find that learning on the job is being devalued in favor of speed. There used to be a pattern when it came to solving a new problem (or a new problem to you): identify the problem, research and learn how to implement a solution, then implement the solution. The coding (implementing part) is fairly straightforward once you knew how to solve the problem. But the learning and understanding was the friction. It was the hardest and most time consuming part. But it was also the most dopamine inducing and rewarding aspect. And that learned and earned solution was something that…