Short pieces written by the people doing the engagements. No newsletter, no gating.
Most reporting disputes are not technical disagreements. They are disagreements about definitions that were never written down.
An error budget with no consequence is just a chart. Here is how we make the policy real without turning it into a blame exercise.
Every novel component in your stack is a maintenance debt that someone else will pay. A framework for deciding when novelty earns its keep.
Four signals that a planned rebuild is actually an attempt to escape accumulated process rather than solve a technical limit.
Page volume, escalation paths and the difference between being on-call and being permanently available.
We do not run a newsletter. If a piece is relevant to something you are working on, just email us and we will send it over.