blog
Notes on systems, infrastructure, and whatever I'm figuring out.
-
The phone number was flagged before we ever used it
Recycled phone numbers carry the previous owner's spam reputation. We couldn't fabricate a status, so we linked out to Truecaller instead, which meant reverse-engineering an undocumented Android deep link with adb.
-
The slow page wasn't the database
A dashboard page was slow to load, so everyone reached for the database. The real cost was the code drawing one dropdown 400 times. A story about N+1 queries and the fix that took them from 400 to 4.
-
You can't un-bounce an email
An AWS suspension taught me that email deliverability is a reputation system. Here is what actually moves it: bounce thresholds, the hard ceiling on address verification, and why clean lists still land in spam.
-
Extending Uptime Kuma: 90-day heartbeats, a Slack command, and shipping a fork
Getting an unmerged feature into production, adding a Slack /incident command, and open-sourcing the result as a clean fork.
-
Driving a whole voice-AI platform from a single prompt
Building OmniDimension's MCP integration layer: two services, 49 tools, an OAuth 2.1 server, shipped to npm and live in production.
-
Our computers don't really know what time it is
A trip down the rabbit hole of quartz crystals, cesium atoms, GPS, NTP, and PTP, after chrony told me my clock was running slow.
-
Most modern mail tooling is two binaries with a UI on top
Configuring a multi-tenant mail server from scratch with Postfix and Dovecot, now handling 200k+ emails a day.
-
What actually makes an AI agent "agentic"
Agentic AI isn't a new model, it's an LLM wired to a loop: plan, act, observe, repeat, until a goal is met instead of a single reply.
-
A backend take-home, and the two bugs that taught me more than the task
A FastAPI service that stores stock prices, serves them over a REST API, and backtests a moving-average crossover strategy, containerized end to end. Two bugs taught me more than the assignment did.