Go Time: Golang, Software Engineering

SOLID Go Design

5 snips
Sep 8, 2016
Ask episode
Chapters
Transcript
Episode notes
1
Introduction
00:00 • 4min
2
ARM Platforms and Scaleway - What's Next?
03:38 • 2min
3
How Does Dave Chaney Make More Time in a Day?
05:56 • 5min
4
Thinking About Design
10:35 • 4min
5
Is There a Mature Model for Go?
14:30 • 2min
6
Code Review
16:14 • 2min
7
The Gang of Four Patterns Book
18:12 • 3min
8
The Metal Language to Talk About Algorithms
21:28 • 3min
9
The Standard Library Is a Double Age Sword
24:10 • 2min
10
GopherCon Live Streaming Sponsor Backtrace
26:21 • 2min
11
Go for Con - You've Got Your Own Package to Help With Error Handling
27:55 • 5min
12
Is Temporary Check a Good Idea?
32:58 • 2min
13
Is It Possible to Retry a Program?
35:18 • 5min
14
Using the Error Value to Annotate Extra Information
40:09 • 2min
15
How to Handle an Error Not Equal to Nil
41:47 • 3min
16
Do You See Value in Structured Logging?
45:06 • 3min
17
Structured Logging in Distributed Application Tracing
48:22 • 4min
18
Is Your Logging Too Much?
52:41 • 2min
19
Is There a Cardinal Rule?
54:22 • 2min
20
The Problem With Debugging Service Software
56:01 • 4min
21
Interfaces and Go
59:55 • 4min
22
Go for Con - Katrina Stocka's Talk Was Fantastic
01:04:10 • 2min
23
Is There a Better Synchronizer?
01:06:30 • 2min
24
The Silver Searcher
01:08:40 • 3min
25
Askey Doctor
01:11:18 • 3min