

Building actually maintainable software ♻️ (Changelog Interviews #504)
Sep 2, 2022
Chapters
Transcript
Episode notes
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Introduction
00:00 • 5min
How to Build Maintainable Software
05:09 • 3min
The Beginning of the Diverging Path
07:47 • 3min
What Does Maintainability Mean?
10:31 • 4min
What Makes a Maintainable Softwhere?
14:09 • 4min
Is There a Difference Between Unit Testing and Unit Testing?
17:47 • 3min
Technical Debt
20:54 • 5min
The Business Is Not Cared About What It Takes
26:09 • 6min
Is It a Good Idea?
32:01 • 6min
Is Maintenance Engineering a Higher Level Than Product Engineering?
37:37 • 5min
What Is the Relative Value of Maintenance?
42:19 • 2min
Good Code and Maintainable Code Are Not the Same Thing
43:55 • 2min
Go Code Base
46:07 • 3min
Is There a More Scientific Method to Doing a Co Bas?
49:24 • 3min
What's Good in Go Code Bases?
51:57 • 5min
What Makes Go a Good Language for Maintainability?
57:18 • 2min
How to Make Go More Maintainable?
59:21 • 5min
Engineers Need to Be on the Hook for When Something Goes Wrong
01:03:52 • 2min
I Agree, but I'm a Little Bit Lower.
01:05:38 • 3min
The Problem With 14 Perameter Functions in Semantic Versioning
01:08:13 • 4min
Go Time One 96 - The Maintenance Show
01:12:10 • 2min