WEBVTT

1
00:00:00.080 --> 00:00:02.020
- Join us at The Hedge for a conversation

2
00:00:02.159 --> 00:00:03.060
- about engineering,

3
00:00:03.439 --> 00:00:04.819
- technology, and business.

4
00:00:05.120 --> 00:00:08.240
- In this episode, Russ White, Tom Ammon, and

5
00:00:08.240 --> 00:00:09.059
- David Barroso

6
00:00:09.439 --> 00:00:12.500
- dig into programming fundamentals for network engineers.

7
00:00:23.964 --> 00:00:25.885
- Well, hello, Phil. You have put up a

8
00:00:25.885 --> 00:00:28.019
- lot of stuff in your little home office

9
00:00:28.260 --> 00:00:28.920
- studio since

10
00:00:29.380 --> 00:00:31.220
- the last time I've seen it. Look at

11
00:00:31.220 --> 00:00:31.880
- all that

12
00:00:32.340 --> 00:00:34.500
- foam on the walls. I don't know. I

13
00:00:34.500 --> 00:00:36.179
- may have to up my game a little

14
00:00:36.179 --> 00:00:37.560
- bit. And David,

15
00:00:38.100 --> 00:00:40.260
- where are you physically located, David? Just so

16
00:00:40.260 --> 00:00:41.594
- that our listeners have a

17
00:00:42.554 --> 00:00:44.495
- sense of who we have on.

18
00:00:46.075 --> 00:00:48.655
- I'm located in in Stockholm, Sweden.

19
00:00:49.195 --> 00:00:52.414
- Oh, okay. Scotland. Oh, that's really cool. Stockholm.

20
00:00:52.875 --> 00:00:54.954
- Oh, Stockholm. Sweden. Okay. I thought you said

21
00:00:54.954 --> 00:00:55.454
- Scotland.

22
00:00:55.960 --> 00:00:57.500
- Okay. Yeah. So Stockholm,

23
00:00:58.200 --> 00:01:00.200
- you know, I've never been to Stockholm, actually.

24
00:01:00.200 --> 00:01:01.559
- I worked for Ericsson. They tried to get

25
00:01:01.559 --> 00:01:03.000
- me to come to Stockholm on a regular

26
00:01:03.000 --> 00:01:05.159
- basis, and I never ended up going. But,

27
00:01:05.159 --> 00:01:06.459
- yeah, that's cool. Good.

28
00:01:07.079 --> 00:01:08.920
- Nice place from what I understand, but very

29
00:01:08.920 --> 00:01:09.420
- cold.

30
00:01:10.635 --> 00:01:13.194
- Oh, right now it's quite cold. Yes. It's

31
00:01:13.194 --> 00:01:15.135
- it's it's very nice during summer.

32
00:01:15.834 --> 00:01:17.674
- Okay. Very nice in the summer. I like

33
00:01:17.674 --> 00:01:18.734
- the way you do that.

34
00:01:21.194 --> 00:01:21.694
- Well,

35
00:01:21.995 --> 00:01:23.755
- if you're into the country skiing and things

36
00:01:23.755 --> 00:01:25.619
- like that, it's also great during winter. I'm

37
00:01:25.619 --> 00:01:27.959
- I'm not a a snow person, so

38
00:01:28.500 --> 00:01:30.119
- I'd rather stay here in summer.

39
00:01:30.500 --> 00:01:31.780
- I have a lot of friends who live

40
00:01:31.780 --> 00:01:32.920
- in Nook, Greenland,

41
00:01:33.379 --> 00:01:35.540
- and I always wonder about them. You know?

42
00:01:35.540 --> 00:01:36.200
- It's like,

43
00:01:38.685 --> 00:01:40.524
- you really have to love winter sports to

44
00:01:40.524 --> 00:01:42.864
- live in Nook, Greenland somehow or another.

45
00:01:44.924 --> 00:01:47.584
- It's okay. It's kind of crazy. But anyway,

46
00:01:48.045 --> 00:01:49.984
- so David, we're talking about

47
00:01:50.680 --> 00:01:53.079
- network engineers and programming. So, you know, we

48
00:01:53.079 --> 00:01:55.159
- started before the recording talking a little bit

49
00:01:55.159 --> 00:01:57.319
- about your background. It might be good to

50
00:01:57.319 --> 00:02:00.359
- fill readers, listeners. Readers, where am I today?

51
00:02:00.680 --> 00:02:02.599
- Anyway, it might be good to fill listeners

52
00:02:02.599 --> 00:02:03.704
- in on that a little bit,

53
00:02:04.265 --> 00:02:06.105
- as to what your background is so they

54
00:02:06.105 --> 00:02:08.344
- have a sense of your experience in that

55
00:02:08.344 --> 00:02:08.844
- space.

56
00:02:09.625 --> 00:02:11.405
- So my background is,

57
00:02:11.944 --> 00:02:14.365
- network engineering. So I've been working at,

58
00:02:15.145 --> 00:02:17.564
- like, service providers, like NTT, for instance.

59
00:02:18.650 --> 00:02:19.709
- And then around

60
00:02:20.090 --> 00:02:21.629
- five years ago, I

61
00:02:21.930 --> 00:02:24.590
- jumped into, like, full time,

62
00:02:25.370 --> 00:02:27.610
- programming in the networking space. So I have

63
00:02:27.610 --> 00:02:29.629
- a lot of experience in both programming

64
00:02:30.009 --> 00:02:31.085
- and as a network

65
00:02:32.824 --> 00:02:34.764
- operator. Okay. Awesome. Great.

66
00:02:35.145 --> 00:02:35.645
- So

67
00:02:36.025 --> 00:02:37.784
- let's just start with a simple question. Why

68
00:02:37.784 --> 00:02:39.544
- do network engineers need to learn to code

69
00:02:39.544 --> 00:02:41.544
- or need need to have programming skills? I

70
00:02:41.544 --> 00:02:43.224
- should say, I should not say learn to

71
00:02:43.224 --> 00:02:44.824
- code because I think there is a difference

72
00:02:44.824 --> 00:02:46.930
- between having programming skills

73
00:02:47.229 --> 00:02:47.729
- and

74
00:02:48.189 --> 00:02:50.509
- being a full on coder. So let's just

75
00:02:50.509 --> 00:02:52.349
- start with why is it important for network

76
00:02:52.349 --> 00:02:55.090
- engineers to have, coding or programming skills?

77
00:02:56.430 --> 00:02:57.729
- I think mostly

78
00:02:58.189 --> 00:02:58.689
- because,

79
00:03:00.245 --> 00:03:02.245
- I mean, if you look at the type

80
00:03:02.245 --> 00:03:04.245
- of networks that we manage, like, ten years

81
00:03:04.245 --> 00:03:05.925
- ago, like, we would have, like, a, I

82
00:03:05.925 --> 00:03:07.604
- don't know, like, a few switches, a few

83
00:03:07.604 --> 00:03:09.604
- routers. Like, you could count them in the

84
00:03:09.604 --> 00:03:10.584
- in the dozens.

85
00:03:11.444 --> 00:03:14.000
- And so everything was more or less manageable,

86
00:03:14.780 --> 00:03:17.180
- like, for a human to to deal with

87
00:03:17.180 --> 00:03:18.639
- with everything. Like, nowadays,

88
00:03:19.099 --> 00:03:21.739
- like, everything is super fast paced. Like, you

89
00:03:21.739 --> 00:03:23.819
- need to do changes super fast because of

90
00:03:23.819 --> 00:03:26.219
- the cloud and and other things, and you're

91
00:03:26.219 --> 00:03:28.085
- also managing, like, way more

92
00:03:28.465 --> 00:03:29.764
- devices, like, one, two,

93
00:03:30.064 --> 00:03:31.525
- even three orders of magnitude,

94
00:03:32.944 --> 00:03:33.444
- higher.

95
00:03:33.824 --> 00:03:35.365
- So it's a matter of

96
00:03:35.665 --> 00:03:37.665
- being able to to do your job to

97
00:03:37.665 --> 00:03:39.745
- begin with. And then secondly, there are also

98
00:03:39.745 --> 00:03:40.485
- other benefits.

99
00:03:41.800 --> 00:03:42.300
- Consistency,

100
00:03:43.400 --> 00:03:43.900
- and

101
00:03:44.199 --> 00:03:46.439
- if you get speed, you manage to... You

102
00:03:46.439 --> 00:03:48.120
- can also free up your time to do

103
00:03:48.120 --> 00:03:51.099
- more interesting stuff instead of just, like, firefighting

104
00:03:51.159 --> 00:03:53.580
- and deploying villains and firewall rules.

105
00:03:53.879 --> 00:03:56.055
- So I think there are several reasons, not

106
00:03:56.055 --> 00:03:57.435
- just one, to be honest.

107
00:03:57.814 --> 00:03:59.495
- Yeah. I I would actually add to that

108
00:03:59.495 --> 00:04:00.875
- personally. I think knowing...

109
00:04:01.175 --> 00:04:03.735
- Having programming skills and even to the point,

110
00:04:03.735 --> 00:04:05.574
- I mean, my my second language... People ask

111
00:04:05.574 --> 00:04:07.335
- me what my second language is sometimes. I'm

112
00:04:07.335 --> 00:04:09.129
- in a PhD program and they're like, oh,

113
00:04:09.129 --> 00:04:10.889
- what are the languages you study? And I

114
00:04:10.889 --> 00:04:12.969
- always say, Si. And they don't make the

115
00:04:12.969 --> 00:04:14.669
- joke. But anyway,

116
00:04:17.290 --> 00:04:19.449
- you know, they're expecting Greek, Latin, or German.

117
00:04:19.449 --> 00:04:20.829
- And I'm always like Si.

118
00:04:21.245 --> 00:04:23.024
- Like, is that a language? Yeah.

119
00:04:24.365 --> 00:04:24.865
- Anyway,

120
00:04:25.324 --> 00:04:28.125
- so I think it's important as well because

121
00:04:28.125 --> 00:04:30.444
- it's a mindset. Right? I mean, it's a...

122
00:04:30.444 --> 00:04:32.944
- Programming or coding is a different mindset.

123
00:04:33.404 --> 00:04:35.480
- I was talking to Alastair Woodman,

124
00:04:36.100 --> 00:04:37.779
- nobody else. Well, I think Phil might know

125
00:04:37.779 --> 00:04:39.860
- Alastair a little bit. But... And he was

126
00:04:39.860 --> 00:04:41.300
- saying, you can always tell the difference between

127
00:04:41.300 --> 00:04:43.139
- a good coder and a bad coder because

128
00:04:43.139 --> 00:04:45.220
- a good coder works with tools. They build

129
00:04:45.220 --> 00:04:47.379
- their own tools. It's like a carpenter. They

130
00:04:47.379 --> 00:04:49.415
- have all these tools that they use. And

131
00:04:49.415 --> 00:04:51.654
- then the really bad coders, or the coders

132
00:04:51.654 --> 00:04:53.175
- who don't really know what they're doing, they

133
00:04:53.175 --> 00:04:54.855
- just use things raw, just like they are.

134
00:04:54.855 --> 00:04:56.775
- Right? They just pop the slider up in

135
00:04:56.775 --> 00:04:58.855
- factory default position, and they just do whatever

136
00:04:58.855 --> 00:05:01.175
- they're going to do. Whereas, good coders are

137
00:05:01.175 --> 00:05:03.689
- always customizing their environment and building tools to

138
00:05:03.689 --> 00:05:05.970
- help them. I think those kinds of mindset

139
00:05:05.970 --> 00:05:08.610
- things are really, really helpful even for network

140
00:05:08.610 --> 00:05:09.110
- engineers.

141
00:05:10.610 --> 00:05:13.250
- Yeah. Even just computational thinking as a skill

142
00:05:13.250 --> 00:05:15.029
- set in itself is super helpful

143
00:05:15.584 --> 00:05:18.564
- in approaching networking problems, other problems.

144
00:05:18.944 --> 00:05:21.584
- My... I'm not very affluent in programming yet.

145
00:05:21.584 --> 00:05:23.824
- I know basically just Python and some Java,

146
00:05:23.824 --> 00:05:24.324
- but,

147
00:05:25.264 --> 00:05:25.925
- my journey

148
00:05:26.225 --> 00:05:28.064
- into that even has helped me understand the

149
00:05:28.064 --> 00:05:29.579
- systems that are operating on top of the

150
00:05:29.579 --> 00:05:32.060
- network a lot better and, has increased my

151
00:05:32.060 --> 00:05:33.919
- ability to troubleshoot and resolve issues.

152
00:05:35.819 --> 00:05:38.939
- Yeah. Interesting. So so I guess that segues

153
00:05:38.939 --> 00:05:40.079
- into the next question.

154
00:05:40.540 --> 00:05:42.725
- So if you're gonna learn programming skills,

155
00:05:43.345 --> 00:05:45.345
- what languages should you learn? What should you

156
00:05:45.345 --> 00:05:46.725
- do? Any ideas, David?

157
00:05:47.584 --> 00:05:49.685
- That's gonna depend a bit on your,

158
00:05:51.185 --> 00:05:53.264
- like, on your on your field. In the

159
00:05:53.264 --> 00:05:53.764
- network

160
00:05:54.384 --> 00:05:57.319
- world, the main one would be Python. Like,

161
00:05:57.319 --> 00:05:58.939
- there is a library for almost

162
00:05:59.560 --> 00:06:00.779
- everything network related,

163
00:06:01.399 --> 00:06:02.860
- and it's also what's getting,

164
00:06:03.639 --> 00:06:04.379
- most traction,

165
00:06:05.800 --> 00:06:08.599
- in our communities. So Python, like, without any

166
00:06:08.599 --> 00:06:09.099
- doubt.

167
00:06:09.479 --> 00:06:11.845
- And Golang would be also also a a

168
00:06:12.064 --> 00:06:14.865
- good option, but that has a bit of...

169
00:06:14.865 --> 00:06:15.365
- There's...

170
00:06:15.824 --> 00:06:17.345
- The community is not that big there in

171
00:06:17.345 --> 00:06:19.365
- the networking space yet, so I would

172
00:06:19.904 --> 00:06:21.444
- I would say, Python.

173
00:06:23.105 --> 00:06:25.569
- Interesting. Do you see Golang growing as a

174
00:06:25.569 --> 00:06:27.830
- language that's used in the network automation space?

175
00:06:28.529 --> 00:06:30.550
- I I think so. I'm actually

176
00:06:30.930 --> 00:06:34.050
- doing, like, at at work, for instance, everything

177
00:06:34.050 --> 00:06:37.009
- I do nowadays is, is Golang. Like, there

178
00:06:37.009 --> 00:06:39.845
- are a few reasons for for that. Like,

179
00:06:40.384 --> 00:06:42.404
- my main reasons would be, like,

180
00:06:42.944 --> 00:06:46.225
- speed. Like, colon is way faster than, than

181
00:06:46.225 --> 00:06:46.725
- Python.

182
00:06:47.504 --> 00:06:48.245
- And, also,

183
00:06:49.024 --> 00:06:50.404
- because it's statically

184
00:06:50.730 --> 00:06:51.230
- typed,

185
00:06:53.210 --> 00:06:55.069
- the code tends to be more reliable.

186
00:06:55.370 --> 00:06:57.290
- Like, there's no way that you can pass

187
00:06:57.290 --> 00:06:58.750
- the wrong type to a function,

188
00:06:59.050 --> 00:07:01.850
- and then everything just explodes, which is kind

189
00:07:01.850 --> 00:07:03.550
- of a common problem in,

190
00:07:04.475 --> 00:07:05.995
- in Python. So I think long term... And

191
00:07:05.995 --> 00:07:07.274
- when I say long term, I mean, like,

192
00:07:07.274 --> 00:07:08.955
- I don't know, like, maybe ten years. I

193
00:07:08.955 --> 00:07:09.694
- think Golang

194
00:07:10.014 --> 00:07:10.514
- is

195
00:07:10.835 --> 00:07:11.335
- maybe,

196
00:07:12.475 --> 00:07:15.274
- in the position that Python is, today and

197
00:07:15.274 --> 00:07:16.654
- Python may be the

198
00:07:16.955 --> 00:07:18.495
- the the pearl of today

199
00:07:18.795 --> 00:07:20.470
- for people who makes fun of pearl.

200
00:07:21.250 --> 00:07:23.569
- Yeah. Interesting. But it... So it... It's hard

201
00:07:23.569 --> 00:07:25.490
- to predict in ten years, but that... That's

202
00:07:25.490 --> 00:07:28.210
- why that exists. Yeah. I mean, who knows

203
00:07:28.210 --> 00:07:30.389
- what's gonna happen in ten years? ATM,

204
00:07:30.850 --> 00:07:31.350
- according

205
00:07:31.650 --> 00:07:33.810
- to some analysts, was going to take over

206
00:07:33.810 --> 00:07:35.615
- the desktop in ten years. I mean I

207
00:07:35.615 --> 00:07:36.914
- still remember the charts.

208
00:07:41.375 --> 00:07:43.394
- I'm still not running ATM so

209
00:07:43.774 --> 00:07:44.995
- maybe they were wrong.

210
00:07:45.375 --> 00:07:45.875
- So

211
00:07:47.209 --> 00:07:48.569
- it might be interesting to go into a

212
00:07:48.569 --> 00:07:50.250
- little bit of the difference between Python and

213
00:07:50.250 --> 00:07:52.730
- Golang, for people who aren't familiar with the

214
00:07:52.730 --> 00:07:56.430
- two different programming languages and even the paradigm

215
00:07:56.569 --> 00:07:58.889
- of different ways of building programming languages or

216
00:07:58.889 --> 00:08:01.754
- the way they work. For instance, Golang is

217
00:08:01.754 --> 00:08:03.915
- not really an interpreted language, but Python is.

218
00:08:03.915 --> 00:08:05.035
- Can we go into a little bit of

219
00:08:05.035 --> 00:08:06.335
- that and try to explain,

220
00:08:06.715 --> 00:08:07.775
- maybe for listeners,

221
00:08:08.154 --> 00:08:10.074
- why that's different or or what the differences

222
00:08:10.074 --> 00:08:10.735
- there are?

223
00:08:11.675 --> 00:08:14.654
- So the main difference between an... The interpreted

224
00:08:14.715 --> 00:08:15.935
- language and a compiled

225
00:08:16.300 --> 00:08:18.780
- language is that you... Like, in Python, for

226
00:08:18.780 --> 00:08:21.020
- instance, which is interpreted, you would write your

227
00:08:21.020 --> 00:08:23.580
- code, and then you have this, dot p

228
00:08:23.580 --> 00:08:24.080
- y

229
00:08:24.460 --> 00:08:27.199
- file that then you use Python,

230
00:08:28.300 --> 00:08:31.214
- like, the program to run that that script.

231
00:08:31.214 --> 00:08:32.654
- Right? So every time you need to run

232
00:08:32.654 --> 00:08:34.654
- your script, you need Python in the same

233
00:08:34.654 --> 00:08:36.914
- machine to be able to to run it.

234
00:08:37.615 --> 00:08:41.075
- With a compiled language like like c, Java,

235
00:08:41.615 --> 00:08:42.115
- Golang,

236
00:08:42.590 --> 00:08:45.470
- you have instead, a compiler that will read

237
00:08:45.470 --> 00:08:47.549
- the code and generate a a binary, and

238
00:08:47.549 --> 00:08:50.210
- that binary can be run without requiring,

239
00:08:50.990 --> 00:08:53.970
- the the, like, Java itself or,

240
00:08:54.750 --> 00:08:56.690
- or Golang or

241
00:08:57.070 --> 00:08:59.174
- or or or the c compiler. Like, you

242
00:08:59.174 --> 00:09:01.034
- have the binary, and the binary can be

243
00:09:01.095 --> 00:09:02.075
- can be run.

244
00:09:03.735 --> 00:09:04.475
- Another benefit

245
00:09:04.774 --> 00:09:05.274
- of,

246
00:09:07.254 --> 00:09:09.195
- compile language as opposed to runtime,

247
00:09:10.054 --> 00:09:10.554
- languages,

248
00:09:11.095 --> 00:09:11.595
- runtime

249
00:09:11.919 --> 00:09:14.340
- language is the same as interpreter languages, is

250
00:09:14.480 --> 00:09:16.100
- that you are able to catch,

251
00:09:16.720 --> 00:09:19.059
- errors on compile time. Like, usually,

252
00:09:19.679 --> 00:09:21.940
- compiled languages are also,

253
00:09:22.480 --> 00:09:25.040
- statically typed. So you need to say, like,

254
00:09:25.040 --> 00:09:27.014
- oh, this function takes these parameters, and these

255
00:09:27.014 --> 00:09:29.835
- parameters are of are of this particular type.

256
00:09:29.975 --> 00:09:31.894
- So you make a mistake and pass the

257
00:09:31.894 --> 00:09:32.714
- wrong type,

258
00:09:33.095 --> 00:09:33.995
- things just,

259
00:09:35.095 --> 00:09:36.774
- blow up at compile time. So it means

260
00:09:36.774 --> 00:09:38.294
- that when you run the program, you don't

261
00:09:38.294 --> 00:09:40.990
- find any surprises that, oh, yeah. I passed

262
00:09:40.990 --> 00:09:42.509
- this type, and this type doesn't have this

263
00:09:42.509 --> 00:09:43.009
- particular

264
00:09:43.549 --> 00:09:44.929
- attribute, which is a common,

265
00:09:45.629 --> 00:09:48.669
- problem with with Python. Like, anyone that has

266
00:09:48.669 --> 00:09:51.490
- written some Python has seen the typical,

267
00:09:52.029 --> 00:09:53.024
- error, non type

268
00:09:53.504 --> 00:09:54.965
- has... Doesn't have the attribute

269
00:09:55.345 --> 00:09:56.085
- blah. Right?

270
00:09:57.105 --> 00:09:58.404
- So those would be, like,

271
00:09:59.825 --> 00:10:01.445
- main main differences,

272
00:10:01.904 --> 00:10:05.264
- I guess. Yeah. So so it also depends

273
00:10:05.264 --> 00:10:07.024
- on whether the language is strongly typed or

274
00:10:07.024 --> 00:10:09.276
- or weakly typed. Right? So c, for instance,

275
00:10:09.276 --> 00:10:11.730
- is not a weakly typed language. You can

276
00:10:11.730 --> 00:10:13.829
- cast a string to a pointer

277
00:10:14.209 --> 00:10:16.049
- or a string to a like you can

278
00:10:16.049 --> 00:10:18.529
- take the ASCII value of a number and

279
00:10:18.529 --> 00:10:19.970
- just use it as a number with no

280
00:10:19.970 --> 00:10:23.415
- conversion. Like it's just stored in memory locations.

281
00:10:23.415 --> 00:10:25.254
- You can do whatever you want to. In

282
00:10:25.254 --> 00:10:27.014
- fact, a lot of people who start with

283
00:10:27.014 --> 00:10:28.774
- C, that's one of their biggest confusions is

284
00:10:28.774 --> 00:10:30.774
- the whole pointer mess, how you can cast

285
00:10:30.774 --> 00:10:33.835
- pointers and pass pointers and shared memory versus

286
00:10:34.215 --> 00:10:36.235
- things that are not shared, stuff like that.

287
00:10:36.470 --> 00:10:38.790
- Whereas with Golang, it's a strongly typed language,

288
00:10:38.790 --> 00:10:40.330
- right? So if you want to cast

289
00:10:40.870 --> 00:10:43.429
- a text string as integers or as a

290
00:10:43.429 --> 00:10:45.269
- different type, you've actually got to go through

291
00:10:45.269 --> 00:10:47.830
- the process of doing that cast. You can't

292
00:10:47.830 --> 00:10:50.884
- just randomly use the array or the string

293
00:10:50.884 --> 00:10:51.785
- in a different way,

294
00:10:52.245 --> 00:10:54.264
- which also helps catch errors, right?

295
00:10:54.965 --> 00:10:56.105
- Yeah. Yeah. Correct.

296
00:10:56.805 --> 00:10:59.524
- So, and now, Python, now is Python weakly

297
00:10:59.524 --> 00:11:00.665
- or strongly typed?

298
00:11:01.125 --> 00:11:03.080
- I think it's pretty weakly typed from what

299
00:11:03.080 --> 00:11:04.519
- I remember. I don't do a lot of

300
00:11:04.519 --> 00:11:06.299
- Python. So... I... Py... Python

301
00:11:06.600 --> 00:11:07.340
- is actually,

302
00:11:08.120 --> 00:11:09.820
- strongly typed, but it's dynamically

303
00:11:10.440 --> 00:11:13.019
- typed, which means that you can change variable.

304
00:11:13.080 --> 00:11:14.679
- You you can change the type of of

305
00:11:14.679 --> 00:11:17.544
- variables, but you cannot easily convert,

306
00:11:18.485 --> 00:11:20.485
- like, between types. Like, if you have, an

307
00:11:20.485 --> 00:11:22.804
- object of a particular type, you cannot just

308
00:11:22.804 --> 00:11:24.565
- say, like, oh, now it's gonna be this

309
00:11:24.565 --> 00:11:25.605
- other thing that's just,

310
00:11:27.125 --> 00:11:28.964
- blow. So the the main thing is that

311
00:11:28.964 --> 00:11:30.644
- it's dynamically typed. So you have this,

312
00:11:31.889 --> 00:11:34.610
- variable n, and you can start with n

313
00:11:34.610 --> 00:11:36.930
- being an integer, and then three lines below,

314
00:11:36.930 --> 00:11:39.029
- you just assign a string in there.

315
00:11:40.529 --> 00:11:43.250
- So it's dynamic. That's even more confusing than

316
00:11:43.250 --> 00:11:45.695
- c. Because it's just... Yes. Whatever it is

317
00:11:45.695 --> 00:11:47.455
- in C, it's always a string. You can

318
00:11:47.455 --> 00:11:48.894
- use it as a number, but it's still

319
00:11:48.894 --> 00:11:50.894
- a string. And, you know, you assume that

320
00:11:50.894 --> 00:11:53.054
- if it's a string, there's a null endpoint

321
00:11:53.054 --> 00:11:55.695
- and stuff like that. So that's interesting. Now,

322
00:11:55.695 --> 00:11:57.154
- another difference is that

323
00:11:57.695 --> 00:11:59.610
- compiled languages like C Golang

324
00:12:00.549 --> 00:12:01.209
- are required

325
00:12:01.750 --> 00:12:04.549
- to be recompiled for different processors. Now, that

326
00:12:04.549 --> 00:12:06.950
- used to be a big deal. And in

327
00:12:06.950 --> 00:12:08.629
- some cases, it still can be. In data

328
00:12:08.629 --> 00:12:10.629
- centers, you can get ARM chips versus Intel

329
00:12:10.629 --> 00:12:12.975
- chips. And it used to be AMD had

330
00:12:12.975 --> 00:12:14.034
- a completely different,

331
00:12:14.815 --> 00:12:17.375
- different API or a different instruction set than

332
00:12:17.375 --> 00:12:19.075
- Intel did, so you would have to recompile

333
00:12:19.615 --> 00:12:20.835
- on multiple platforms.

334
00:12:21.214 --> 00:12:23.054
- And that still is true, like, with cell

335
00:12:23.054 --> 00:12:24.274
- phones or with

336
00:12:24.860 --> 00:12:26.860
- ARM chips and data centers or tablets or

337
00:12:26.860 --> 00:12:29.040
- something like that. Whereas with something like

338
00:12:29.660 --> 00:12:32.320
- Python or even Java in a JVM,

339
00:12:32.860 --> 00:12:34.860
- which it is kind of a virtual machine

340
00:12:34.860 --> 00:12:36.560
- that you're running inside of,

341
00:12:37.019 --> 00:12:38.620
- then you can just run it on anything.

342
00:12:38.620 --> 00:12:41.105
- It doesn't matter because it just... There's the

343
00:12:41.105 --> 00:12:43.425
- interpreter sitting there that does the job of

344
00:12:43.425 --> 00:12:45.665
- making the right machine code pop out the

345
00:12:45.665 --> 00:12:47.184
- other end. So those are kind of some

346
00:12:47.184 --> 00:12:47.925
- of the differences.

347
00:12:48.465 --> 00:12:50.485
- So now let's talk. So

348
00:12:51.264 --> 00:12:52.565
- so Golang is interesting.

349
00:12:53.070 --> 00:12:55.710
- I really like Golang. I've looked at Go

350
00:12:55.710 --> 00:12:57.389
- BGP and stuff like that. Now I don't

351
00:12:57.389 --> 00:12:59.169
- know that I would still

352
00:12:59.470 --> 00:13:00.450
- suggest running...

353
00:13:00.990 --> 00:13:03.309
- I still think building a routing protocol or

354
00:13:03.309 --> 00:13:05.070
- something is still something that you should be

355
00:13:05.070 --> 00:13:07.904
- doing in C because of the expressive semantics.

356
00:13:08.524 --> 00:13:09.904
- But as a network automation,

357
00:13:10.365 --> 00:13:12.764
- now what type of tools are available in

358
00:13:12.764 --> 00:13:14.845
- Golang for network automation? I assume you have

359
00:13:14.845 --> 00:13:15.345
- gRPC,

360
00:13:15.804 --> 00:13:18.125
- which means you can do JSON and stuff

361
00:13:18.125 --> 00:13:19.559
- like that. But are there

362
00:13:20.279 --> 00:13:22.279
- things like SaltStack or anything else that you

363
00:13:22.279 --> 00:13:23.879
- can use or Ansible that you can use

364
00:13:23.879 --> 00:13:24.620
- with Golang?

365
00:13:25.480 --> 00:13:27.419
- So I haven't I haven't seen anything

366
00:13:27.879 --> 00:13:30.279
- like that. Like, everything I'm using, for instance,

367
00:13:30.279 --> 00:13:33.365
- is mostly built on top of gRPC,

368
00:13:33.904 --> 00:13:36.804
- which works, like, beautifully with with Golang.

369
00:13:37.825 --> 00:13:40.544
- But now I haven't used anything like... I

370
00:13:40.544 --> 00:13:42.945
- haven't seen anything like salt or or anything

371
00:13:42.945 --> 00:13:45.904
- like that. For those familiar with with Nornir,

372
00:13:45.904 --> 00:13:49.429
- I wrote, a Golang equivalent, which is basically

373
00:13:49.429 --> 00:13:50.809
- what I'm what I'm using.

374
00:13:52.709 --> 00:13:53.990
- So tell us about that a little bit

375
00:13:53.990 --> 00:13:56.169
- because that's really interesting. It's... Like I said,

376
00:13:56.230 --> 00:13:58.149
- good coders always build their own tools. So

377
00:13:58.149 --> 00:13:59.669
- tell us about this tool that you've built.

378
00:13:59.669 --> 00:14:00.490
- It's very interesting.

379
00:14:01.110 --> 00:14:01.610
- So

380
00:14:02.414 --> 00:14:05.455
- this is for both, Nournier and and Gournier,

381
00:14:05.455 --> 00:14:08.115
- which is the Golang equivalent. Like, the idea

382
00:14:08.575 --> 00:14:10.274
- here is to have, like, a framework

383
00:14:11.054 --> 00:14:11.554
- to,

384
00:14:12.894 --> 00:14:13.554
- to do,

385
00:14:14.254 --> 00:14:17.054
- various things, like loading an inventory of of

386
00:14:17.054 --> 00:14:17.554
- devices

387
00:14:17.929 --> 00:14:19.070
- and then being able

388
00:14:19.450 --> 00:14:22.089
- to to pass task to the to the

389
00:14:22.089 --> 00:14:24.669
- framework to execute those tasks over

390
00:14:25.049 --> 00:14:27.129
- over those devices. So you would say, like,

391
00:14:27.129 --> 00:14:29.129
- okay. I'm gonna I'm gonna create a task

392
00:14:29.129 --> 00:14:30.750
- that its own... Only responsibility

393
00:14:31.129 --> 00:14:33.745
- is to configure a set of, BGP

394
00:14:34.365 --> 00:14:34.865
- peers.

395
00:14:35.565 --> 00:14:37.085
- And then you just say, like, okay. This

396
00:14:37.085 --> 00:14:39.024
- is my inventory. This is my task. Just

397
00:14:39.485 --> 00:14:42.365
- do it over this set of devices, and

398
00:14:42.365 --> 00:14:44.304
- then everything just... Like, all the multithreading,

399
00:14:44.605 --> 00:14:47.480
- all the passing data around, making sure that

400
00:14:47.480 --> 00:14:47.639
- the,

401
00:14:48.840 --> 00:14:49.340
- code,

402
00:14:50.120 --> 00:14:52.460
- is executed and all that. That's just

403
00:14:52.920 --> 00:14:54.600
- done for for you. You only have to

404
00:14:54.600 --> 00:14:55.899
- think in terms of,

405
00:14:57.080 --> 00:14:59.179
- individual operations, and then all

406
00:14:59.800 --> 00:15:02.414
- the magic on these different devices happens by

407
00:15:02.414 --> 00:15:02.914
- itself.

408
00:15:04.095 --> 00:15:05.615
- Really cool. So is this open source? You

409
00:15:05.615 --> 00:15:06.834
- can get this on Git?

410
00:15:07.294 --> 00:15:09.375
- Yeah. This is all on on GitHub. It's

411
00:15:09.375 --> 00:15:10.914
- all Apache two,

412
00:15:11.534 --> 00:15:12.034
- licensed

413
00:15:12.735 --> 00:15:14.669
- and, yeah, available on

414
00:15:15.230 --> 00:15:16.990
- PyPI in the case of,

415
00:15:18.110 --> 00:15:22.049
- Nournier for Python, and is just available via

416
00:15:22.110 --> 00:15:23.649
- GoGet as as useful.

417
00:15:24.669 --> 00:15:25.169
- Okay.

418
00:15:25.789 --> 00:15:29.315
- So Nournier is written in Python and uses...

419
00:15:29.375 --> 00:15:31.615
- It has plugins for Netmiko and Napalm. Do

420
00:15:31.615 --> 00:15:34.034
- you have similar plugins in the Gornir,

421
00:15:34.894 --> 00:15:36.034
- library for Golang?

422
00:15:36.815 --> 00:15:37.954
- So there is some,

423
00:15:39.375 --> 00:15:41.714
- plugins for SSH based,

424
00:15:42.320 --> 00:15:46.019
- devices, but because everything I'm doing is, gRPC

425
00:15:46.240 --> 00:15:47.220
- myself, so

426
00:15:47.759 --> 00:15:49.139
- I... I'm mostly just,

427
00:15:50.879 --> 00:15:53.460
- having integrations for my own gRPC devices.

428
00:15:55.120 --> 00:15:55.940
- Very cool.

429
00:15:56.495 --> 00:15:56.995
- Awesome.

430
00:15:57.774 --> 00:15:59.394
- That's great. So

431
00:16:00.414 --> 00:16:01.934
- so let's talk a little bit about the

432
00:16:01.934 --> 00:16:03.315
- skill set. So

433
00:16:03.934 --> 00:16:05.855
- when you think about learning how to code

434
00:16:05.855 --> 00:16:07.695
- or a network engineer thinking about learning how

435
00:16:07.695 --> 00:16:09.774
- to code, what is it that they should

436
00:16:09.774 --> 00:16:12.149
- be learning? Is it data structures, algorithms?

437
00:16:12.929 --> 00:16:14.610
- I know Git. Git's a big one, and,

438
00:16:14.610 --> 00:16:16.289
- honestly, I still struggle with Git, and I

439
00:16:16.289 --> 00:16:18.209
- need to spend some time doing better with

440
00:16:18.209 --> 00:16:19.490
- Git. And it's really sad because I'm a

441
00:16:19.490 --> 00:16:22.149
- maintainer on FR routing, so I push PRs

442
00:16:22.289 --> 00:16:23.970
- all the time. I did code reviews and

443
00:16:23.970 --> 00:16:25.995
- PRs all the time, and I'm in the

444
00:16:26.075 --> 00:16:27.995
- code all the time looking at how things

445
00:16:27.995 --> 00:16:30.475
- work, and yet I still feel completely lost

446
00:16:30.475 --> 00:16:32.075
- in Git a lot of times. So I

447
00:16:32.075 --> 00:16:33.754
- know Git's a big one. Right? I mean,

448
00:16:33.754 --> 00:16:36.154
- you need to learn Git to start from.

449
00:16:36.154 --> 00:16:38.335
- That would be my immediate guess.

450
00:16:39.434 --> 00:16:41.509
- Yeah. I mean, I think there are several

451
00:16:41.509 --> 00:16:42.009
- tools

452
00:16:42.710 --> 00:16:44.009
- to program that people

453
00:16:44.389 --> 00:16:46.330
- usually overlooks. Like, they

454
00:16:46.710 --> 00:16:49.290
- go straight into coding, and they

455
00:16:49.990 --> 00:16:53.190
- don't, spend any time, like, learning the the

456
00:16:53.190 --> 00:16:56.345
- tools for parameters. Like, for instance, like, the

457
00:16:56.884 --> 00:16:57.625
- the usual

458
00:16:58.004 --> 00:16:59.065
- one that people,

459
00:16:59.685 --> 00:17:02.585
- ignores is learning how to use a debugger.

460
00:17:03.365 --> 00:17:05.144
- And that's the only way of actually

461
00:17:05.605 --> 00:17:07.785
- trying to more or less sanely,

462
00:17:08.700 --> 00:17:11.179
- troubleshoot code when it doesn't work as as

463
00:17:11.179 --> 00:17:13.259
- expected. Like, a debugger is something that can

464
00:17:13.259 --> 00:17:15.099
- tap into your program, and then you can

465
00:17:15.099 --> 00:17:17.659
- stop the execution of your program and say,

466
00:17:17.659 --> 00:17:18.940
- like, okay. Can you just show me the

467
00:17:18.940 --> 00:17:19.440
- memory

468
00:17:19.819 --> 00:17:21.884
- when you hit this particular line of the

469
00:17:21.884 --> 00:17:23.724
- code? So that's useful to start seeing, like,

470
00:17:23.724 --> 00:17:25.724
- okay. Why is this not working as as

471
00:17:25.724 --> 00:17:27.424
- expected? And people usually,

472
00:17:28.765 --> 00:17:29.244
- ignores,

473
00:17:29.644 --> 00:17:32.605
- that. Another thing that is very useful to

474
00:17:32.605 --> 00:17:34.305
- learn to use is some proper

475
00:17:34.765 --> 00:17:36.960
- ID. IDEs can help you with the debugger

476
00:17:36.960 --> 00:17:39.440
- itself. It can help you by... With auto

477
00:17:39.440 --> 00:17:40.580
- completion, with

478
00:17:40.960 --> 00:17:43.440
- inline documentation. It just makes your life so

479
00:17:43.440 --> 00:17:45.380
- much easier, especially when you're starting

480
00:17:45.680 --> 00:17:47.059
- and you may not know

481
00:17:47.599 --> 00:17:49.964
- the the libraries that you need by heart.

482
00:17:49.964 --> 00:17:52.444
- Like, you start typing, and the auto complete

483
00:17:52.444 --> 00:17:53.804
- more or less shows you the option that

484
00:17:53.804 --> 00:17:54.924
- you have. Like, oh, yeah. This is the

485
00:17:54.924 --> 00:17:57.484
- function that I that I was thinking of,

486
00:17:57.484 --> 00:17:59.505
- which is also great for exploring new,

487
00:18:00.845 --> 00:18:01.345
- libraries.

488
00:18:02.125 --> 00:18:03.069
- And, of course,

489
00:18:04.410 --> 00:18:05.769
- Git, I would say that those are the

490
00:18:05.769 --> 00:18:06.829
- most important

491
00:18:07.289 --> 00:18:07.789
- overlooked,

492
00:18:08.569 --> 00:18:10.349
- tools that people need to learn.

493
00:18:11.369 --> 00:18:12.970
- Yeah. I think it was about six months

494
00:18:12.970 --> 00:18:15.075
- into my journey of learning Python that I,

495
00:18:15.954 --> 00:18:18.054
- ran into PDB, IPDB

496
00:18:18.514 --> 00:18:20.034
- and started using it. And I was like,

497
00:18:20.034 --> 00:18:22.115
- oh my gosh. This is fantastic. It,

498
00:18:23.075 --> 00:18:25.794
- really changes the game for actually understanding how

499
00:18:25.794 --> 00:18:27.315
- your code is running instead of just trying

500
00:18:27.315 --> 00:18:28.694
- to arbitrarily troubleshoot

501
00:18:29.075 --> 00:18:30.755
- functions and things. So,

502
00:18:31.090 --> 00:18:32.769
- what do you use in Golang? Is it,

503
00:18:33.570 --> 00:18:35.250
- g d... Is there, like, a GDB? What's

504
00:18:35.250 --> 00:18:35.750
- the,

505
00:18:36.570 --> 00:18:38.470
- the the tool for debugging?

506
00:18:39.170 --> 00:18:41.330
- Yeah. So there is GDB, and there is

507
00:18:41.330 --> 00:18:44.950
- also one that is tailored for Golang, specifically,

508
00:18:45.009 --> 00:18:46.325
- which is called Delves.

509
00:18:48.464 --> 00:18:48.964
- Okay.

510
00:18:50.464 --> 00:18:51.044
- So Delve...

511
00:18:52.065 --> 00:18:53.284
- Oh, sorry. Go ahead. And

512
00:18:53.744 --> 00:18:56.144
- I was gonna say Delve is pretty similar

513
00:18:56.144 --> 00:18:58.299
- to to PDP. So you have experience with

514
00:18:58.299 --> 00:19:00.140
- it. Like, you would... And just start playing

515
00:19:00.140 --> 00:19:01.740
- with Delphi. You will see, like, it's pretty

516
00:19:01.740 --> 00:19:04.140
- much the same type of interface, the same

517
00:19:04.140 --> 00:19:06.160
- type of commands, and and everything.

518
00:19:07.339 --> 00:19:09.279
- Uh-huh. What... How does GDB

519
00:19:09.580 --> 00:19:10.799
- differ from Delphi?

520
00:19:11.580 --> 00:19:12.080
- So

521
00:19:12.779 --> 00:19:14.695
- GDB is more tailored

522
00:19:15.234 --> 00:19:18.295
- for compiled software, so it's a bit more

523
00:19:18.914 --> 00:19:21.414
- rough to to to follow. Like,

524
00:19:22.674 --> 00:19:23.494
- like, you will...

525
00:19:23.795 --> 00:19:26.115
- It doesn't integrate that well with the with

526
00:19:26.115 --> 00:19:28.529
- the Golang code, so it's harder to

527
00:19:28.910 --> 00:19:31.390
- jump into particular lines and and things like

528
00:19:31.390 --> 00:19:31.890
- that.

529
00:19:33.630 --> 00:19:36.509
- Gotcha. Gotcha. Do you use, other tools along

530
00:19:36.509 --> 00:19:38.450
- with that? Like, do you set breakpoints in,

531
00:19:39.309 --> 00:19:41.164
- some sort of text editor in order to

532
00:19:41.164 --> 00:19:42.304
- run your code and,

533
00:19:42.845 --> 00:19:45.085
- debug it? Or do you typically just walk

534
00:19:45.085 --> 00:19:46.765
- through the program directly? How do you go

535
00:19:46.765 --> 00:19:47.664
- about that normally?

536
00:19:48.204 --> 00:19:51.265
- I usually deal with the command line directly.

537
00:19:51.325 --> 00:19:52.605
- And by the command line, I mean the

538
00:19:52.605 --> 00:19:54.065
- command line that the debugger

539
00:19:54.365 --> 00:19:55.565
- gives you. When you start to do a

540
00:19:55.565 --> 00:19:57.180
- program, it jumps into this,

541
00:19:58.519 --> 00:19:59.240
- shell, within,

542
00:20:00.519 --> 00:20:03.160
- PBB or Dell or any other you may

543
00:20:03.160 --> 00:20:05.480
- be using. And then I just type the

544
00:20:05.480 --> 00:20:07.559
- the break points in in there. I program

545
00:20:07.559 --> 00:20:08.414
- mostly in in

546
00:20:09.215 --> 00:20:10.894
- BI, so I don't have a lot of...

547
00:20:10.894 --> 00:20:12.515
- I don't have a super fancy

548
00:20:12.975 --> 00:20:15.315
- ID myself. I tend to just,

549
00:20:17.055 --> 00:20:19.075
- deal with the with the common line.

550
00:20:20.255 --> 00:20:21.315
- Oh, that's interesting.

551
00:20:21.799 --> 00:20:24.059
- So I use Visual Studio Code,

552
00:20:25.000 --> 00:20:25.720
- quite a bit,

553
00:20:26.599 --> 00:20:29.720
- because it's just easier to jump around like

554
00:20:29.720 --> 00:20:31.400
- a text document and edit it that way

555
00:20:31.400 --> 00:20:33.559
- for for me. I'm curious why you use

556
00:20:33.559 --> 00:20:35.559
- VI and just go directly from the the

557
00:20:35.559 --> 00:20:36.059
- CLI.

558
00:20:37.159 --> 00:20:39.964
- So I mostly use VI because everything I

559
00:20:39.964 --> 00:20:41.184
- do is in the

560
00:20:41.724 --> 00:20:43.724
- in the command line anyway. Like, I'm... When

561
00:20:43.724 --> 00:20:45.585
- I'm programming, I'm mostly, like,

562
00:20:46.285 --> 00:20:47.184
- working with,

563
00:20:47.964 --> 00:20:48.464
- containers,

564
00:20:49.005 --> 00:20:52.049
- maybe SSHing into remote machines, and I'm always

565
00:20:52.049 --> 00:20:54.789
- in the in the command line doing whatever.

566
00:20:55.250 --> 00:20:56.950
- So I used to use,

567
00:20:58.130 --> 00:20:58.630
- ATOM,

568
00:20:59.089 --> 00:21:00.789
- before jumping into VI.

569
00:21:01.169 --> 00:21:02.149
- And I

570
00:21:02.849 --> 00:21:05.649
- I felt that I was always jumping between

571
00:21:05.649 --> 00:21:06.869
- Windows and losing

572
00:21:07.444 --> 00:21:08.825
- track of what I was doing,

573
00:21:09.365 --> 00:21:11.444
- with so much context switching. So I started

574
00:21:11.444 --> 00:21:15.045
- just, like, using TMX and and BI, and

575
00:21:15.045 --> 00:21:16.664
- then my workflow just became

576
00:21:17.285 --> 00:21:19.704
- a bit faster and and better.

577
00:21:20.164 --> 00:21:21.944
- Although it has a bit of

578
00:21:22.644 --> 00:21:24.069
- a learning curve, like,

579
00:21:24.369 --> 00:21:27.170
- the... Going through configuring the eye and t

580
00:21:27.170 --> 00:21:28.289
- mux to your,

581
00:21:29.089 --> 00:21:29.589
- liking.

582
00:21:30.849 --> 00:21:31.750
- Yeah. Yeah.

583
00:21:36.609 --> 00:21:38.664
- I think you're muted. Yeah. I'm muted.

584
00:21:40.085 --> 00:21:40.585
- So,

585
00:21:40.884 --> 00:21:42.484
- yeah, let me think about what I was

586
00:21:42.484 --> 00:21:43.384
- just gonna say.

587
00:21:45.125 --> 00:21:47.384
- I just blew my... Blew myself up.

588
00:21:47.924 --> 00:21:49.779
- So you don't use Z Max? I'm I'm

589
00:21:49.779 --> 00:21:51.539
- pretty amazed that you use VI. You're hung

590
00:21:51.539 --> 00:21:52.279
- on VI.

591
00:21:52.660 --> 00:21:54.660
- VI, I find very difficult to use personally.

592
00:21:54.660 --> 00:21:56.019
- I know most of the coders I deal

593
00:21:56.019 --> 00:21:58.420
- with don't find it very difficult to use,

594
00:21:58.420 --> 00:22:00.500
- but I I seem to find it very

595
00:22:00.500 --> 00:22:01.480
- difficult to use.

596
00:22:02.819 --> 00:22:05.365
- So I I tried to use Emacs a

597
00:22:05.365 --> 00:22:06.904
- couple of times, and

598
00:22:07.205 --> 00:22:09.924
- I have found two problems with it. The

599
00:22:09.924 --> 00:22:12.805
- first one was that I haven't had the

600
00:22:12.805 --> 00:22:13.785
- time to actually

601
00:22:14.325 --> 00:22:16.505
- customize it to my liking yet, so

602
00:22:16.805 --> 00:22:19.019
- I don't have the same environment that

603
00:22:19.500 --> 00:22:20.880
- I would have with VI.

604
00:22:21.339 --> 00:22:23.580
- And the second issue is that I I

605
00:22:23.580 --> 00:22:25.820
- have problems in my my hands. So I'm

606
00:22:25.820 --> 00:22:26.559
- very sensitive

607
00:22:27.660 --> 00:22:30.380
- to changes in the movements that I do

608
00:22:30.380 --> 00:22:32.954
- with my fingers and my wrist. And

609
00:22:34.234 --> 00:22:36.794
- I... Two days that I tried TMax, that

610
00:22:36.794 --> 00:22:38.174
- just led to a

611
00:22:38.474 --> 00:22:41.434
- lot of pain. So decided to to just

612
00:22:41.434 --> 00:22:41.934
- stop.

613
00:22:42.474 --> 00:22:45.115
- That's very interesting. Yeah. So so that's another

614
00:22:45.115 --> 00:22:47.454
- interesting point is that your tools are often,

615
00:22:48.394 --> 00:22:51.190
- can be man... Or can be impacted by

616
00:22:51.490 --> 00:22:53.250
- what you do on a regular basis, like,

617
00:22:53.250 --> 00:22:55.170
- what your workflow is, which is very interesting

618
00:22:55.170 --> 00:22:55.670
- because

619
00:22:56.369 --> 00:22:57.809
- because a lot of people say, well, how

620
00:22:57.809 --> 00:23:00.049
- do you write fast in Microsoft Word or

621
00:23:00.049 --> 00:23:01.970
- whatever? They're always fussing me about writing books

622
00:23:01.970 --> 00:23:03.990
- in Microsoft Word. You should be using markdown.

623
00:23:04.210 --> 00:23:06.505
- And I say, well, I don't know. I've...

624
00:23:06.505 --> 00:23:08.984
- Don't even use the standard Microsoft Word menu

625
00:23:08.984 --> 00:23:11.005
- system. I have my own that I've built.

626
00:23:11.144 --> 00:23:12.825
- And second of all, I don't use a

627
00:23:12.825 --> 00:23:14.125
- mouse. I use a tablet.

628
00:23:14.424 --> 00:23:16.345
- And so because I use a tablet, I

629
00:23:16.345 --> 00:23:18.424
- can actually switch back and forth between the

630
00:23:18.424 --> 00:23:18.924
- keyboard

631
00:23:19.599 --> 00:23:22.159
- and the tablet much, much faster, particularly if

632
00:23:22.159 --> 00:23:24.319
- I put on touch mode on the tablet.

633
00:23:24.319 --> 00:23:25.279
- I don't even have to pick a pen

634
00:23:25.279 --> 00:23:26.639
- up or anything. I just reach over there

635
00:23:26.639 --> 00:23:27.460
- and do it.

636
00:23:27.839 --> 00:23:29.599
- So I find it actually to be pretty

637
00:23:29.599 --> 00:23:32.085
- fast. So I think the work flow is

638
00:23:32.085 --> 00:23:34.404
- really, really important. People don't think about the

639
00:23:34.404 --> 00:23:34.904
- workflow

640
00:23:35.365 --> 00:23:37.065
- in terms of what they're doing.

641
00:23:37.444 --> 00:23:39.625
- And second of all, just the idea that,

642
00:23:39.765 --> 00:23:41.224
- you know, your physical...

643
00:23:41.525 --> 00:23:44.085
- The way you're physically made is that it's

644
00:23:44.085 --> 00:23:46.484
- easier for you to use your fingers in

645
00:23:46.484 --> 00:23:47.940
- a way where all the commands are close

646
00:23:47.940 --> 00:23:49.460
- together. And I don't think people think about

647
00:23:49.460 --> 00:23:52.179
- those things. But they're really important in getting

648
00:23:52.179 --> 00:23:53.640
- your workflow speed up.

649
00:23:55.220 --> 00:23:57.059
- Yeah. Yeah. I agree. I I try to

650
00:23:57.059 --> 00:23:59.160
- avoid anything that requires,

651
00:23:59.539 --> 00:24:01.065
- a mouse mouse for the same issue that

652
00:24:01.065 --> 00:24:02.825
- I mentioned before. Like, if I use a

653
00:24:02.825 --> 00:24:05.065
- mouse for long periods of time, I start

654
00:24:05.065 --> 00:24:07.785
- getting pain in my in my wrist. I

655
00:24:07.785 --> 00:24:08.525
- always try

656
00:24:08.984 --> 00:24:11.625
- to optimize for for the common line because

657
00:24:11.625 --> 00:24:14.159
- I feel more comfortable typing. I also feel

658
00:24:14.159 --> 00:24:14.740
- that I'm

659
00:24:15.119 --> 00:24:17.440
- faster typing than just moving the mouse around,

660
00:24:17.440 --> 00:24:19.919
- but mostly because it doesn't lead to to

661
00:24:19.919 --> 00:24:20.419
- pain.

662
00:24:20.960 --> 00:24:22.259
- Yeah. Right. Right.

663
00:24:22.880 --> 00:24:25.460
- So in the realm of programming beyond tools,

664
00:24:25.599 --> 00:24:27.700
- do you think people need to learn algorithms?

665
00:24:27.759 --> 00:24:29.414
- Like, I see people who say, I just

666
00:24:29.414 --> 00:24:31.674
- don't need to learn algorithms and data structures

667
00:24:31.734 --> 00:24:33.494
- or anything like that. I just need to

668
00:24:33.494 --> 00:24:35.335
- go learn how to do stuff. How would

669
00:24:35.335 --> 00:24:38.134
- you pit those two arguments against one another,

670
00:24:38.134 --> 00:24:40.394
- or how do you see that playing out?

671
00:24:41.015 --> 00:24:41.460
- So

672
00:24:42.019 --> 00:24:42.519
- regarding

673
00:24:42.980 --> 00:24:46.179
- algorithm, I'm not sure that it's so important

674
00:24:46.179 --> 00:24:47.240
- nowadays because

675
00:24:47.619 --> 00:24:48.359
- most of

676
00:24:48.980 --> 00:24:51.859
- the useful ones are gonna be implemented as

677
00:24:51.859 --> 00:24:54.075
- part of the standard library. Like, how to

678
00:24:54.154 --> 00:24:56.075
- sort a a list, how to search in

679
00:24:56.075 --> 00:24:57.434
- a sort of list. Like, all those kind

680
00:24:57.434 --> 00:24:59.054
- of things are already

681
00:24:59.514 --> 00:25:02.095
- solved. It's nice to know them because that

682
00:25:02.474 --> 00:25:02.974
- also

683
00:25:03.595 --> 00:25:05.194
- helps you, like,

684
00:25:05.674 --> 00:25:06.894
- like, to think about

685
00:25:07.274 --> 00:25:09.694
- problems and and whatnot. I don't think they're

686
00:25:10.200 --> 00:25:10.700
- extremely,

687
00:25:11.240 --> 00:25:14.059
- important. I think data structure is more important

688
00:25:14.359 --> 00:25:16.839
- because a lot of people struggle with, like,

689
00:25:16.839 --> 00:25:18.759
- Oh, I have I have all this data,

690
00:25:18.759 --> 00:25:21.339
- and they have even problems iterating

691
00:25:21.960 --> 00:25:24.119
- over the data because they don't understand the

692
00:25:24.119 --> 00:25:26.414
- difference between a map or a dictionary,

693
00:25:27.115 --> 00:25:29.035
- and a list, for instance. Like... So I

694
00:25:29.035 --> 00:25:31.615
- think data structure is certainly super important.

695
00:25:32.634 --> 00:25:33.134
- Algorithm,

696
00:25:33.994 --> 00:25:36.315
- it's nice to know because that's gonna open

697
00:25:36.315 --> 00:25:38.474
- up, new way of thinking for you, but

698
00:25:38.474 --> 00:25:40.130
- I would say it's not as important,

699
00:25:40.750 --> 00:25:42.830
- nowadays. So that brings up a good question.

700
00:25:42.830 --> 00:25:44.670
- What what are the differences between a map,

701
00:25:44.670 --> 00:25:45.730
- a list, and a dictionary?

702
00:25:46.029 --> 00:25:48.109
- So a dictionary and a map is mostly

703
00:25:48.109 --> 00:25:50.190
- the same. It's just that different languages call

704
00:25:50.190 --> 00:25:53.244
- them, in different ways. In Python, it's called,

705
00:25:53.785 --> 00:25:55.085
- a map... A dictionary.

706
00:25:55.465 --> 00:25:58.505
- In Perl, it's called, HashMap, if I recall

707
00:25:58.505 --> 00:26:01.384
- correctly, and in Golang, it's called, a map.

708
00:26:01.384 --> 00:26:04.025
- So that's just the same data structure, just

709
00:26:04.025 --> 00:26:04.525
- different,

710
00:26:05.144 --> 00:26:06.765
- programming languages call it,

711
00:26:07.305 --> 00:26:07.805
- differently.

712
00:26:08.430 --> 00:26:08.930
- And,

713
00:26:10.670 --> 00:26:12.130
- so the main difference between

714
00:26:12.430 --> 00:26:14.289
- a map and a and a list,

715
00:26:14.590 --> 00:26:16.269
- or a dictionary and a list would be

716
00:26:16.269 --> 00:26:16.769
- that,

717
00:26:17.710 --> 00:26:18.850
- a list is just

718
00:26:19.230 --> 00:26:21.325
- what the name implies. It's just a list

719
00:26:21.325 --> 00:26:24.044
- of elements. So you have one element after

720
00:26:24.044 --> 00:26:25.984
- the other. They may be sorted

721
00:26:26.444 --> 00:26:29.424
- in the same order as they're inserted in

722
00:26:29.644 --> 00:26:30.544
- the in the list.

723
00:26:31.325 --> 00:26:31.825
- While

724
00:26:32.125 --> 00:26:33.664
- a map or a dictionary,

725
00:26:34.524 --> 00:26:35.984
- they're usually not

726
00:26:36.580 --> 00:26:38.420
- ordered in a list. What they are is

727
00:26:38.420 --> 00:26:40.740
- just referenced by, by a key. So you

728
00:26:40.740 --> 00:26:43.080
- have a set of elements within the dictionary,

729
00:26:43.619 --> 00:26:45.140
- and the way that you access them is

730
00:26:45.140 --> 00:26:47.080
- by saying, like, okay, give me this particular

731
00:26:47.220 --> 00:26:49.940
- element. And then that particular element is just

732
00:26:49.940 --> 00:26:52.184
- referenced by this by this key. Yeah. And

733
00:26:52.184 --> 00:26:54.285
- I suppose that kinda ties back to algorithmic

734
00:26:54.345 --> 00:26:56.505
- efficiency too a little bit because if you

735
00:26:56.505 --> 00:26:58.984
- have a list of, you know, a million

736
00:26:58.984 --> 00:27:00.825
- different data points, you would have to loop

737
00:27:00.825 --> 00:27:02.585
- over the entire list to find something. Right?

738
00:27:02.585 --> 00:27:04.105
- Whereas with the dictionary, you can just do

739
00:27:04.105 --> 00:27:05.730
- a a hash lookup on the key. So

740
00:27:05.890 --> 00:27:08.289
- algorithmically, it's a lot more efficient depending on

741
00:27:08.289 --> 00:27:09.730
- what exactly you're trying to do with the

742
00:27:09.730 --> 00:27:10.230
- program.

743
00:27:10.849 --> 00:27:12.609
- Yeah. It depends on what you're trying to

744
00:27:12.609 --> 00:27:14.390
- get out of the right because

745
00:27:14.769 --> 00:27:16.849
- if you can structure it in the way

746
00:27:16.849 --> 00:27:17.829
- where you have

747
00:27:19.730 --> 00:27:20.470
- a key

748
00:27:21.250 --> 00:27:23.625
- to get things, then that's fine. But sometimes

749
00:27:23.625 --> 00:27:25.565
- you can't. Right? Sometimes it's...

750
00:27:25.944 --> 00:27:28.605
- Yeah. I mean, those data structure are mostly

751
00:27:29.304 --> 00:27:29.804
- interesting

752
00:27:30.345 --> 00:27:31.565
- when you're

753
00:27:32.105 --> 00:27:33.005
- talking about

754
00:27:33.544 --> 00:27:35.820
- efficiency. Like, you really need to

755
00:27:36.120 --> 00:27:38.220
- to, like, make your code,

756
00:27:38.680 --> 00:27:41.240
- like, super efficient because of what you're doing.

757
00:27:41.240 --> 00:27:43.240
- And then it's when it's interesting to know,

758
00:27:43.240 --> 00:27:45.960
- like, the, like, the very deep details of

759
00:27:45.960 --> 00:27:47.429
- those data structure, how they're implemented in the

760
00:27:47.429 --> 00:27:47.720
- in the language, and and and whatnot. But

761
00:27:47.720 --> 00:27:48.470
- that's probably

762
00:27:55.014 --> 00:27:57.115
- programming... As network parameters because

763
00:27:57.494 --> 00:27:59.654
- we're all... We're always gonna be bound by

764
00:27:59.654 --> 00:28:02.214
- IO anyway. Mhmm. So the CPU is gonna

765
00:28:02.214 --> 00:28:04.619
- be idle anyway most of the time. So

766
00:28:04.619 --> 00:28:07.119
- so you would say you're bounded mostly by

767
00:28:07.500 --> 00:28:09.580
- the way... The most logical way to structure

768
00:28:09.580 --> 00:28:11.259
- the data in a way that makes it

769
00:28:11.259 --> 00:28:12.640
- easy to read the code

770
00:28:13.019 --> 00:28:15.680
- or understand what's going on rather than

771
00:28:15.980 --> 00:28:16.954
- as much around,

772
00:28:17.974 --> 00:28:20.454
- making the program efficient. Because I know in

773
00:28:20.454 --> 00:28:22.615
- c, we go to great lengths to make

774
00:28:22.615 --> 00:28:23.115
- things

775
00:28:23.734 --> 00:28:26.714
- as efficient as possible in many cases using

776
00:28:26.934 --> 00:28:29.414
- data structures that most people wouldn't even begin

777
00:28:29.414 --> 00:28:30.154
- to understand.

778
00:28:31.335 --> 00:28:32.599
- So that's that's interesting.

779
00:28:33.539 --> 00:28:35.559
- Yeah. Correct. I mean, if you're writing BGP

780
00:28:35.859 --> 00:28:38.660
- as the as the demon to to run

781
00:28:38.660 --> 00:28:40.259
- it in your machine, like, sure. Like, you're

782
00:28:40.259 --> 00:28:41.880
- gonna have to be dealing with,

783
00:28:42.900 --> 00:28:45.539
- a stream of bytes to make everything as

784
00:28:45.539 --> 00:28:47.319
- efficient as as possible,

785
00:28:48.515 --> 00:28:50.615
- like three s and other data structures.

786
00:28:50.994 --> 00:28:52.615
- But if you're just trying to automate,

787
00:28:53.315 --> 00:28:55.095
- like, the, like, the

788
00:28:55.474 --> 00:28:58.615
- deployment of configuration to this particular BGP instance,

789
00:28:58.914 --> 00:29:01.894
- then just make sure that you optimize for

790
00:29:01.954 --> 00:29:04.079
- for the human that is gonna be,

791
00:29:05.099 --> 00:29:07.259
- dealing with the system rather than for the

792
00:29:07.259 --> 00:29:09.599
- machine. Because in the end, I mean,

793
00:29:09.900 --> 00:29:11.599
- you're talking like a few milliseconds

794
00:29:11.980 --> 00:29:13.519
- of latency between your,

795
00:29:14.299 --> 00:29:15.359
- management station

796
00:29:16.195 --> 00:29:18.455
- and the system that you're configuring anyway.

797
00:29:19.234 --> 00:29:21.875
- So saving a few nanoseconds is gonna be

798
00:29:21.875 --> 00:29:22.695
- just negligible.

799
00:29:23.075 --> 00:29:25.095
- Yeah. Yeah. And if you use something like,

800
00:29:25.555 --> 00:29:27.715
- Napalm or NetMico in order to log into

801
00:29:27.715 --> 00:29:28.535
- a box and,

802
00:29:29.795 --> 00:29:32.580
- get data back or a gRPC call or

803
00:29:32.580 --> 00:29:34.820
- or whatever that... Like you're saying, that's IO

804
00:29:34.820 --> 00:29:36.100
- bound. So it's gonna take a lot of

805
00:29:36.100 --> 00:29:38.100
- time for that query to go through the

806
00:29:38.100 --> 00:29:38.600
- network,

807
00:29:39.299 --> 00:29:41.880
- whereas the the time that the CPU actually

808
00:29:42.100 --> 00:29:43.865
- takes to process that and parse the data

809
00:29:43.865 --> 00:29:45.884
- that you get back is, like, fractional.

810
00:29:47.224 --> 00:29:47.724
- So...

811
00:29:48.105 --> 00:29:50.904
- Yeah. Yeah. Awesome. So if you were... Since

812
00:29:50.904 --> 00:29:51.964
- you've made the transition,

813
00:29:52.424 --> 00:29:54.024
- if you were talking to a network engineer

814
00:29:54.024 --> 00:29:55.964
- today who wanted to get started in programming

815
00:29:56.700 --> 00:29:58.940
- or just even learning the skill sets, where

816
00:29:58.940 --> 00:30:00.299
- would you tell them to start? Is there

817
00:30:00.299 --> 00:30:02.460
- a book? Is there just go do it?

818
00:30:02.460 --> 00:30:04.139
- Or how would you how would you start

819
00:30:04.139 --> 00:30:05.440
- out talking to people?

820
00:30:06.380 --> 00:30:08.159
- So I would suggest

821
00:30:08.539 --> 00:30:09.440
- going through

822
00:30:09.894 --> 00:30:10.394
- places

823
00:30:10.775 --> 00:30:11.515
- like Coursera,

824
00:30:12.054 --> 00:30:12.554
- edX.

825
00:30:12.934 --> 00:30:13.515
- I know

826
00:30:13.894 --> 00:30:15.994
- that Kirk Byers, who is the,

827
00:30:16.535 --> 00:30:18.634
- author of Nemeco has also some

828
00:30:19.414 --> 00:30:19.914
- training

829
00:30:20.535 --> 00:30:21.755
- courses. I would suggest

830
00:30:22.134 --> 00:30:23.755
- just pick one of these and

831
00:30:24.375 --> 00:30:26.250
- go through through them. And

832
00:30:26.630 --> 00:30:29.609
- when you have completed any of these courses,

833
00:30:29.669 --> 00:30:31.609
- just try to jump into any

834
00:30:32.069 --> 00:30:33.849
- open source project and start

835
00:30:34.230 --> 00:30:36.490
- helping there as much as you can

836
00:30:37.029 --> 00:30:39.464
- learn the the tools, the processes,

837
00:30:39.924 --> 00:30:40.424
- and

838
00:30:40.884 --> 00:30:43.304
- and things like that. I... Most most

839
00:30:44.085 --> 00:30:45.924
- most people will just do one of these

840
00:30:45.924 --> 00:30:47.544
- courses and not do the

841
00:30:47.845 --> 00:30:48.904
- open source thing.

842
00:30:49.764 --> 00:30:50.264
- And

843
00:30:50.804 --> 00:30:51.210
- that's

844
00:30:51.849 --> 00:30:53.929
- a bit of a pity, especially when you

845
00:30:53.929 --> 00:30:56.490
- are working alone because then you're missing out

846
00:30:56.490 --> 00:30:57.710
- on a lot of,

847
00:30:58.329 --> 00:31:00.109
- interest in tooling. Like, how to use

848
00:31:00.970 --> 00:31:01.950
- gate when

849
00:31:02.250 --> 00:31:02.750
- you're,

850
00:31:04.534 --> 00:31:07.015
- several people working together. How you... How to

851
00:31:07.015 --> 00:31:07.515
- use

852
00:31:07.974 --> 00:31:11.194
- a CI system for testing. How to use,

853
00:31:12.534 --> 00:31:15.095
- testing libraries and and things like that. So

854
00:31:15.095 --> 00:31:16.554
- that's also an important,

855
00:31:17.174 --> 00:31:20.289
- skill that people often overlook. And it's super

856
00:31:20.289 --> 00:31:22.609
- hard to get if you're working alone in

857
00:31:22.609 --> 00:31:23.269
- in your,

858
00:31:23.730 --> 00:31:26.950
- particular company. So I think it's interesting to,

859
00:31:27.170 --> 00:31:30.130
- after you have done some learning, try to

860
00:31:30.130 --> 00:31:30.869
- get into

861
00:31:31.490 --> 00:31:33.445
- a larger team even if that larger team

862
00:31:33.445 --> 00:31:35.445
- is just some open source project. Alright. Well,

863
00:31:35.445 --> 00:31:37.445
- thanks David for coming on, and we'll hope

864
00:31:37.445 --> 00:31:39.205
- to talk to you again in the near

865
00:31:39.205 --> 00:31:39.705
- future.

866
00:31:40.325 --> 00:31:42.345
- Thank you for having me. Thank you, David.

867
00:32:02.835 --> 00:32:04.914
- Thank you for joining us. You can find

868
00:32:04.914 --> 00:32:07.440
- the hedge at rule11.tech.