Response body — /blogs
Writing about the parts
the documentation leaves out.
Each post is a war story — something I built, broke, fixed,
and didn't want to forget.
Response metadata
WAL Wasn't Enough. Here Is What I Built Instead.
Building a database sync service between two local servers — without delete propagation, without cyclic foreign key failures, and without WAL. A war story about the edge cases nobody warns you about.
How Database Indexes Actually Work: B-Trees, Compound Indexes, and the ESR Rule
An interview question about making search faster sent me down a rabbit hole into B-Trees, compound index internals, and why the order of fields in an index changes everything. Here is what I learned.
I Built a Second Brain and Then Replaced It With Something Better in a Day
How two weeks of managing a custom server taught me to stop reinventing the wheel — and how an MCP server I built in a day replaced all of it.
System Design Should Apply at Every Scale—Including Your Dev Environment
Why I ditched RDS for my personal app, and what that taught me about over-engineered dev environments costing $300+ per cycle.
Why I write
Most engineering content explains how things work when they work. I'm more interested in what happens when they don't — the edge cases, the failure modes, the things you only learn after shipping to production at 11pm on a Friday.
Writing forces me to understand something well enough to explain it without the code in front of me. If I can't, I haven't understood it.