When discussing Trunk-Based Development (TBD), we often get bogged down in the mechanics: the branching strategy, the CI speed, or the revert logic. But as a colleague recently pointed out to me, moving away from Pull Requests (PRs) is a “drastic change” that impacts more than just Git history. It impacts the social fabric of the team.
Read more...Trunk-Based Development is designed for speed. It removes waiting and keeps integration continuous. Code moves to the trunk quickly, often within minutes.
Read more...When we talk about the current AI surge, the conversation almost always centres on output.
Read more...Most developers recognise the “waiting room” of software development. The code is written, the tests are green, and the change is ready. Then you hit git push, open a Pull Request (PR), and the work stops moving, and then the wait begins.
For many developers, the time spent waiting for reviews exceeds the time spent writing the change.
In The Claes Test, I ask a critical question about collaboration: Do boundaries get out of the way so teams can solve problems together? (Question 7).
Read more...In a previous post, I talked about Kurt Lewin’s equation: \(B = f(P, E)\).
Read more...When we talk about DevOps transformation, the conversation usually starts with tools. Kubernetes. CI/CD pipelines. Cloud platforms, and nowadays LLMs.
Read more...The Eisenhower Matrix is one of those productivity tools everyone knows. It’s neat, simple, and widely taught.
Read more...I love the terminal, but I still spend half my day in Sublime Text. When an idea appears I hit Cmd+N to open a blank, unsaved buffer and start typing.
Read more...In this series, we’ve explored the visible friction in software teams: the flow killers, the product mistakes, and the technical debt that slows everything down.
Read more...