After learning something new, it’s tempting to let our excitement drive us to pick up that shiny new hammer at any opportunity and go looking for some nails. We are all neophiles.
This applies to every field and endeavor. You learn a new word that tastes like honey when it forms on the tongue, and you start looking for excuses to use it. One method of teaching works great for one child, and so you try to replicate that success with other children despite their uniqueness. You get a new Instant pot, and you use it to make every meal for the next 2 weeks. Never mind that one of those meals was scrambled eggs.
In my own field of computer programming, there are times where, after coming to understand a new development pattern, my thinking gets colored by it. How can I solve this new problem with this same pattern? It worked so well before, so of course it must work well again on this other problem that might be totally unrelated. As a result, I can burn too much time. Or write code that isn’t optimal.
Eventually we find ourselves laying flat on our backs after we tried to push our new, gigantic square peg through a round hole while running at a dead sprint. Or worse, we end up running endlessly in circles wondering why our new key won’t unlock any of the doors we need to go through. We start getting impatient with the doors.
The trick, I think, is to get to the stage where you have internalized it. It becomes a common thing. Your new skill/idea needs to be bouncing around in your subconscious and part of your overall repertoire, instead of at the forefront of your mind, dancing and demanding your attention.
How do you do this? By learning something new.