About Me

I optimize for maintenance, not hype.

Software engineering is an exercise in managing complexity. I build systems that survive the initial commit—pipelines that are idempotent, APIs that are predictable, and infrastructure that fails gracefully. With 5 years of production experience, I’ve learned that the most impressive code is the kind you don't have to wake up at 3 AM to fix.

My work sits at the intersection of data engineering and distributed backends. I don't just move data; I ensure its correctness, consistency, and availability. From tuning PostgreSQL query plans to architecting resilient Kafka streams, I focus on the "boring" engineering that keeps businesses running.

I write to clarify my thinking and contribute to the community. When I'm not in a terminal, I'm usually behind a camera or reading poetry, finding patterns in the world just as I do in code.

My Philosophy

I write code that works and is easy to understand. I focus on solving problems simply rather than overcomplicating things.

I enjoy working through hard problems and learning from them. I like to keep things straightforward and practical.

I work best as a individual contributer and at times with teams too. I value clear communication and different viewpoints. I believe in creating an environment where people can share ideas openly.