Why I write here

I build software for a living — specifically the kind that can’t fail quietly. Most of my career has been spent on infrastructure where the stakes are real: AI-powered platforms that have to scale, distributed systems that have to stay up, and security architecture for data that genuinely matters. I’ve done that work across consumer tech, public safety, and healthcare, and the through-line has always been the same taking an ambiguous, high-stakes problem and turning it into an architecture that holds.

This is where I write about that work, and the ideas behind it.

You’ll find a few different kinds of posts here. The first is book reviews — the books that change how I think about systems, design, or leadership deserve more than a star rating, so I write about what stayed with me and where I pushed back. The second is technical writing — notes from the field on infrastructure, distributed systems, and the architectural decisions that look small until they aren’t.

I write partly to think more clearly, and partly because the best parts of this field are the conversations. If something here resonates, or you think I’ve got it wrong, I’d like to hear it.

— Anusha