Writing things down so I actually learn them
Short, specific notes — not tutorials. More get added as the underlying work happens; the ones marked "coming soon" are queued, not filler.
Building REST APIs Other Teams Actually Want to Use
What changes when the consumer of your API is another engineering team, not a frontend you also control.
PublishedWhat MCP Taught Me About Tool Design
Designing for an AI agent as the caller forces a different kind of clarity than designing for a human.
PublishedWhy On-Device: The Privacy Tradeoff Behind SentinelEdge
Treating a constraint as the design driver, not a limitation to work around.
Lessons from GoDaddy
What changed about how I write code once other teams depended on it.
Observability, from the Inside
Working on the platform other engineers reach for during an incident.
Elasticsearch, Query by Query
What I wish I'd known before writing my first production query.
Code Reviews That Actually Teach You Something
The review comments I've kept coming back to.
A Debugging Journal
Specific bugs, root-cause first — the format I trust more than any "I built X" writeup.
FastAPI in Production, Not in a Tutorial
The parts of FastAPI that matter once real teams depend on the service.
A System-Design Walkthrough
Redesigning a real pipeline at 100x scale, whiteboard-format.