Sharing my thoughts, one coffee at a time.

The AI revolution, at the time of writing, didn’t arrive like an asteroid crept in like weather. Gradual, persistent, and deeply altering. We woke up one morning and it was here, everywhere: auto completing emails, filtering resumes, writing poetry, grading code, recommending products, forecasting churn. In boardrooms and bedrooms, AI became the silent co-pilot. The buzz was about intelligence. Artificial, general, narrow, super. Debates flared about sentience, risk, regulation. But underneath the hype and hand wringing, a quieter question lingered: What actual value has AI brought us? ...

We’ve been sold a lot of reinvention in the past decade. Cloud-native architectures, Kubernetes-first everything, throw away the old and start clean. But reality is stubborn: enterprises have decades of investment in legacy systems, sprawling VM fleets, bespoke configurations—and yet they’re under pressure to “modernize” yesterday. The problem isn’t just technical. It’s economic. You can’t simply deprecate your previous investments, nor should you. What you can do is rethink your build artifacts. ...

Most companies don’t aspire to build perfect DevOps or cloud engineering teams. They just want the problems solved, quickly, safely, and without hiring dozens of specialists. That’s where Internal Developer Platforms (IDPs) come in: a productized way to give developers self-service deployments, secure environments, and golden paths to production without reinventing the wheel. But IDPs aren’t for everyone. If you’re Netflix, Shopify, or Airbnb, companies where platform engineering is a strategic differentiator, you should architect and manage your own stack. But if you’re a growing SaaS, a retailer modernizing online experiences, or a financial institution moving to the cloud, platform engineering isn’t your business. Shipping features is. ...

Most teams treat sovereign cloud like a logistics problem. Spin up a local region. Wrap it in compliance. Copy the infra. Move the data. Done. But this isn’t about copying and pasting your stack into a new jurisdiction. It’s about accepting a new reality: the cloud is no longer neutral ground. A new law, a new sanction, or a new interpretation of “access” can ripple through your architecture overnight. Sovereignty means, besides control, knowing where your data lives, who can touch it, and what happens if the situation changes tomorrow. ...

There’s a metaphor I keep coming back to when I think about modern cloud development: the vending machine. Think about it. When you walk up to a vending machine, you don’t wonder how it was stocked or who maintains it. You just press a button and get what you need. Fast, predictable, and (usually ;-)) reliable. That’s how the cloud should work. But for most teams, building in the cloud still feels like assembling the vending machine from parts every time you want a snack. You’re setting up infrastructure, configuring pipelines, stitching together services, and navigating endless layers of DevOps complexity. Even with great platforms like AWS, Azure, or GCP, the work behind the scenes can be overwhelming—especially when velocity matters. ...

2025 is all about Agentic AI. Organizations rushing to the digital riverbed for ‘artificial’ gold, only to find themselves observing others trying to yield the same value without the right knowledge and tools. While the (applied) technology has a lot of potential, generating business value out of it is still at very early stages. There are a lot of products who bring DIY Agentic AI capabilities, yet embedding it in an organization and yielding value is where organizations struggle. People simply don’t know how to deal with and oversee ‘it’. Is it a threat? Do I lose control? Will it have a heartbeat? Will it do my dishes? ...