About

The story

I used to fix things by changing YAML until the error went away. One evening, on the platform team at Increff, I traced a single packet through a Kubernetes node instead — namespaces, veth pairs, iptables, conntrack, all the way down — and I've never worked the same way since.

That night taught me what I actually enjoy: not using systems, but understanding them. The invisible parts of software — the operating system, the network, the layers underneath every abstraction — are where I want to spend my career.

How I think

I keep asking "why" until I understand what actually happens, instead of stopping at the command or the API. I go deep where it matters, and I've learned the hard way where it doesn't — depth once cost me sleep, meals, and deadlines before I learned to calibrate it. I draw diagrams because that's how I think. I write things down because that's how I understand.

I'm aiming to be a platform engineer — the person who builds the ground other engineers stand on — and specifically not an SRE. I care about the architecture, not the tool of the week, and about building internal platforms reliable enough that the people using them can forget they're there.

Beyond the terminal

I build software for my Rotaract club — a real platform for members, finance, attendance, events, and communication — because good software should take friction off volunteers, not add it. Engineering only matters to me when it quietly improves someone's life.

I'd rather do things properly than do them the way everyone else does. Lately that also means working on how I communicate — presentation, speaking, and writing in the open. I get by in English and Tamil, and I'm slowly picking up Kannada and Hindi.

Here, on this site

Traces are systems followed to the bottom. The Log is my learning in public. The Lab is where things break on purpose. What I'm doing right now lives on /now, and the tools I use on /uses. If you're evaluating me for work, /work has everything in one place.