CaSE: Conversations about Software Engineering

Adam Tornhill on Software Design X-Rays

Jan 17, 2022

54:32

Creator website

Highlights

AI Chapters

Episode notes

The Single Most Important Thing You Can Do to Fix a Bad Cod

01:38

Why Isn't Your Code Refractory?

02:01

Change Coupling and Clone Detection Tools

02:05

Introduction

2min

The Sign X Rays a Really Interesting Combination

5min

Is There a Priority Aspect?

2min

What Is a Hot Spot?

3min

Is the Inter Interest Rate on Cods a Problem?

3min

Is There Anything You Can Improve?

3min

Using the Trends as an Ote Warning System

2min

Why Isn't Your Code Refractory?

2min

The Single Most Important Thing You Can Do to Fix a Bad Cod

2min

10.

Is There a Problem With Coat?

2min

11.

Ex Ray Analysis - What Is an Ex Ray Analysis?

4min

12.

Change Coupling Is a Soft Analysis Technique

2min

13.

Change Coupling and Clone Detection Tools

2min

14.

Clone Detection

2min

15.

How to Find Out if You Have a Problem

4min

16.

How Do You Show the Coupling?

2min

17.

Change Capting

2min

18.

How to Organize Your Development Teams?

2min

19.

Using Behavior Co Analysis, You Can Visualize That, Right?

2min

20.

Do We Need to Create Better Boundaries?

3min

21.

Is Bavo Coalsis More Important?

2min

22.

How to Fix a Problem in a Complex Architecture?

2min

Sven Johann talks with Adam Tornhill about Software Design X-Rays

This interview was recorded for the GOTO Book Club

Chapter Marks:

0:00 Intro
2:54 Behavioral code analysis
8:53 Hotspot analysis and technical debt
14:42 Trends analysis
21:05 System mastery
24:11 Software Design X-Ray
27:18 The more metrics the better?
30:09 Change coupling
33:19 Copy-paste dilemma
42:40 Change coupling gets more expensive with distance
45:20 Team structure visualized in the code
53:52 Outro

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.