About Me

I’m a technical architect and backend engineer who enjoys turning messy, real-world problems into clean, reliable systems. Most of my work lives in the JVM world—Scala, Java, functional programming, distributed services—and I care a lot about code that is simple, observable, and actually shippable.

I started as a developer who just wanted things to work faster and break less. Over the years, I’ve worked on APIs, high-throughput services, and enterprise platforms, learning how architecture, infrastructure, and product fit together. I enjoy designing systems end-to-end: from data models and contracts to deployment, monitoring, and failure handling.

“I love building systems that are boring in production and exciting on the whiteboard—stable for users, challenging for my brain.”

I like monoliths that are well-designed, microservices that are truly justified, and teams that value clarity over buzzwords. My default mode is: understand the real constraint, pick a pragmatic solution, measure it, then iterate.

Alongside my day job, I mentor developers, write about system design and backend engineering, and experiment with side projects in Scala, Rust, and AI/LLMs. Teaching and documenting what I learn keeps me honest and forces me to think more clearly.

I’m especially interested in performance, reliability, and developer experience: good logging, useful metrics, sensible abstractions, and tools that make teams faster instead of busier. I enjoy working with people who ask hard questions, challenge assumptions, and still get things done.

Outside of code, you’ll usually find me in a gym, with a notebook planning the next project, or refining ideas for writing—whether it’s about escaping the middle-class mindset, career growth, or technical deep dives.

This site is where I share what I learn, what I build, and sometimes what I break along the way.