The smallest useful slice still has to work
A narrow release can reduce investment without leaving people to bridge its gaps. Define a complete workflow before cutting scope, including the behavior that matters when something goes wrong.
4 min read
Engineering Essays .
Architecture, delivery, maintenance, and the trade-offs behind dependable software.
4 articles
A rollback does not undo every consequence
Restoring a previous release can leave changed data, external effects, and interrupted work behind. A recovery plan starts with those consequences and identifies how the crew will resolve them.
4 min read
Sometimes the useful change is a dependency removed
Dependencies consume attention as well as computing resources. Follow one recurring interruption to its source and examine whether the next useful outcome requires the dependency at all.
4 min read
Generated code and generated tests can agree on the wrong answer
A passing test suite can repeat the assumptions that produced an implementation. Evaluate AI-assisted work against explicit requirements, independent examples, and the consequences of being wrong.
4 min read