Engineering Handbook
Overview
This vault is a practical frontend engineering operating system for day-to-day work in React, Next.js, TypeScript, Node.js, and production delivery.
Why It Matters
Good engineers do not rely on memory alone. A handbook makes decisions repeatable, reviews sharper, and debugging faster.
Core Concepts
- Foundations explain how to think.
- Daily Development covers the workflows you use most.
- Frontend, Backend Knowledge, and Architecture capture technical depth.
- Testing, DevOps, AI Development, Career, Checklists, and Playbooks turn knowledge into action.
Mental Models
Treat this as a living wiki, not a notebook. Each page should answer “what is this, when should I use it, and what should I avoid?”
Best Practices
- Keep pages concise and scannable.
- Link related docs instead of repeating the same explanation.
- Prefer practical examples over theory.
Common Mistakes
- Writing disconnected notes.
- Over-explaining basics.
- Letting one-off debugging knowledge stay trapped in a terminal buffer.
Trade-offs
This vault favors usefulness over completeness. Short, opinionated docs are better than a giant unread reference.
Decision Framework
flowchart TD
A[Need an answer] --> B{Is it a daily workflow?}
B -->|Yes| C[Open Daily Development]
B -->|No| D{Is it technical depth?}
D -->|Yes| E[Open the relevant technical section]
D -->|No| F[Open Checklists or Playbooks]Examples
- Debug a production issue with Debugging.
- Review a PR with Pull Requests.
- Make an architecture call with Decision Making.
Checklists
- Find the topic page first.
- Add the missing context before editing code.
- Link new pages from related documents.
Senior Engineer Notes
Senior engineers optimize for clarity, leverage, and consistency. A good handbook reduces cognitive load for future-you and teammates.