Appendix

Reading Routes

This is a field manual, not a textbook. You don't read it cover to cover. You use it when you need it.

A Note on Framing

This manual uses military metaphors throughout. The intent is operational: the voice in your ear when things are going sideways, practical guidance under pressure.

If the framing doesn't resonate, ignore it. Take what helps. Leave what doesn't. The principles underneath are what matter.

How to Use This Manual

When you have a specific question: Use search (Ctrl+K / Cmd+K) or the table of contents. Find the section. Get the answer. Get back to work.

When you want to learn a topic: Read the relevant chapter. Follow the cross-references. Apply what you learn immediately.

When you're mentoring: Point to specific sections. Use the checklists. Reference shared vocabulary.

When you're debating: Ground the discussion in 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)

Start here. Build the foundation.

  1. Master Your Gear — Know your tools. This is non-negotiable.
  2. Find Your Own Answers — The hierarchy of truth. The 15-minute rule.
  3. Communication — Declare your status. Asking questions is the work.
  4. Code Review — How we review. How to receive feedback.
  5. Pairing & Collaboration — How we work together.

Then explore as needed. The rest will come.

On-Call Engineer

When you're carrying the pager.

  1. Debugging — The methodology. Reproduce, isolate, understand, fix, verify.
  2. Incidents — Roles, priorities, communication cadence.
  3. Quick Reference: Debugging — The checklist version.
  4. Templates — Incident update and postmortem skeletons.

Bookmark these. You'll need them at 2 AM.

Tech Lead

Architecture, debt, and people.

  1. Architecture vs Design — Know what's load-bearing. Choose tradeoffs deliberately.
  2. Technical Debt — Deliberate debt. Debt registers. Payback triggers.
  3. Communication — Status, decisions, alignment.
  4. P-Cubed — Prepare, Prove, Produce. The execution cycle.

You're making architectural decisions and helping others grow. These are your tools.

Staff+ / Principal

Systems thinking and organizational impact.

  1. Levels of Work — Problem, Initiative, Epic, Task. Know which you're solving.
  2. Architecture vs Design — There are no best practices. Only tradeoffs.
  3. Teaching & Mentoring — Multiplying yourself.
  4. The Canon — The reading list. The shared vocabulary.

You're shaping how others work. These frameworks become your vocabulary.

Manager / Engineering Leader

People, process, and systems.

  1. Communication — Status updates, decision-making, alignment.
  2. P-Cubed — How work flows through teams.
  3. Incidents — Response structure. Postmortems. Blameless culture.
  4. Learning & Growth — How engineers develop.

You're creating the environment where good engineering happens.

Routes by Situation

"I'm stuck on a bug"

  1. Debugging — The full methodology
  2. Quick Reference: Debugging — The checklist

"I need to make an architectural decision"

  1. Architecture vs Design — Framework for thinking
  2. Quick Reference: Tradeoffs — Questions to ask
  3. Templates — ADR template

"Production is down"

  1. Incidents — Response structure
  2. Templates — Incident update template

"I need to write a design doc / ADR"

  1. Architecture vs Design — What to include
  2. Templates — ADR skeleton

"I'm reviewing code"

  1. Code Review — The full guide
  2. Templates — PR description template

"I'm onboarding someone new"

  1. Point them to the New Engineer route
  2. Teaching & Mentoring — How to teach effectively

Quick References

For when you need the checklist, not the essay:

Find your route. Use what you need. Get back to work.