Context

So, I recently came across a wonderful book called “The Right Way to Commit”, which made me realize how important it is to know what to do next. But here’s the thing: sometimes, even with new knowledge, it’s not always easy to act on it and consistently make better decisions.

Software engineering is all about learning, unlearning, and relearning. Whether it’s about making, committing, or breaking changes, I try to figure out what committing means and what making a change means.

Solution?

My simple solution: filter, commit, repeat

Before making any change, the main thing is to understand the purpose, context, and the real reason for making the change. The right way to commit is the one that helps you and your team move forward, and you can always iterate on it later.

To make this easier, I try to ask myself: what does it mean to commit, and what does it mean to make a change?

Final Thoughts

Once you make a change, you should also take a moment to appreciate how much effort went into making it possible and how you can improve it further! However, keep in mind that this is not a 100% perfect or prescriptive guide, but rather a way to keep learning and iterating.

In summary, try to work with new learnings, download the book if you haven’t already, and use it to help you commit better. If you have any thoughts, let me know!