Cheat Sheets
A cheat sheet is scoped to an activity under time pressure — a round you are about to walk into, an incident you have just been paged for — not to a technology. Per-technology summaries belong in Reference, and duplicating them here at lower fidelity would help nobody and double the maintenance surface.
Each sheet answers four questions, enforced in CI: when to reach for it, the order to work in, the
values worth not deriving under pressure, and what going wrong looks like. The print stylesheet
hides navigation chrome, so Cmd/Ctrl+P produces a clean page.
Published
Section titled “Published”| Sheet | Use it when |
|---|---|
| Design Round | You have 45 minutes and a system design prompt |
| Coding Round | You are about to build a limiter, retry path, batcher, or worker pool |
| Design Review | You are reviewing someone else’s design |
| Incident Response | You have just been paged |
| Leadership Round | You are about to be asked about decisions you made |
Three cover an interview round; two cover work. That is the whole set the handbook’s material supports honestly — a sheet for an activity it does not cover in depth elsewhere would be a summary of nothing.