060: Coping with Complexity with Kent Beck

December 27th, 2017 · 43 mins 2 secs

About this Episode

01:19 – Kent’s Superpower: Putting Things Together That Don’t Necessarily Go Together

Surfaces and Essences: Analogy as the Fuel and Fire of Thinking by Douglas Hofstadter and Emmanuel Sander

04:01 – Metaphors in Software Development

07:32 – Writing Tests and Keeping a Journal

The unit/integration distinction confuses me. I test at the level of, “Here’s a thought I need to capture.”

@KentBeck on @greaterthancode

10:58 – Complexity Partitioning

One Bite At A Time: Partitioning Complexity

Kent’s musings on the topic of unit versus integration testing after the show.

21:59 – The Way Systems Change Over Time as an Important Part of How We Design Software

27:20 – Changing Culture Vs Code and Storytelling and Succession


Jamey: Thinking about the reasons why we do things.

Rein: How computer systems are beginning to take on the complexity of biological systems.

Coraline: The concept of lumpers vs splitters.

Sam: How strategies for dealing with complexity don’t just have to be about the problem itself, they can be about the emotional response of the programmer who has to get some work done.

Jessica: The for-allers vs the for-eachers; universalist vs existentialist.

Kent: Not being bothered by culture change and helping people feel the same.

This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode.

To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.

Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!

Support Greater Than Code