Noob Observation: There is an element of knowing what saves you time and then on top of that why and how it does. The saving I will divide into two categories:

Noob Observation: There is an element of knowing what saves you time and then on top of that why and how it does. The saving I will divide into two categories: 1. Easy wins category: Don't repeat code, cause you will take twice to change it. This is clearly visible to even the author. 2. What I call the "tougher" win category: When you require more executive function like breaking a bad habit, managing cognitive load; in short understanding why it saves you time in the long run. A reasonable example of this is using typing in python. I and many of you know that you can catch errors way faster using types+pyre(for example) than writing tons of unit tests, but it takes an old python programmer longer to get used to putting in the types and some times remembering to set up and use Pyre to get used to the idea of how it saves time. Pre-pyre used to python dev might just think "I will write tons of unit tests". There is obviously a psychological/mental health component to this.