Why I’m writing in public
A small corner of the web for durable notes about software, systems, and the craft of building.
Most useful engineering lessons do not arrive as grand revelations. They show up as a naming decision that makes the next change obvious, a production incident that exposes a hidden assumption, or a small tool that removes friction from a daily loop.
This site is where I plan to keep those lessons.
What belongs here
I’ll write about the work behind the work: how systems are shaped, why interfaces feel clear or confusing, and what makes a codebase hospitable over time.
That likely means notes on:
- software architecture without ceremony
- web interfaces and product details
- tools that improve a developer’s feedback loop
- mistakes, tradeoffs, and the reasoning behind a decision
Why MDX
The posts live beside the code as MDX. Most articles can stay plain Markdown, while the occasional interactive explanation can import an Astro or Alpine-powered component directly:
import Demo from "../../components/mdx/Demo.astro";
<Demo />That keeps the default simple without putting a ceiling on what an article can become.
Start small, keep going
There is no publishing machine here. Just a place to think carefully, explain clearly, and leave useful artifacts behind.