8 ms·
With any new habit in life, you fixate on it for a very brief period and then try to let it fade into the background. Then you periodically revisit it to see ho
by hinkley 2y ago
With any new habit in life, you fixate on it for a very brief period and then try to let it fade into the background. Then you periodically revisit it to see how you’re doing.
From a programming standpoint, and off the top of my head, I would include TDD, code coverage, and anything that comes out of a root cause analysis.
I tell junior devs who ask to spend a little more time on every task than they think necessary, trying to raise their game. When doing a simple task you should practice all of your best intentions and new intentions to build the muscle memory.
- osigurdson 2y ago>> TDD, code coverage I don't know how to track TDD, but for me, code coverage is an example of the same old false proxies that people used to track in the 000s. Before creating a metric and policing it, make sure you can rigorously defend its relationship to NPV. If you can't do this, find something else to track.