Go Time: Golang, Software Engineering

The art of the PR: Part 1

Aug 18, 2022
Ask episode
Chapters
Transcript
Episode notes
1
Introduction
00:00 • 4min
2
Go Time Podcast - Go Time Pod
04:11 • 2min
3
What Is a PR? And Why Do We Even Do These?
05:54 • 2min
4
Is There Such a Thing as a Good PR Review?
07:27 • 2min
5
What Is a Pull Request?
09:17 • 2min
6
What Is a Change Log?
10:53 • 2min
7
What Is a PR?
12:35 • 3min
8
Is It Necessary to Build a PR?
15:25 • 2min
9
Do You Have a Follow Up Question?
16:57 • 2min
10
The Number of Commits Is a Good Indicator
18:48 • 4min
11
How to Review a PR?
22:36 • 2min
12
Firehodrant - A Reliability Platform for Every Developer
24:17 • 2min
13
Code Review - The Art of Giving and Receiving Code Reviews
25:49 • 3min
14
Is It a One Sided Street?
28:43 • 3min
15
Do You Review Differently Depending on the Level of the PR?
31:58 • 2min
16
Does It Matter Who Puts the PR In?
33:36 • 2min
17
The Value of a Fresh Perspective
35:28 • 3min
18
Is It Easier to Give Grace to a Review if English Isn't Their First Language?
38:06 • 3min
19
Is It Easier to Work in a Team With a Native Speaker?
40:53 • 2min
20
Do Emojis Help With Your PR?
43:15 • 2min
21
Using Emojis in Jelica
44:45 • 2min
22
Using Emojis in a Pull Request?
46:38 • 2min
23
The One Thing Driving Your Business Productivity With Honeycomb
48:32 • 4min
24
Is There Really an Art to Doing a Good PR?
52:09 • 3min
25
Unpopular Opinion Time
54:47 • 2min
26
Are You a Software Engineer?
56:43 • 2min
27
Go Time Episode #5 - Computer Science vs Software Engineering
58:49 • 3min