About Me

Who I Am

I'm a Cloud Architect and DevOps Engineer with a focus on building infrastructure that actually scales and teams that can maintain it. I've spent years working with AWS, GCP, and Azure — not just clicking buttons in consoles, but designing systems that survive production.

What I Believe

  • Concepts over code: If you don't understand WHY something works, you can't debug it when it breaks at 3 AM.
  • Document the trade-offs: Every technology choice has downsides. Hiding them doesn't make them disappear.
  • No silver bullets: Kubernetes isn't always the answer. Neither is serverless. Context matters.
  • AI is a tool: It won't replace engineers who understand systems. It WILL replace those who just copy-paste.

Technical Focus

  • Infrastructure as Code: Crossplane, Terraform, AWS CDK
  • Cloud Platforms: AWS (primary), GCP, Azure
  • Kubernetes: EKS, GKE, AKS, and self-managed clusters
  • GitOps: ArgoCD, Flux, and the patterns that make them work
  • Platform Engineering: Building internal developer platforms that developers actually want to use
  • Observability: Prometheus, Grafana, Loki, Tempo — the full stack

Why This Blog

Most cloud content online falls into two categories: either it's marketing material from vendors, or it's tutorials so basic they're useless in production. I wanted to create something different.

Here you'll find:

  • Honest comparisons of tools (including their weaknesses)
  • Production patterns with real-world context
  • Architectural Decision Records (ADRs) that explain the WHY
  • Opinions backed by experience, not hype

Let's Connect

I'm always interested in discussing architecture challenges, debating tool choices, or helping teams level up their infrastructure practices.

"The best infrastructure is the one your team can understand, operate, and evolve — not the one with the most impressive architecture diagram."