The Quiet Resistance to AI

The Overwhelm of AI

A year ago, AI felt like an advantage. Today… it feels like a responsibility. In this episode, I explore how AI hasn’t just added more tools—it has multiplied output. And with that comes a new kind of overwhelm. More to review. More to decide. More to keep up with. We’ve adapted to tech waves before—but this time, the pace is different. The real challenge isn’t building anymore… it’s evaluating. Because when everything moves faster, our thinking struggles to keep up.

The Quiet Resistance to AI

AI tools are rapidly becoming part of software development, yet many experienced engineers remain sceptical. Not because they fear the technology — but because they’ve tried it. In this episode of Systems & Stories, we explore the quiet resistance to AI tools like GitHub Copilot and Claude. Why do some engineers find them transformative while others feel they slow them down? And how might the role of engineers evolve with this change? This isn’t about hype or dismissal. It’s about learning how to use the next layer of engineering leverage wisely.

Exactly As Designed

Sometimes nothing breaks. No alerts. No crashes. No obvious mistakes. And yet, the outcome is irreversible. This episode explores a system that did exactly what it was designed to do — and why that can be the most dangerous kind of failure.

Where Empathy Goes In Systems

Empathy doesn’t disappear at work. It doesn’t suddenly vanish when organizations grow. So where does it go? In this episode of Systems & Stories, we explore it: Systems are built by people who care — yet over time, those same systems begin to feel cold, rigid, and inhuman. If systems are made of people, shouldn’t empathy survive? If you’ve ever felt the gap between how people care — and how systems behave — this one’s for you.

Clean Systems in a Messy Cloud

Cloud architecture is rarely as clean as the diagrams make it look. Real systems grow, responsibilities blur, and the cloud introduces a unique kind of chaos — latency, failures, scaling quirks, and service interactions you never planned for. In this episode, we explore what it actually means to keep systems clean in an environment that is anything but. We talk about the evolution from clean code to clean cloud thinking, the dangers of over-engineering with microservices, and the subtle art of finding boundaries that make systems resilient rather than fragile.