Software architecture, human judgment, and AI's limits with Grady Booch

Kent talks with Grady Booch about what software engineering still means in the age of AI agents, why implementation is only one part of the work, and why human judgment remains central to building durable systems.

They discuss software architecture, the limits of large language models, computable minds, product engineering across different risk and complexity levels, and the kind of curiosity that helps engineers grow beyond a narrow slice of the field.

(00:00) - Introduction to Product Engineering
(01:00) - Grady Booch background
(06:47) - The Last Software Engineer
(09:00) - Will the software industry end?
(10:04) - Consciousness and the computable mind
(20:13) - What is software engineering?
(27:45) - Software architecture and agents
(35:30) - The ceiling for LLMs on implementation
(39:33) - Durable skills and human judgment
(41:39) - Curiosity beyond your domain
(45:47) - Homework: read foreign source code

Grady brings a rare long-view perspective to the AI and software engineering conversation: early computing, Rational Software, UML, IBM Research, NASA work, software architecture, and current research into computing and the human experience. That background gives this episode a useful tension. Kent and Grady do not agree on every framing, especially around whether the software development industry could eventually "end," but they find common ground around judgment, curiosity, and the responsibility engineers have for what they build.

A major theme is that implementation is not the whole of software engineering. Grady breaks the work into a broader journey from imagination to executable artifacts, with computer science, algorithms, architecture, organizational forces, economics, risk, and ethics all shaping the result. Agents and LLMs can help with some of that work, but Grady argues they remain unreliable narrators: useful, fast, and sometimes impressive, while still needing experienced humans who can smell when the work is going off the rails.

The episode closes with a practical challenge for engineers: broaden your judgment by studying systems and ideas outside your usual domain. Read unfamiliar source code. Read books outside your lane. Build the curiosity that gives your technical decisions more context.

Homework

Read the source code for a system that is completely foreign to your usual work.
Use historical or open source systems like MacPaint, MediaWiki, or the Linux kernel to study different constraints and architectures.
Read a book outside your domain, such as The Sciences of the Artificial, Systemantics, or The Society of Mind.

Resources

Guest: Grady Booch

Host: Kent C. Dodds

See on Epic Product Engineer

Fler avsnitt av Become an Epic Product Engineer