Code Strategies as Diets
There is no one right diet or right way to write code. Pick something sustainable and stick with it.
I recently attended MenderCon. It's an online conference for software menders. What is a mender? A mender is someone who actually enjoys working on Legacy Code and mending old systems as opposed to makers who enjoy making new things.
MenderCon is a celebration of the power of mending Legacy Code. It's got a keynote and a stage with some scheduled presentations and it also has an open space component. I spent most of my time in the OpenSpace. I enjoyed lots of good conversations there, including a discussion of how to best teach TDD and an AI Vent session.
There was one comment that stood out to me. I didn't write it down so I am paraphrasing.
I thought that was a great analogy. It kind of goes along with a bunch of things like Atomic Habits and GeePaw Hill's Change Harvesting. Lasting change starts small and sustainable. Small changes over time lead to bigger changes. There is a famous Hemingway quote that sums this up: 'How did you go bankrupt? Two ways. Gradually, then suddenly.' Here he is talking about a negative change, but it works for positive change as well.
Need Help?
Need help building good habits for your team? We offer a variety of coaching packages. With as little as one learning hour a week you will start to see improvements. If that sounds interesting, let's talk.
