ls ~/writing

Writing

Distributed systems, performance, and the things that only show up once something is actually running. Occasionally what broke while I was fixing something else.

6 November 2026· 6 min
JSON.stringify invented my bug
One debugging line printed a broken filter that never existed. Here is how to spot the trap, why it happens, and what to print instead.
#javascript#debugging#json#mongodb#mongoose
16 October 2026· 5 min
Publish before you delete
A failed repack in go-git could delete the only copy of your commits and still hand you a polite error. The cause was one defer.
#go#git#open-source#data-integrity#defer
6 September 2026· 7 min
Four ways a correct DNS record still looks broken
I put mail on a domain I own. Every record was right within a minute. Getting anything to agree that they were right took the rest of the hour.
#dns#email#networking#deliverability
4 September 2026· 2 min
The 1.1 MB icon font
My portfolio scored 62. I assumed React, or the animations, or too much JavaScript. It was one font file.
#performance#web-vitals#fonts
2 September 2026dev.to ↗
Your .env.example is lying to you: catching config drift in TypeScript
A schema that generates your .env.example, and fails CI when the two disagree.
#typescript#prahari#config
16 August 2026Medium ↗
I Took My Task Queue From a Demo to a Distributed System
Leases, reapers and owner fencing — what it takes to survive kill -9 without losing work.
#distributed-systems#go#redis
17 April 2026Medium ↗
10 TypeScript Pitfalls That Look Correct (But Aren't)
Type-level mistakes that compile cleanly and still bite you at runtime.
#typescript
4 March 2026Medium ↗
I Built a Distributed Task Queue From Scratch to Actually Understand How They Work
Priority queues, retries and dead letters, built the slow way on purpose.
#distributed-systems#go#redis