So what do those habits look like? The key to manageable code is not applying big, complex ideas occasionally (you know, those 4 week refactoring branches). Instead, it comes from applying very simple ideas
. Relentlessly. No seriously, turn that dial up all the way to 11.
Tiny Steps That Maintain a Working State
As you move in the right direction, you want to
build-in and ensure quality at every step
, rather than adding or verifying quality after the fact. That means having feedback loops, like tests and foolproof automation. You can learn more about some of these processes for building-in quality and reducing friction in [Continuous Delivery].
Make smaller steps, and keep things in a working state at each point along the way.
Now use your IDE's automated refactoring to rename the function. And here's the scary part. Commit it. Right now. And push it all the way through to production. If you can't do that, then
write down a list of reasons you can't
. Now you've got a todo list of things that are getting in the way of building relentless tiny habits to improve code. Once you've gotten through your todo list and are able to push that tiny improvement through to production, you're off to a great start!