Appendix
Reading Routes
This is a field manual. You don't read it cover to cover. You use it when you need it.
How to Use This Manual
Got a specific problem? Hit Ctrl+K (Cmd+K on Mac) to search. Find the section. Get the answer. Get back to work.
Want to learn a topic? Pick a route below. Read the chapters. Apply immediately.
Mentoring someone? Point them to a route. Use the checklists as shared vocabulary.
Debating an approach? Use the frameworks. "What level of work is this?" "What are we trading off?" "Is this architecture or design?"
Routes by Role
New Engineer (First Week)
Build the foundation first.
- Master Your Gear — Know your tools cold
- Find Your Own Answers — Hierarchy of truth, 15-minute rule
- Communication — Declare status, ask questions
- Code Review — Give and receive feedback
Then explore as needed.
On-Call Engineer
When you're carrying the pager, bookmark these:
- Debugging — The methodology
- Incidents — Response structure
- Quick Reference: Debugging — Checklist for 2 AM
Tech Lead
Making architectural decisions and growing others.
- Architecture vs Design — Know what's load-bearing
- P-Cubed — Prepare, Prove, Produce
- Technical Debt — Deliberate debt, payback triggers
Staff+ / Principal
Shaping how others work.
- Levels of Work — Problem, Initiative, Epic, Task
- Architecture vs Design — No best practices, only tradeoffs
- Teaching & Mentoring — Multiply yourself
Manager / Engineering Leader
Creating the environment where good engineering happens.
- P-Cubed — How work flows through teams
- Communication — Status, decisions, alignment
- Incidents — Response structure, blameless culture
Routes by Situation
"I'm stuck on a bug" → Debugging | Quick Reference
"I need to make an architectural decision" → Architecture vs Design | ADR Template
"Production is down" → Incidents | Update Template
"I'm reviewing code" → Code Review
"I'm onboarding someone new" → New Engineer route | Teaching & Mentoring
Quick References
Checklists, not essays:
Find your route. Get back to work.