The Panic Button for Trunk-Based Development
04 Mar 2026Trunk-Based Development is designed for speed. It removes waiting and keeps integration continuous. Code moves to the trunk quickly, often within minutes.
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...