Go Time: Golang, Software Engineering

How to make mistakes in Go

Jul 29, 2021
Ask episode
Chapters
Transcript
Episode notes
1
Introduction
00:00 • 2min
2
How to Make Mistakes in Go
02:29 • 2min
3
What Are Your Favorite Mistakes?
04:05 • 3min
4
Is There a Multi Error?
06:55 • 3min
5
How Common Is This Problem With Custom Error Types?
10:13 • 2min
6
Is There an Antidote to Returning an Interface?
12:07 • 1min
7
I'm Hearing, Mark. You Should Be a Little Bit Louder
13:37 • 2min
8
Is Concurrency Always Faster?
15:13 • 2min
9
The Merge Sort Algorithm Is a Perfect Fit for Concurrency
17:00 • 4min
10
Source Graph - The Ideal State of Software Development
21:06 • 3min
11
Is Concurrency a Good Thing?
24:23 • 2min
12
Go for Slack - Chris James
26:14 • 2min
13
Is There a Language Change That Could Be Made?
28:12 • 2min
14
Do You Like Generics?
29:43 • 2min
15
Generics
31:31 • 2min
16
You Don't Need Channels to Use Go Concurrency, Right?
33:23 • 2min
17
Go Concurrency Is Not Going to Be Your Bottleneck
34:55 • 2min
18
Go for Guides - Is There a Memory Leak?
36:58 • 2min
19
Using Time.After in a Concurrent Application?
38:30 • 3min
20
Can I Use Time After in a Safe Way?
41:14 • 4min
21
Go Modules - I Love It!
44:53 • 2min
22
I Don't Export Packages, Right?
47:19 • 2min
23
Go for Guides and Interfaces Is an Advanced Case, Johnny.
48:59 • 2min
24
The Time for Unpopular Opinions
50:37 • 2min
25
Don't Make as Many Mistakes as Possible
52:11 • 2min
26
Don't Be Paralyzed When You're Learning Something New
54:05 • 2min
27
Yourself Is Not a Mistake
56:06 • 2min
28
How to Avoid 100 Go Mistakes
57:39 • 2min
29
Changelog Podcasts - Ship It, Go Time, and More!
59:19 • 2min
30
The Audio Book Version of Your Book
01:01:09 • 2min