· 2 min read
What does the incident history say?
The postmortem folder is the most honest architecture document an organization owns. How we read a year of incidents before we read a single diagram.
#reviews#incidents#evidence
Tagged: reviews
6 articles
· 2 min read
What does the diagram leave out?
Every architecture diagram is a claim about what matters. The review is not about the boxes you drew; it is about the arrows you did not.
#reviews#diagrams#evidence
· 5 min read
What would have to be true?
The five-word question our whole practice runs on. A long briefing on using it to audit claims, size risks, and end the meetings that should not have started.
#reviews#method#decision-records
· 2 min read
What is the load path?
Every request your system serves travels a load path, and most teams have never traced one end to end. The first question of every review we run.
#scaling#architecture#reviews
· 2 min read
How do you read a latency histogram?
The average is a fiction and the p99 is a person. Reading latency distributions the way the review reads them, shape first.
#reviews#latency#observability
· 3 min read
What makes an architecture reviewable?
Some systems can be reviewed in a day; others resist a month of workshops. The difference is a property of the architecture, and it can be designed in.
#reviews#design#decision-records