design review
A meeting where a proposed system design is examined by colleagues before it is built.
In more detail
A good review follows a fixed order: requirements, estimation, data model, high level design, one deep dive, then failure modes. Going back a step when a number surprises you is the process working. A system design interview is the same exercise under a strict time limit.
Example
A forty five minute budget: five minutes of requirements, five of estimation, eight on the data model, twelve on the high level design, ten on one deep dive, five on failure modes.Related terms
- system design — The work of deciding how the parts of a software system fit together to meet its requirements, and writing down what each choice costs.
- deep dive — The part of a design discussion spent examining the single riskiest component in detail.
- decision record — A short written note of a technical decision, the facts behind it and the trade-off accepted, so later reviewers understand why.
Taught in
- What A Design Is For, And How To Run A Design Discussion — Scalable System Design & Distributed Architecture
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
- Worked Design Three: Scaling The Metrics Pipeline — Scalable System Design & Distributed Architecture