I'm starting to write things down. Not for anyone in particular at first — mostly to force myself to understand the systems I build well enough to explain them. This is the first post, so it doubles as a quick tour of how writing works here.

Why write

Backend work is full of decisions that feel obvious in the moment and mysterious six months later. Writing is how I keep the reasoning around: why a schema looks the way it does, why a queue sits between two services, why a deployment is shaped a certain way.

How these posts work

Each post is a plain Markdown file in src/content/posts/. The filename becomes the URL slug, and the frontmatter at the top supplies the title, summary, date, and read time. Drop a file in, and it shows up — no code changes.

Images use standard Markdown syntax with an absolute path from public/:

The image above lives at public/writing/hello-world-diagram.svg and is referenced as /writing/hello-world-diagram.svg. Export from Obsidian with "Markdown links" turned on and the syntax matches exactly.

What to expect

Short, practical notes — schema design, Docker, CI/CD, and the occasional security CTF write-up. If something here saves you an afternoon, that's a win.

The best way to learn something is to explain it badly, then fix the explanation.

More soon.