The Intimidation of Creatively Solving Problems

One of the things about programming in the same “environment” for an extended period is that you get comfortable with the way you tackle similar problems. Case in point:
When you start writing a plugin, you likely have an idea as to how you will implement something before writing it.
I’d venture to say that this begins to happen while the client is describing their problem. I don’t think there’s anything inherently wrong about this. In fact, I believe that it’s probably a good thing as it’s a sign you’re learning your way around the API, how to structure files, assets, and so on.
But at what point do we start coasting on autopilot? Or, perhaps a better way to ask it, is when are we just going through the motions of solving different-but-similar problems?
We Should Be Creatively Solving Problems
For most of us, the things we’re building for others are going to likely be slight variations on problems we’ve already solved or problems that have been solved by other people. (Thus libraries, right?)
On top of that, we have reusable components and libraries of our own that we import into new projects top help us with certain, repetitive
Source: https://managewp.org/articles/13749/the-intimidation-of-creatively-solving-problems

source https://williechiu40.wordpress.com/2016/11/02/the-intimidation-of-creatively-solving-problems/