Skip to content
·1 min read

Welcome — and what this place is for

An intro to this site: why it exists, what I'll write here, and what I won't.

This is the part of the internet where I think out loud about software.

Engineering blogs tend to fall into two camps: either the surface-level tutorial (“how to center a div in 2026”) or the impenetrable systems paper. I want to write the thing in between — honest notes from the inside of real projects.

What you’ll find here

  • Post-mortems. Bugs that taught me something. The fix is rarely the lesson.
  • Patterns that held up. Architectures I’d recommend after running them in production for more than a quarter.
  • Tooling. Small notes on the editor, the shell, the deploy pipeline.
  • Opinions. Defended with code, not vibes.

What you won’t

  • Hot takes on framework wars.
  • AI doom or AI hype. I use it; I’ll write about how, not whether.
  • “10 things every senior engineer must know.”

Why a blog, in 2026

Because the half-life of a tweet is hours and the half-life of a good blog post is years. I still find myself searching for posts written in 2014 about PostgreSQL locking. That’s the bar.

If a post here saves one engineer one production incident, it’s earned its hosting bill many times over.

See you in the next one.