I'm a software engineer focused on distributed systems, Apache Kafka, and Kubernetes. My work involves designing and building cloud-native messaging infrastructure, Kafka operators, and multi-cluster architectures.
I enjoy understanding how systems behave under failure, scale, and imperfect network conditions. Most importantly, I like extracting practical lessons from real-world problems and sharing them with the broader engineering community.
Background
Over the past several years, I've had the opportunity to work on large-scale distributed systems at the infrastructure level. This includes:
- Building and operating Kafka clusters across multiple data centers and cloud environments
- Designing Kubernetes-based architectures for stateful applications
- Contributing to open source projects like Strimzi, helping others run Kafka reliably on Kubernetes
- Debugging production issues in complex distributed systems at scale
- Working with teams to migrate from legacy messaging systems to modern Kafka-based architectures
What I Focus On
My technical work is organized around four pillars:
Apache Kafka (50%)
Deep expertise in Kafka internals, architecture, performance tuning, security, operations, and production troubleshooting. Particular focus on real-world problems: migrations, replication failures, networking issues, and performance debugging.
Kubernetes (25%)
Experience building production Kubernetes deployments with emphasis on stateful applications. Expertise in operators, networking, multi-cluster deployments, and cloud-native patterns. Active work with Strimzi Kafka operator.
Distributed Systems (15%)
Understanding of the fundamental concepts that power reliable systems: consensus, replication, failure detection, consistency, and networking. This helps move beyond just knowing tools to understanding principles.
AI for Engineers (10%)
Exploring how AI is changing software engineering: code review, debugging, troubleshooting, and developer tooling. Particularly interested in how AI can help with distributed systems work.
Why I Write
I write about technical topics for a few reasons:
- To clarify my own thinking: Writing forces you to understand things deeply. If I can't explain it clearly, I probably don't understand it well enough.
- To help others avoid mistakes: Many of the problems I've debugged in production are avoidable with the right knowledge. I want to share that knowledge.
- To build a searchable knowledge base: Years from now, I want my past self's solutions to be findable — both for me and for the community.
- To establish credibility through demonstrated work: Credibility comes from showing real expertise, not from claiming expertise.
My Approach to Technical Work
I believe in:
- Deep understanding over surface knowledge: I'd rather understand one system thoroughly than know ten systems superficially.
- Practical lessons over generic tutorials: "How to set up Kafka" is less useful than "Why your Kafka setup failed in production and how to prevent it."
- Systems thinking: Problems rarely exist in isolation. Understanding the broader context matters.
- Reliability and observability: Brilliant systems that fail in production are not brilliant. I prioritize operational reliability.
Experience & Skills
Core Technologies
Apache Kafka, Kubernetes, Strimzi, Distributed Systems, Cloud Native Architecture
Languages
Java, Go, Python, YAML, Bash
Cloud Platforms
AWS, Google Cloud Platform, Microsoft Azure
Tools & Ecosystems
Docker, Prometheus, Grafana, Elasticsearch, Redis, PostgreSQL, etcd
Outside of Work
Building distributed systems by day; trying to understand the universe at its most fundamental level by curiosity. I'm fascinated by the same question that drives my engineering work — how does it actually work? — applied to a much bigger system: the universe itself. Quantum mechanics, relativity, QED, QFT — I find the same sense of wonder in a Feynman diagram as I do in a well-designed distributed protocol.
I believe the fusion of deep technical thinking and genuine curiosity about the world is where the best ideas come from. That instinct to ask why at the most fundamental level is what makes a great engineer — and a great scientist.
Let's Connect
I'm always interested in discussing distributed systems, Kafka architecture, Kubernetes patterns, and real-world engineering challenges. Feel free to reach out: