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...Most productivity tools work the same way. They rely on capturing everything into one big Master List, sorting and labeling it, and hoping that structure will lead to execution.
Read more...In the first post, I introduced nine wastes that hide in software teams. In the second, we looked at the flow killers that destroy momentum. In the third, we covered the product wastes that derail your work.
Read more...In the first post, I introduced nine wastes that hide in software teams. In the second, we looked at the flow killers that destroy momentum.
Read more...