Engineering notes
This is a personal engineering knowledge base: a place to turn things I learn, build, debug, and decide into notes I can use again.
The notes favor practical understanding over encyclopedic coverage. Each one should answer one useful question, stay small enough to scan, and contain enough detail to apply the idea without reopening the original research.
What is here​
| Note type | Purpose |
|---|---|
| Concepts | Explain general ideas and mechanisms |
| Tool references | Explain how a specific product or technology works |
| Problem-solutions | Record what failed, why, and how it was fixed |
| Articles | Capture useful ideas from external sources |
| Project learnings | Record discoveries made while building something |
| Decisions | Preserve choices, trade-offs, and consequences |
Notes are grouped by subject. Related theory grows into a topic folder with an overview note and focused child notes. Project-specific material lives under the relevant project.
How notes are made​
capture -> classify -> draft -> review -> approve -> publish -> validate
Notes are drafted with a matching template, reviewed before publication, and checked with
the site build. The repository workflow is documented in
KNOWLEDGE-WORKFLOW.md.
Current focus​
The first rebuilt topic is coding-agent harnesses, including a reference note on OpenCode.