Home
Overview
This is the entry point for the handbook. Start here when you need the right page fast.
Why It Matters
Navigation matters because the best handbook is the one you actually open during work.
Core Concepts
- Foundations: thinking and judgment.
- Daily Development: shipping and reviewing work.
- Technical sections: frontend, backend, architecture, testing, and DevOps.
- Operating sections: AI Development, Career, Checklists, and Playbooks.
Mental Models
Use the handbook as a decision aid. If you cannot quickly find the relevant page, the structure needs to improve.
Best Practices
- Keep the most-used pages close to the top.
- Add links from overview pages back to the detailed docs.
- Use checklists for repeatable tasks.
Common Mistakes
- Creating duplicate notes for the same topic.
- Burying operational docs under theory.
- Forgetting to connect related pages.
Trade-offs
The handbook is intentionally opinionated. That keeps it practical, but it also means some pages will have a clear recommended default.
Decision Framework
flowchart TD
A[Need guidance] --> B{Is it about workflow?}
B -->|Yes| C[Daily Development]
B -->|No| D{Is it about code or systems?}
D -->|Yes| E[Technical sections]
D -->|No| F[Playbooks or Checklists]Examples
- Ship a feature: Feature Development
- Fix a bug: Bug Fix Workflow
- Prepare a release: Release Checklist
Checklists
- Open the correct section before starting.
- Follow the linked checklist for the task.
- Add a new page if the workflow repeats.
Senior Engineer Notes
Senior engineers build systems that reduce repeated decision-making. A good home page is a map, not a dump.