5 parts
Why Engineering Teams Stop Shipping
A five-part series on the tipping points that freeze delivery, and the first month of work that restores cadence.
Open series →Journal
Writing on shipping, cost, and leadership
Series for problems that take more than one sitting. Standalone notes when a single point will do.
Featured series
Latest posts
ERC-8427 integrations: what has been tested so far
The ERC-8427 repo now tests spend grants with Safe, ERC-4337 accounts, ERC-8004 agent identities, and ERC-7710 delegations, proposes a mapping for x402 payments, and an outside developer has built an order-amendment experiment on it. What each one does, and how far it has been tested.
Read essay →ERC-8427: capped, revocable spending on Ethereum
ERC-8427 lets an account owner register capped, revocable spending of ETH and tokens for a delegate, with per-payment, rolling, and lifetime caps. Where it helps and why.
Read essay →Locking funds on a condition, on any Canton registry
Canton's token standard can show a lock, but not a standard way to release on a condition. A draft interface, reference implementation, and ask for builders who need it across registries.
Read essay →The First 30 Days
The first four pieces looked at different reasons a small team can struggle to ship. Here is how to bring those investigations together in the first month.
Read essay →Who Reviews the Machine
A small team starts using AI coding tools, and more work waits for review. Who has time to check the additional code, and what the first two weeks of that work look like.
Read essay →Where the Week Went
Six engineers, a full week, and very little progress on the work everyone agreed was important. How small teams account for support, incidents, and the other jobs that fill the calendar.
Read essay →Busy Is Not Shipping
The team keeps releasing features, but important customer and business problems remain. How small engineering teams can reconnect their work to the results people need.
Read essay →The Complexity Tipping Point
Delivery rarely collapses overnight. Six months ago the team shipped in days. Now a small feature needs six meetings. Here is what a complexity tipping point looks like, and the first two weeks of work.
Read essay →