WEBVTT

1
00:00:00.040 --> 00:00:03.120
<v Speaker 1>Hey everyone, and welcome back. We're doing a deep dive

2
00:00:03.200 --> 00:00:09.160
<v Speaker 1>today into modern system administration, building and maintaining reliable systems,

3
00:00:09.800 --> 00:00:14.000
<v Speaker 1>and it's a really fascinating look at how, you know,

4
00:00:14.039 --> 00:00:17.399
<v Speaker 1>system administration is changing. It's not just keeping the lights

5
00:00:17.399 --> 00:00:18.000
<v Speaker 1>on anymore.

6
00:00:18.199 --> 00:00:21.239
<v Speaker 2>Yeah, it's not just you know. I mean sometimes it

7
00:00:21.280 --> 00:00:24.440
<v Speaker 2>feels like you're just like keeping the servers running, keeping

8
00:00:24.519 --> 00:00:27.879
<v Speaker 2>the lights on, like you said, But it's much more

9
00:00:27.920 --> 00:00:28.160
<v Speaker 2>than that.

10
00:00:28.640 --> 00:00:32.759
<v Speaker 1>Yeah. This book really drives home the point that modern

11
00:00:32.799 --> 00:00:36.520
<v Speaker 1>sissemens they need a whole new set of skills.

12
00:00:36.600 --> 00:00:39.880
<v Speaker 2>It's a whole different way of thinking about the job. Really. Absolutely,

13
00:00:40.000 --> 00:00:43.920
<v Speaker 2>It's like you're not just reacting to problems anymore. You're

14
00:00:43.960 --> 00:00:49.079
<v Speaker 2>building systems that are like fundamentally more resilient, more reliable.

15
00:00:49.159 --> 00:00:51.520
<v Speaker 1>And that's where this whole idea of version control comes in,

16
00:00:51.560 --> 00:00:53.719
<v Speaker 1>which is like a huge theme in this book.

17
00:00:53.880 --> 00:00:56.479
<v Speaker 2>Yeah, they're big on version control, and you know what,

18
00:00:56.799 --> 00:00:59.679
<v Speaker 2>they should be, right because, I mean, honestly, it's not

19
00:00:59.719 --> 00:01:01.240
<v Speaker 2>just for software developers anymore.

20
00:01:01.600 --> 00:01:05.079
<v Speaker 1>Exactly. This book makes the case that version control is

21
00:01:05.280 --> 00:01:08.120
<v Speaker 1>just as crucial for sissigmind's, if not more so in

22
00:01:08.120 --> 00:01:08.799
<v Speaker 1>some cases.

23
00:01:09.000 --> 00:01:12.640
<v Speaker 2>And there's like actual data to back this up the

24
00:01:12.680 --> 00:01:16.799
<v Speaker 2>door State of DevOps report. They found a super strong

25
00:01:16.920 --> 00:01:21.799
<v Speaker 2>link between using version control and having you know, a

26
00:01:22.000 --> 00:01:24.200
<v Speaker 2>really high performing IT team.

27
00:01:24.519 --> 00:01:26.560
<v Speaker 1>It makes you wonder why we weren't all using it

28
00:01:26.640 --> 00:01:30.920
<v Speaker 1>like yesterday. Remember those times early in your career maybe

29
00:01:30.920 --> 00:01:33.319
<v Speaker 1>where you messed up like just one configuration file.

30
00:01:33.359 --> 00:01:34.319
<v Speaker 2>Oh, tell me about it, and.

31
00:01:34.280 --> 00:01:36.400
<v Speaker 1>You're like scrambling to find a backup.

32
00:01:36.480 --> 00:01:37.200
<v Speaker 2>Oh yeah, and you.

33
00:01:37.159 --> 00:01:39.040
<v Speaker 1>Don't even know how old it is. Well, it's the

34
00:01:39.120 --> 00:01:40.920
<v Speaker 1>right one, and then you realize it's from like a

35
00:01:41.000 --> 00:01:44.040
<v Speaker 1>year ago, and everything's different exactly. Version control is like

36
00:01:44.200 --> 00:01:48.840
<v Speaker 1>having that like that magic undo button for your entire systems.

37
00:01:48.920 --> 00:01:51.359
<v Speaker 2>It's a lifesaver, it really is. It is, and it's

38
00:01:51.400 --> 00:01:55.040
<v Speaker 2>not just about you know, recovering from disasters either. Like

39
00:01:55.400 --> 00:01:58.799
<v Speaker 2>think about when you're onboarding a new team member. Oh yeah,

40
00:01:58.840 --> 00:02:01.439
<v Speaker 2>instead of them having to like wade through a bunch

41
00:02:01.480 --> 00:02:03.760
<v Speaker 2>of old scripts and trying to figure out what does what,

42
00:02:04.079 --> 00:02:06.719
<v Speaker 2>version control gives them that history.

43
00:02:06.799 --> 00:02:10.439
<v Speaker 1>It's like instant documentation almost exactly. Yeah, like a clear

44
00:02:10.520 --> 00:02:12.280
<v Speaker 1>picture of how the system evolved.

45
00:02:12.280 --> 00:02:14.400
<v Speaker 2>It just makes everything so much smoother, And you.

46
00:02:14.360 --> 00:02:17.919
<v Speaker 1>Know, it's really cool this book. It takes version control

47
00:02:18.120 --> 00:02:20.800
<v Speaker 1>way beyond just code. Oh yeah, you're like, why stop

48
00:02:20.840 --> 00:02:24.879
<v Speaker 1>there exactly? Configuration files, scripts, build images.

49
00:02:25.120 --> 00:02:27.800
<v Speaker 2>If it's part of your system, it should be under

50
00:02:27.879 --> 00:02:28.479
<v Speaker 2>version control.

51
00:02:28.520 --> 00:02:30.840
<v Speaker 1>They're like version control everything pretty much.

52
00:02:31.039 --> 00:02:32.879
<v Speaker 2>And it makes sense, right, I mean, you want that

53
00:02:32.919 --> 00:02:33.759
<v Speaker 2>single source.

54
00:02:33.599 --> 00:02:36.400
<v Speaker 1>Of truth, right, so everyone knows exactly what's going on.

55
00:02:36.479 --> 00:02:38.800
<v Speaker 2>No more like oh, which version of this script is

56
00:02:38.800 --> 00:02:39.520
<v Speaker 2>the right one?

57
00:02:39.680 --> 00:02:43.280
<v Speaker 1>Exactly? And then the book it dives into this whole

58
00:02:43.280 --> 00:02:47.560
<v Speaker 1>debate about you know, mona repo versus multi repo.

59
00:02:47.759 --> 00:02:47.960
<v Speaker 2>Ah.

60
00:02:48.039 --> 00:02:50.879
<v Speaker 1>Yeah, I thought was really interesting because at first I

61
00:02:50.919 --> 00:02:52.639
<v Speaker 1>was like, mono repo, that's got to be the way

62
00:02:52.639 --> 00:02:56.520
<v Speaker 1>to go, right. It seems so simpfl like one giant repository.

63
00:02:56.680 --> 00:02:57.520
<v Speaker 1>Everything's in there.

64
00:02:57.599 --> 00:03:00.000
<v Speaker 2>Yeah, one source of truth, super.

65
00:02:59.680 --> 00:03:02.599
<v Speaker 1>Easy, super simple. But then they start talking about you know,

66
00:03:02.639 --> 00:03:04.479
<v Speaker 1>when you've got a huge team, and.

67
00:03:04.400 --> 00:03:09.680
<v Speaker 2>Like it gets complicated. Yeah, imagine like fifty engineers all

68
00:03:09.719 --> 00:03:13.439
<v Speaker 2>working on the same massive repository. Oh yeah, the merged

69
00:03:13.479 --> 00:03:15.319
<v Speaker 2>conflicts alone would be a nightmare.

70
00:03:15.400 --> 00:03:16.120
<v Speaker 1>It'd be crazy.

71
00:03:16.280 --> 00:03:21.360
<v Speaker 2>Suddenly that single source of truth doesn't seem so simple anymore, right,

72
00:03:22.039 --> 00:03:25.800
<v Speaker 2>and even just managing dependencies, oh yeah, like one team

73
00:03:25.879 --> 00:03:28.080
<v Speaker 2>needs this version of a library, another team needs a

74
00:03:28.080 --> 00:03:31.280
<v Speaker 2>different version. It can get messy exactly, And the book

75
00:03:31.280 --> 00:03:34.120
<v Speaker 2>does a good job of like not picking a side.

76
00:03:34.120 --> 00:03:36.199
<v Speaker 2>It's not saying mono repos all these good or multi

77
00:03:36.240 --> 00:03:37.039
<v Speaker 2>repos always bad.

78
00:03:37.159 --> 00:03:37.280
<v Speaker 3>Right.

79
00:03:37.520 --> 00:03:41.439
<v Speaker 2>It really depends on your team, your workflow, your specific needs,

80
00:03:41.560 --> 00:03:44.960
<v Speaker 2>your context exactly. So, like the takeaway for me was,

81
00:03:45.120 --> 00:03:48.199
<v Speaker 2>you know, be intentional about your choice document it, make

82
00:03:48.240 --> 00:03:50.439
<v Speaker 2>sure everyone understands why you're doing what you're doing.

83
00:03:50.520 --> 00:03:53.479
<v Speaker 1>Make sure everyone's on the same page exactly. Yeah. And

84
00:03:53.520 --> 00:03:58.520
<v Speaker 1>beyond just you know, preventing those like disasters, right, lost

85
00:03:58.560 --> 00:04:00.919
<v Speaker 1>work those oh no moments. The book it gets into

86
00:04:00.960 --> 00:04:03.960
<v Speaker 1>these other like amazing benefits of version control.

87
00:04:04.199 --> 00:04:08.199
<v Speaker 2>Oh yeah, but I hadn't really thought about before, like reproducibility.

88
00:04:08.280 --> 00:04:12.280
<v Speaker 1>Reproducibility huge, huge. I mean, if you have good version control,

89
00:04:12.400 --> 00:04:15.680
<v Speaker 1>you can spin up any previous version of your system

90
00:04:16.040 --> 00:04:20.480
<v Speaker 1>like that, like instantly, exactly. So think about testing a

91
00:04:20.519 --> 00:04:25.199
<v Speaker 1>new feature, right, or like debugging a really tricky issue, right,

92
00:04:25.399 --> 00:04:29.759
<v Speaker 1>You can recreate the exact environment from any point in time.

93
00:04:29.959 --> 00:04:32.160
<v Speaker 2>Makes troubleshooting so much easier, so much easier.

94
00:04:32.199 --> 00:04:32.879
<v Speaker 1>It's incredible.

95
00:04:32.959 --> 00:04:35.759
<v Speaker 2>It's like having that rewind button for your infrastructure.

96
00:04:35.839 --> 00:04:38.480
<v Speaker 1>It really is. And I love how the book uses

97
00:04:38.519 --> 00:04:42.560
<v Speaker 1>that analogy of a shared bank account to describe version control.

98
00:04:42.680 --> 00:04:45.160
<v Speaker 2>Oh yeah, that's such a good analogy, right, Like.

99
00:04:45.160 --> 00:04:47.480
<v Speaker 1>Imagine you and I are trying to run a business, right,

100
00:04:47.480 --> 00:04:50.160
<v Speaker 1>We're making deposits, we're taking out money, but there's no

101
00:04:50.319 --> 00:04:51.360
<v Speaker 1>record of any of it.

102
00:04:51.600 --> 00:04:53.279
<v Speaker 2>Chaos, total chaos. Yeah.

103
00:04:53.639 --> 00:04:57.720
<v Speaker 1>But with version control, it's like having that perfect transaction history.

104
00:04:58.120 --> 00:05:01.439
<v Speaker 1>Every change is logged, Who may it, why they made it,

105
00:05:01.519 --> 00:05:04.279
<v Speaker 1>accountability exactly, transparency.

106
00:05:04.360 --> 00:05:07.160
<v Speaker 2>It just makes everything so much more organized and manageable.

107
00:05:07.600 --> 00:05:12.000
<v Speaker 1>So we've like really hammered home how powerful version control is.

108
00:05:12.399 --> 00:05:16.600
<v Speaker 1>But what about actually, you know, putting it into practice. Right,

109
00:05:16.680 --> 00:05:18.879
<v Speaker 1>This book doesn't just tell you to do it.

110
00:05:18.680 --> 00:05:19.399
<v Speaker 2>That shows you how.

111
00:05:19.519 --> 00:05:22.759
<v Speaker 1>They actually give you the like the steps, the tools.

112
00:05:22.560 --> 00:05:26.600
<v Speaker 2>Exactly, and it's written for Sissigmins bi semence.

113
00:05:26.319 --> 00:05:29.560
<v Speaker 1>So it's super practical. And they even get into code reviews,

114
00:05:29.680 --> 00:05:33.519
<v Speaker 1>which can be you know, a bit of a touchy subject. Sometimes.

115
00:05:33.759 --> 00:05:37.079
<v Speaker 1>I've been in those code reviews that are like brutal.

116
00:05:37.279 --> 00:05:39.240
<v Speaker 1>We've all been there where it feels like, you know,

117
00:05:39.319 --> 00:05:42.959
<v Speaker 1>everyone's just picking apart your code and it's not very constructive,

118
00:05:43.079 --> 00:05:45.920
<v Speaker 1>not helpful at all. This book takes a totally different approach,

119
00:05:46.000 --> 00:05:46.720
<v Speaker 1>though They.

120
00:05:46.639 --> 00:05:51.600
<v Speaker 2>Really emphasized that like code reviews should be a learning opportunity. Oh,

121
00:05:51.600 --> 00:05:55.560
<v Speaker 2>it's a chance to share knowledge, to catch potential issues

122
00:05:55.600 --> 00:05:59.079
<v Speaker 2>early on, but in a constructive way. Yeah, it's a

123
00:05:59.120 --> 00:06:00.600
<v Speaker 2>team effort, not a competition.

124
00:06:00.800 --> 00:06:05.000
<v Speaker 1>Yeah, it shouldn't be about, you know, tearing each other down,

125
00:06:05.279 --> 00:06:06.079
<v Speaker 1>exactly right.

126
00:06:06.120 --> 00:06:08.279
<v Speaker 2>And it all comes back to that idea of collaboration.

127
00:06:10.560 --> 00:06:13.959
<v Speaker 2>We're all in this together, and speaking of collaboration and

128
00:06:14.040 --> 00:06:16.839
<v Speaker 2>like just working smarter in general. I love the part

129
00:06:16.879 --> 00:06:21.079
<v Speaker 2>where they talk about setting up a really awesome local

130
00:06:21.120 --> 00:06:24.560
<v Speaker 2>development environment because that can make such a huge difference.

131
00:06:24.759 --> 00:06:28.480
<v Speaker 1>It really can. Having the right tools, the right setup,

132
00:06:28.720 --> 00:06:30.439
<v Speaker 1>it just makes you so much more productive.

133
00:06:30.480 --> 00:06:32.839
<v Speaker 2>And the book goes into detail about like choosing the

134
00:06:32.879 --> 00:06:35.360
<v Speaker 2>right editor, setting up testing frameworks.

135
00:06:35.480 --> 00:06:38.399
<v Speaker 1>It's all about efficiency, righty, making your life easier.

136
00:06:38.720 --> 00:06:41.040
<v Speaker 2>And honestly, I think that kind of sums up what

137
00:06:41.079 --> 00:06:43.519
<v Speaker 2>I love about this book. What's that It's all about

138
00:06:43.560 --> 00:06:48.720
<v Speaker 2>giving cissidminds the tools, the knowledge, the mindset to not

139
00:06:48.800 --> 00:06:52.720
<v Speaker 2>just like survive, but to actually thrive to access in

140
00:06:52.839 --> 00:06:56.519
<v Speaker 2>this like crazy world of ever changing technology.

141
00:06:56.680 --> 00:06:59.279
<v Speaker 3>Because it is constantly changing, you always feel like you're

142
00:06:59.439 --> 00:07:04.199
<v Speaker 3>like playing exactly, but this book it gives you a framework,

143
00:07:04.360 --> 00:07:07.000
<v Speaker 3>a way of thinking about the work that can really

144
00:07:07.000 --> 00:07:10.319
<v Speaker 3>help you stay ahead of the curve. Absolutely, and it

145
00:07:10.360 --> 00:07:12.879
<v Speaker 3>gets you thinking about not just the technical stuff, but

146
00:07:12.920 --> 00:07:14.199
<v Speaker 3>the human element too.

147
00:07:14.319 --> 00:07:16.720
<v Speaker 1>Oh yeah, that's so important, which you know they don't

148
00:07:16.720 --> 00:07:17.800
<v Speaker 1>always teach you about.

149
00:07:17.600 --> 00:07:22.319
<v Speaker 2>In school, No they don't. But as systems become more complex,

150
00:07:22.399 --> 00:07:26.240
<v Speaker 2>as teams get bigger, those soft skills, those human skills,

151
00:07:26.600 --> 00:07:28.000
<v Speaker 2>they become even more important.

152
00:07:28.360 --> 00:07:30.959
<v Speaker 1>Communication, collaboration, all that stuff.

153
00:07:31.040 --> 00:07:34.000
<v Speaker 2>It's not just about the technology anymore. It's about the people.

154
00:07:34.199 --> 00:07:37.040
<v Speaker 1>Yeah, And with that, I think we've done our deep

155
00:07:37.079 --> 00:07:37.839
<v Speaker 1>dive for today.

156
00:07:38.000 --> 00:07:38.759
<v Speaker 2>That was a good one.

157
00:07:38.800 --> 00:07:43.319
<v Speaker 1>We explored this whole world of modern system administration.

158
00:07:42.839 --> 00:07:47.360
<v Speaker 2>Version control. Everything we talked about, version control, local development.

159
00:07:46.959 --> 00:07:49.360
<v Speaker 1>The human side of it all, so much good stuff.

160
00:07:49.480 --> 00:07:52.120
<v Speaker 1>So we hope this episode gave you some things.

161
00:07:51.879 --> 00:07:55.079
<v Speaker 2>To think about, inspired you to maybe try some new things.

162
00:07:54.879 --> 00:07:57.519
<v Speaker 1>Maybe even level up your own Sissenmin game a little bit.

163
00:07:58.160 --> 00:07:58.720
<v Speaker 2>Exactly.

164
00:07:59.000 --> 00:08:02.360
<v Speaker 1>Until next time, happy coding, and mayor systems always be

165
00:08:02.680 --> 00:08:03.279
<v Speaker 1>up and running.