Field notes
Notes from under the hood.
Short, useful thinking for engineers who want to understand the systems they build, not just make them pass today.
Caching · 6 min read
The question underneath “Should we use Redis?”
Before picking a tool, name the latency, load, cost, or consistency problem you are actually solving.
Career · 5 min read
Learning backend engineering in public
Build a compounding practice around projects, writing, and the questions that keep you curious.
Architecture · 8 min read
The overlooked work of naming boundaries
A system gets easier to change when its boundaries reflect the jobs it truly has to do.
Operations · 7 min read
What an incident teaches you about design
Postmortems are not paperwork. They are one of the best inputs for the next system decision.
Built to grow
A structure that can hold the whole backend stack.
Built for ongoing publishing
Each starter route is designed to expand into articles, explainers, and visual deep-dives without changing the site structure.
SEO-friendly from day one
Every route ships with metadata, crawlable content, and stable internal links so the site can grow with the library.
Made for backend thinking
The layout keeps the editorial feel while leaving room for diagrams, flows, and interactive models later.