Personal technical notebook
Engineering notes, kept useful.
Observations on software, systems, and the small decisions that make them easier to understand and operate.
Latest notes
Short records of what worked, what did not, and which details will matter again.
-
→
Keeping small systems legible
A system can be small and still be difficult to reason about. A few habits keep its shape visible.
-
→
Measure before tuning
Useful performance work begins with a question, a boundary, and a repeatable observation.
-
→
Reducing moving parts
Complexity is often introduced one reasonable decision at a time. Removing it works the same way.
Working principles
A small set of defaults for building things that can still be understood after the first version.
-
01
Measure the real thing
Start with an observable question before choosing a tool or an optimization.
-
02
Prefer fewer layers
Every layer should earn its place by making the system clearer or more dependable.
-
03
Write down the why
Commands expire quickly. The reason behind a decision stays useful much longer.