RSS

Why I Write About Systems That Break

October 1, 2025

Why this blog exists

Production systems fail in ways that documentation never covers. Over 6+ years of building and operating distributed systems, the most valuable lessons I have learned came from real outages, real architectural trade-offs, and real debugging sessions. This blog is where I write those lessons down.

I cover three areas:

  • Distributed systems and reliability. Deep dives into outages and RCAs from companies like AWS and Cloudflare, breaking down what went wrong, why recovery was hard, and what we can take from it.
  • AI agent architectures. Building AI agents from scratch in TypeScript, covering tool routing, multi-step orchestration, and production readiness.
  • Backend engineering at scale. The decisions and patterns that matter when your system handles millions of users, processes payments globally, or needs to stay up at 3am.

Most engineering blogs stay surface-level. I aim for the opposite. Every post goes deep enough that you walk away understanding not just what happened, but why.

Blogs I read and recommend

These writers set the standard for the kind of technical depth I am aiming for: