Go Time: Golang, Software Engineering

Building actually maintainable software

Sep 9, 2021
Ask episode
Chapters
Transcript
Episode notes
1
Introduction
00:00 • 2min
2
Go Time - Part Two
02:24 • 3min
3
How to Build Maintainable Software
04:57 • 3min
4
The Diverging Tensions
07:58 • 3min
5
What Does Maintainability Mean?
10:54 • 4min
6
What Makes Amtatil Cox Great?
14:32 • 4min
7
Is There a Difference Between Unit Testing and Unit Testing?
18:10 • 3min
8
Technical Debt
21:16 • 5min
9
Is Your Code Base Maintainable?
26:03 • 6min
10
Keeping the Soft War Alive, Right?
31:56 • 6min
11
Is Maintenance Engineering a Higher Level Than Product Engineering?
37:26 • 3min
12
What Is the Relative Value of Maintenance?
40:18 • 2min
13
Good Code and Maintainable Code Can Be Separated
41:50 • 2min
14
Using Go Code Bases, It's Like, Okawilf
44:03 • 3min
15
Is There a Scientific Method to Doing a Co Bas?
47:19 • 3min
16
What's Good in a Romance Novel?
49:55 • 5min
17
What Makes Go a Good Language for a Building?
55:14 • 2min
18
Go Code
57:14 • 5min
19
Engineers Need to Be Exposed to the Layers of the Stack
01:01:52 • 2min
20
Security Engineering - Shouldn't Use Sementic Versioning for Any Versioning System?
01:03:35 • 3min
21
Code Pyramid
01:06:21 • 4min
22
Go Time on the Change Log
01:10:06 • 2min