Hi, I’m Ricardo!
Cloud Architect & Systems Engineer who makes tech simple.
I share practical insights on Azure, Kubernetes, and AI, write in-depth guides, and publish the AKS Newsletter every month to help professionals navigate cloud computing with clarity
My superpowers
Azure & Cloud
Step-by-step guides, architecture best practices, and cost optimization tips for Azure.
Kubernetes & AKS
Hands-on labs, troubleshooting tips, and newsletter insights for running workloads at scale.
AI for Infra Pros
Bridging AI concepts with infrastructure, tools, deployments, and performance tuning.
Career & Learning
Stories, mentorship advice, and learning paths for cloud professionals.
Biography
I simplify complex technology for a global audience, blending real-world experience in Azure, Kubernetes, and AI with clear, actionable guidance. My work spans from designing cloud architectures and automation workflows to publishing technical deep dives that help professionals build, scale, and optimize their solutions.
With a passion for teaching, I craft content that connects—whether it’s a blog post, hands-on lab, or newsletter edition. My goal is to empower readers with knowledge they can immediately apply, while inspiring curiosity and continuous learning.
Blog
Over the past year, I’ve been working closely with some of the bigger and more visible AI customers in Microsoft’s ecosystem.Large platforms. Fast-moving teams. High expectations. High stakes. On paper, that kind of visibility sounds exciting.In reality, it comes with a weight that’s hard to explain unless you’ve been there. Because being close to impact
and why that’s not an accident. If you have worked with both Azure and AWS long enough, you have probably felt it. AWS feels straightforward.Azure feels… heavier. Not worse. Not broken. Just harder to reason about. The console feels denser.The mental model feels less obvious.The number of “extra” concepts feels higher. This is not a
For years, “cloud-first” has been treated as a badge of honor. Companies proudly announce that everything is in the cloud, architects optimize for migrations instead of outcomes, and teams equate progress with how little infrastructure they still own. But after working with dozens of real systems, across different industries and at different scales, one thing