What this is
This is day0ops. A space for writing about the infrastructure that runs underneath everything else: Kubernetes, service mesh, observability, platform engineering, and increasingly, AI infrastructure.
I’ve spent twenty years building distributed systems. Started writing Java and C++, moved into DevOps and SRE, and now work as a Principal Architect helping teams design cloud-native platforms. Along the way, I’ve been on-call at 1am or 2am more times than I’d like to count, debugged networking issues that made no sense, and learned that most production problems come down to configuration, timing, or both.
Why write
Three reasons.
To clarify my own thinking. Writing forces you to be precise. If I can’t explain something clearly, I probably don’t understand it well enough.
To document what I’ve learned. The best debugging sessions and architecture decisions deserve more than a Slack thread that disappears in six months.
To contribute back. I’ve learned a lot from other engineers sharing their work. This is my attempt to do the same.
What to expect
Posts will cover:
- Infrastructure and platform engineering — Kubernetes, Istio, Cilium, GitOps, and the operational reality of running distributed systems
- AI infrastructure — what it actually takes to run LLMs and agentic systems in production
- Incidents and debugging — real problems, how they were solved, and what went wrong
- Software engineering — architecture patterns, API design, and the craft underneath the tools
No fixed schedule. I’ll write when there’s something worth saying.
Get in touch
Find me on GitHub, X/Twitter, or LinkedIn.
Thanks for reading.