I’ve spent close to two decades working on systems where failure is visible and mistakes are expensive. My work has covered VoIP, real-time systems, backend infrastructure, and the tooling around them. Much of that time has not been spent chasing novelty, but learning where systems bend, where they break, and why simple ideas become complicated at scale.

I care about clarity in code and restraint in design. I ascribe to minimalism, not as an aesthetic, but as a discipline. I choose fewer abstractions, fewer moving parts, and even fewer promises. I am interested in technology that works quietly and earns trust by being predictable rather than impressive.

This site exists as a place to think in public, slowly and deliberately. The writing here reflects ongoing work. Architectural decisions, design trade-offs, failures worth understanding, and ideas that take time to mature. Some pieces are technical and concrete. Others are reflective. All of them are written with care and intent.

I don’t write tutorials, unless they are quirky and non-obvious. I don’t publish hot takes either. If something appears here, it is because I believe it will still be worth reading later, long after the tools change and the noise moves on.

The common thread across everything I work on is longevity. Systems are meant to last. Ideas are meant to compound. Work that can be revisited without embarrassment is worth doing.

If you find something useful here, that’s enough.