If you have been in software development for more than a few years, chances are you have heard of Robert C. Martin, better known as “Uncle Bob.”

Even if you do not recognize the name immediately, your day-to-day work has almost certainly been shaped by his legacy. He organized and popularized the S.O.L.I.D. design principles (00:50). While the individual ideas were not all brand new, he synthesized them into a framework that helped spark a software craftsmanship movement. He was also one of the original signers of the Agile Manifesto (00:50), and the author of staples like Clean Code (00:16) and Clean Architecture (04:20).

If you search for Uncle Bob on YouTube, you will find thousands of talks on craftsmanship, TDD, and software patterns. But a recent conversation caught my attention. In a podcast episode hosted by Kent C. Dodds, titled Architecture, AI agents, and product empathy with Robert C. Martin, Uncle Bob dives into how he is using AI coding agents today.

You can watch the full episode here:

Architecture, AI agents, and product empathy with Robert C. Martin

1. The Shocking Shift: Walking Away from the Code

Coming from the author of Clean Code, one statement was surprising:

“If we are going to get the benefit from these agents, then we are going to have to walk away from the code.” (08:02)

Hearing Uncle Bob say that felt shocking at first. But as he explains, code syntax is simply the latest layer of low-level detail we are rising above (06:26), much like developers once transitioned away from paper tape or hand-crafted assembly language (05:59).

Rather than obsessing over line-by-line syntax, he describes using AI agents to handle low-level implementation while he interrogates system-level structure, module dependencies, and architectural boundaries (08:58).

2. Building Design Sense: Curiosity and Play

When Kent asked how engineers can cultivate better design judgment, a uniquely human skill that AI agents still lack, Uncle Bob offered advice that resonated deeply with me (25:15):

Just play: try things, make mistakes, and stay curious.

To internalize architecture, you have to get your hands dirty (25:56). Build silly tools, write side projects, shape ideas in code, and learn from the friction when something breaks (25:22). Curiosity and experimentation build intuition that no book or prompt can replace.

3. Product Empathy: Bridging IT and the Field

Near the end of the episode, Uncle Bob shared a story from 40 years ago. His manager forced him to get out of the office and spend a day in a repair truck with a field technician testing telephone lines (36:20).

That story highlights what true product engineering is all about: combining technical depth with human empathy (37:40).

In software development, we are often many layers removed from the engineers, technicians, and frontline staff whose daily work creates the need for our systems. It serves both us and our organizations to step into their world, understand real pain points, and design solutions that make their work easier (38:53).

Final Thoughts

Whether you are fully embracing AI agents or still skeptical, hearing one of the founding voices of clean software design share his hands-on workflow and architectural perspective is worth 40 minutes of your time.

Watch the full discussion here: https://youtu.be/RxxxGkFIUJ0