I started coding because I was fascinated by how small text files could control machines. That fascination never left — it just became more refined. These days I spend most of my time thinking about concurrency, data consistency, and API contracts.

My engineering philosophy is simple: build for the person who's going to debug your code at 2 AM (usually future-me). That means comprehensive logging, defensive error handling, and systems that fail loudly rather than silently.

Outside of work I write about distributed systems, contribute to open-source tools, and occasionally win arguments about database indexing strategies at coffee shops.