WEBVTT

1
00:00:00.040 --> 00:00:03.319
<v Speaker 1>Welcome back everyone to the deep dive. You know, we

2
00:00:03.399 --> 00:00:07.879
<v Speaker 1>get a lot of requests, and this one was pretty interesting.

3
00:00:08.000 --> 00:00:10.679
<v Speaker 1>This time we're going deep on C programming.

4
00:00:10.759 --> 00:00:11.279
<v Speaker 2>Oh nice.

5
00:00:11.480 --> 00:00:15.359
<v Speaker 1>Yeah, so many listeners are I think curious, you know,

6
00:00:15.919 --> 00:00:19.600
<v Speaker 1>about how C programming is actually used in the real

7
00:00:19.640 --> 00:00:23.760
<v Speaker 1>world and what kind of practical applications it has. And

8
00:00:23.800 --> 00:00:25.920
<v Speaker 1>we happen to have a well not happen to have

9
00:00:25.960 --> 00:00:29.079
<v Speaker 1>We got a C programming textbook. Oh cool, and we

10
00:00:29.120 --> 00:00:32.600
<v Speaker 1>also have the table of contents, which is really cool,

11
00:00:32.640 --> 00:00:34.960
<v Speaker 1>I think. So. I mean we can kind of get

12
00:00:35.000 --> 00:00:37.439
<v Speaker 1>like a cheat sheet overview of this without having to

13
00:00:37.439 --> 00:00:40.000
<v Speaker 1>read through pages and pages. Code love it. So we

14
00:00:40.039 --> 00:00:41.799
<v Speaker 1>can already tell this deep dive is going to be

15
00:00:42.280 --> 00:00:43.000
<v Speaker 1>pretty interesting.

16
00:00:43.119 --> 00:00:45.439
<v Speaker 2>Yeah. Sea is everywhere, even if people don't realize it,

17
00:00:45.560 --> 00:00:49.039
<v Speaker 2>So this will be fun to like reveal the sea

18
00:00:49.119 --> 00:00:49.799
<v Speaker 2>behind the curtain.

19
00:00:49.799 --> 00:00:53.399
<v Speaker 1>I guess, yes, exactly. So the book is called Practical

20
00:00:53.439 --> 00:00:57.240
<v Speaker 1>C Programming Solutions for Modern Sea Developers. I can get

21
00:00:57.359 --> 00:01:01.439
<v Speaker 1>this ready for this. It's dedicated to Gudo van Rossom.

22
00:01:01.600 --> 00:01:04.359
<v Speaker 2>Oh wow, who is the Python.

23
00:01:04.239 --> 00:01:06.719
<v Speaker 1>The creator of Python. Yeah, it's like finding out that

24
00:01:06.840 --> 00:01:10.000
<v Speaker 1>you know, your favorite modern artist was inspired by like

25
00:01:10.079 --> 00:01:11.359
<v Speaker 1>a Renaissance master.

26
00:01:11.359 --> 00:01:13.920
<v Speaker 2>You know, totally. I mean that says a lot. You know.

27
00:01:13.959 --> 00:01:15.879
<v Speaker 2>You think Python is like, you know, so easy to

28
00:01:16.000 --> 00:01:20.200
<v Speaker 2>use everything, but it all goes back to C. Yeah,

29
00:01:20.480 --> 00:01:23.359
<v Speaker 2>Like understanding C is almost like seeing how the gears

30
00:01:23.400 --> 00:01:24.239
<v Speaker 2>really turn.

31
00:01:24.200 --> 00:01:25.280
<v Speaker 1>Oh yeah under the hood.

32
00:01:25.359 --> 00:01:29.400
<v Speaker 2>Yeah yeah, totally. Okay, So the author B. M. Harwani

33
00:01:29.879 --> 00:01:34.760
<v Speaker 2>has written about like everything I'm talking jQuery, Python, Wow,

34
00:01:34.879 --> 00:01:39.760
<v Speaker 2>Android clearly knows his stuff, definitely, And I love that

35
00:01:39.840 --> 00:01:43.000
<v Speaker 2>the book takes a kind of a cookbook approach, you know,

36
00:01:43.200 --> 00:01:46.359
<v Speaker 2>like practical solutions, ready to use, kind perfect for a

37
00:01:46.359 --> 00:01:46.879
<v Speaker 2>deep dive.

38
00:01:47.079 --> 00:01:49.680
<v Speaker 1>You said you wanted to see see an action, not

39
00:01:49.840 --> 00:01:52.840
<v Speaker 1>just theory, right, I think this is going to work

40
00:01:52.879 --> 00:01:53.319
<v Speaker 1>really well.

41
00:01:53.400 --> 00:01:56.159
<v Speaker 2>I think so too. Even just glancing at the table

42
00:01:56.200 --> 00:01:59.280
<v Speaker 2>of contents, We've got embedded software and IoT, which is

43
00:01:59.439 --> 00:02:03.959
<v Speaker 2>you know, huge these days, improving the performance of your code.

44
00:02:04.480 --> 00:02:05.560
<v Speaker 2>Who wouldn't want that, right?

45
00:02:05.799 --> 00:02:07.400
<v Speaker 1>Yeah? And it just keeps going And.

46
00:02:07.359 --> 00:02:10.159
<v Speaker 2>Those are great examples of why C is still relevant today.

47
00:02:10.479 --> 00:02:14.240
<v Speaker 2>You know, like IoT, that's all about interacting directly with hardware,

48
00:02:14.439 --> 00:02:18.159
<v Speaker 2>which C excels at, right. And when it comes to

49
00:02:18.719 --> 00:02:22.719
<v Speaker 2>you know, speed and efficiency, nothing beats C pretty much.

50
00:02:22.800 --> 00:02:24.520
<v Speaker 1>That's what I'm hearing Okay, so now I'm looking at

51
00:02:24.560 --> 00:02:27.000
<v Speaker 1>the recipes. These are like a little mini projects. Look,

52
00:02:27.439 --> 00:02:30.479
<v Speaker 1>and there's one called toggling the port of a micro

53
00:02:30.560 --> 00:02:36.520
<v Speaker 1>controller in embedded C. Okay, in parentheses blinking LED.

54
00:02:37.960 --> 00:02:42.400
<v Speaker 2>I love that one. Everyone loves LED's classic. Gotta love it. Yeah.

55
00:02:42.479 --> 00:02:45.319
<v Speaker 1>So, I mean it might seem simple, but it shows

56
00:02:45.439 --> 00:02:48.919
<v Speaker 1>how C controls hardware at such a basic level, right,

57
00:02:49.039 --> 00:02:51.319
<v Speaker 1>which is I think why it's used in so many

58
00:02:51.360 --> 00:02:52.280
<v Speaker 1>devices exactly.

59
00:02:52.360 --> 00:02:55.080
<v Speaker 2>Yeah, Like think of I don't know, the little LED

60
00:02:55.199 --> 00:02:58.840
<v Speaker 2>on your router that blanks to show it's working, right, Yeah,

61
00:02:58.960 --> 00:03:00.319
<v Speaker 2>probably C code run that.

62
00:03:01.280 --> 00:03:04.680
<v Speaker 1>Okay, this next one is a little more, a little

63
00:03:04.719 --> 00:03:09.439
<v Speaker 1>more complex, finding the transpose of a matrix using pointers.

64
00:03:09.560 --> 00:03:12.039
<v Speaker 1>I get that matrices are like these grids of numbers,

65
00:03:12.639 --> 00:03:16.039
<v Speaker 1>But what exactly are pointers and why are they so

66
00:03:16.080 --> 00:03:16.840
<v Speaker 1>important in C?

67
00:03:18.319 --> 00:03:23.400
<v Speaker 2>Yeah, this is a good question. Pointers. They're really powerful, Yeah,

68
00:03:23.400 --> 00:03:25.159
<v Speaker 2>but people often find them confusing.

69
00:03:25.360 --> 00:03:26.159
<v Speaker 1>I can imagine.

70
00:03:26.400 --> 00:03:30.360
<v Speaker 2>Basically, they let you work with memory addresses. Yeah, like

71
00:03:30.439 --> 00:03:33.280
<v Speaker 2>the exact location of data in the computer's memory.

72
00:03:33.639 --> 00:03:36.039
<v Speaker 1>So instead of just knowing like the street name, you

73
00:03:36.120 --> 00:03:38.400
<v Speaker 1>have the exact GPS coordinates of a house.

74
00:03:38.759 --> 00:03:41.159
<v Speaker 2>Perfect analogy. Yeah, and that means C code can jump

75
00:03:41.280 --> 00:03:43.479
<v Speaker 2>right to the data it needs, okay, without having to

76
00:03:43.560 --> 00:03:46.599
<v Speaker 2>search through like a whole neighborhood of memory, which is

77
00:03:46.800 --> 00:03:48.199
<v Speaker 2>one reason why SEE is so efficient.

78
00:03:48.319 --> 00:03:51.439
<v Speaker 1>So efficient, And I see another recipe that caught my eye. Okay,

79
00:03:51.560 --> 00:03:55.719
<v Speaker 1>encrypting a file sounds kind of spy movie ish, right.

80
00:03:55.719 --> 00:03:59.960
<v Speaker 2>But honestly that one is super relevant to like everyone's life.

81
00:04:00.439 --> 00:04:04.360
<v Speaker 2>How so well, encryption is what keeps our online transaction secure, oh,

82
00:04:04.520 --> 00:04:07.639
<v Speaker 2>protects our passwords, make sure digital communication is private.

83
00:04:07.960 --> 00:04:11.199
<v Speaker 1>Oh okay, gotcha. So this recipe shows how C can

84
00:04:11.280 --> 00:04:15.520
<v Speaker 1>like scramble of file's contents, make it unreadable without.

85
00:04:15.199 --> 00:04:20.560
<v Speaker 2>A key exactly. It probably uses math operations like bitshifting

86
00:04:20.600 --> 00:04:23.839
<v Speaker 2>and xor it shiftingah to transform the data so only

87
00:04:23.879 --> 00:04:25.519
<v Speaker 2>someone with the right key can reverse it.

88
00:04:25.680 --> 00:04:30.480
<v Speaker 1>Wow, so we've gone from blinking LEDs to encrypting files.

89
00:04:30.519 --> 00:04:32.560
<v Speaker 1>It's kind of blowing my mind how much C is

90
00:04:32.600 --> 00:04:33.680
<v Speaker 1>involved in all this tech.

91
00:04:33.800 --> 00:04:34.920
<v Speaker 2>It really is foundational.

92
00:04:35.040 --> 00:04:37.680
<v Speaker 1>Yeah all right. So there's this diagram early in the book,

93
00:04:37.720 --> 00:04:41.199
<v Speaker 1>figure one point ten. It shows how matrix elements are

94
00:04:41.240 --> 00:04:44.160
<v Speaker 1>stored in memory. Maybe we can use this to illustrate

95
00:04:44.160 --> 00:04:45.040
<v Speaker 1>some of these concepts.

96
00:04:45.079 --> 00:04:48.240
<v Speaker 2>Ooh good idea visualizing this stuff is always helpful.

97
00:04:48.000 --> 00:04:51.439
<v Speaker 1>Yeah, right, A picture's worth a thousand lines of code exactly.

98
00:04:51.680 --> 00:04:53.160
<v Speaker 1>So let's dive into that matrix.

99
00:04:53.240 --> 00:04:55.680
<v Speaker 2>All right, let's see how C sees those elements. So

100
00:04:55.720 --> 00:04:59.439
<v Speaker 2>figure one point ten. It's it's a grid like a spreadsheet,

101
00:05:00.160 --> 00:05:03.439
<v Speaker 2>the matrix. But the way C stores this in memory,

102
00:05:03.839 --> 00:05:06.759
<v Speaker 2>it's actually a sequence like one element after the other

103
00:05:06.879 --> 00:05:07.480
<v Speaker 2>row by row.

104
00:05:07.759 --> 00:05:10.519
<v Speaker 1>Okay, So it's not like C sees the neat rosen

105
00:05:10.600 --> 00:05:12.839
<v Speaker 1>columns like we do when we look at the diagram, right.

106
00:05:12.920 --> 00:05:16.079
<v Speaker 2>C doesn't like inherently get rose and columns. It just

107
00:05:16.120 --> 00:05:21.160
<v Speaker 2>sees this long line of elements in memory, like imagine

108
00:05:21.360 --> 00:05:23.560
<v Speaker 2>a line of people waiting for a concert.

109
00:05:23.759 --> 00:05:25.959
<v Speaker 1>Okay, okay, I get that. But then how to C

110
00:05:26.240 --> 00:05:28.560
<v Speaker 1>know where one row ends and the next one begins

111
00:05:28.600 --> 00:05:30.120
<v Speaker 1>if it's all one big line.

112
00:05:30.560 --> 00:05:33.120
<v Speaker 2>Well, when you define a matrix in C, you tell

113
00:05:33.160 --> 00:05:36.199
<v Speaker 2>it how many rows and columns it has, like two

114
00:05:36.199 --> 00:05:39.199
<v Speaker 2>by three for example, right right, And using that, C

115
00:05:39.519 --> 00:05:43.560
<v Speaker 2>can actually calculate the exact memory address of each element.

116
00:05:43.759 --> 00:05:45.839
<v Speaker 1>So if I want to grab the element in say

117
00:05:45.879 --> 00:05:49.160
<v Speaker 1>the first row, second column, C does some math behind

118
00:05:49.199 --> 00:05:51.199
<v Speaker 1>the scenes to figure out exactly where it is, and

119
00:05:51.279 --> 00:05:52.639
<v Speaker 1>that memory line yep.

120
00:05:52.879 --> 00:05:55.879
<v Speaker 2>It's like having a seating chart for that concert line.

121
00:05:55.879 --> 00:05:58.920
<v Speaker 2>You know. Yeah, Row one, seat two C knows exactly

122
00:05:58.920 --> 00:06:00.959
<v Speaker 2>where to go. And this is where pointers come.

123
00:06:00.879 --> 00:06:02.759
<v Speaker 1>In, right right, like those GPS coordinates you were.

124
00:06:02.680 --> 00:06:04.800
<v Speaker 2>Talking about, exactly. It gives you direct access. You can

125
00:06:04.839 --> 00:06:07.439
<v Speaker 2>just jump to that memory location, no need to like

126
00:06:07.519 --> 00:06:08.480
<v Speaker 2>walk down the whole line.

127
00:06:08.519 --> 00:06:10.839
<v Speaker 1>Oh I see. So it's like having backstage passes.

128
00:06:11.079 --> 00:06:13.120
<v Speaker 2>Haha. Yeah, you get to bypass the line and go

129
00:06:13.199 --> 00:06:15.519
<v Speaker 2>right to where you need to be. So in that

130
00:06:15.600 --> 00:06:20.279
<v Speaker 2>matrix transpose recipe, C can use pointers to swap elements

131
00:06:20.319 --> 00:06:24.920
<v Speaker 2>around without having to copy entire rows or columns. Super efficient.

132
00:06:25.120 --> 00:06:27.600
<v Speaker 1>That's amazing. But earlier you said pointers can be a

133
00:06:27.639 --> 00:06:30.079
<v Speaker 1>bit tricky too, Like what's the downside of having this

134
00:06:30.240 --> 00:06:31.519
<v Speaker 1>much control over memory?

135
00:06:31.639 --> 00:06:34.360
<v Speaker 2>Well, you gotta be careful. One classic sea pitfall is

136
00:06:34.399 --> 00:06:38.079
<v Speaker 2>the buffer overflow. Imagine you have like a container. Yeah,

137
00:06:38.120 --> 00:06:41.199
<v Speaker 2>it has a fixed size, that's your memory buffer. But

138
00:06:41.240 --> 00:06:42.759
<v Speaker 2>then you try to put more stuff in.

139
00:06:43.199 --> 00:06:45.439
<v Speaker 1>Oh, it overflows, like everything crashes.

140
00:06:45.560 --> 00:06:49.199
<v Speaker 2>It can yeah, data gets corrupted the program like crash,

141
00:06:49.240 --> 00:06:52.079
<v Speaker 2>and it can even create security holes that hackers can

142
00:06:52.079 --> 00:06:52.800
<v Speaker 2>take advantage of.

143
00:06:52.959 --> 00:06:56.120
<v Speaker 1>Oh wow, okay, so it's like with great power comes

144
00:06:56.160 --> 00:06:58.519
<v Speaker 1>great responsibility. Even in C programming.

145
00:06:58.959 --> 00:07:01.399
<v Speaker 2>Definitely, you have the power to directly work with memory,

146
00:07:01.439 --> 00:07:03.160
<v Speaker 2>which you really need to know what you're doing.

147
00:07:03.399 --> 00:07:05.959
<v Speaker 1>Yeah, it makes sense. It's like having a super powerful

148
00:07:06.000 --> 00:07:09.279
<v Speaker 1>sports car, exciting to drive, but you better know how

149
00:07:09.279 --> 00:07:09.839
<v Speaker 1>to handle it.

150
00:07:10.040 --> 00:07:14.319
<v Speaker 2>Perfect analogy. To really master C, you need to understand

151
00:07:14.360 --> 00:07:15.800
<v Speaker 2>what's going on at the memory level.

152
00:07:15.959 --> 00:07:19.079
<v Speaker 1>Yeah, it's deep. Okay, This whole memory and pointers thing

153
00:07:19.279 --> 00:07:22.759
<v Speaker 1>is really making me appreciate how C works under the hood.

154
00:07:22.839 --> 00:07:25.439
<v Speaker 2>It's fascinating, right, and this is just the tip of

155
00:07:25.480 --> 00:07:26.000
<v Speaker 2>the iceberg.

156
00:07:26.079 --> 00:07:28.279
<v Speaker 1>Really, I know we still have all those other recipes

157
00:07:28.319 --> 00:07:30.800
<v Speaker 1>to explore. I'm really curious about that encryption one.

158
00:07:30.920 --> 00:07:33.199
<v Speaker 2>Yeah, me too. I think it's a good example of

159
00:07:33.240 --> 00:07:37.360
<v Speaker 2>how c's low level control can be used for security.

160
00:07:36.920 --> 00:07:40.519
<v Speaker 1>Stuff exactly, making sure only the right people can access

161
00:07:40.600 --> 00:07:41.040
<v Speaker 1>the data.

162
00:07:41.279 --> 00:07:44.399
<v Speaker 2>Yep, exactly. Like think about when you enter your credit

163
00:07:44.439 --> 00:07:48.519
<v Speaker 2>card info online, oh right, or send a confidential email.

164
00:07:49.360 --> 00:07:53.079
<v Speaker 2>Encryption is working behind the scenes to protect that information.

165
00:07:53.720 --> 00:07:56.079
<v Speaker 2>And a lot of the time that encryption is built

166
00:07:56.120 --> 00:07:56.839
<v Speaker 2>on C code.

167
00:07:56.920 --> 00:07:59.680
<v Speaker 1>That's incredible. C is like the secret language of cybersecurity.

168
00:08:00.360 --> 00:08:03.240
<v Speaker 2>You could say that it's great for these complex encryption algorithms.

169
00:08:03.360 --> 00:08:05.879
<v Speaker 1>Okay, well, let's switch gears for a second and talk

170
00:08:05.920 --> 00:08:08.519
<v Speaker 1>about that chapter on embedded software and IoT. I want

171
00:08:08.560 --> 00:08:11.399
<v Speaker 1>to see how C plays into the world of like

172
00:08:11.560 --> 00:08:13.720
<v Speaker 1>smart devices and all these connected systems.

173
00:08:14.079 --> 00:08:16.759
<v Speaker 2>Yeah, great idea. So remember how C is really good

174
00:08:16.759 --> 00:08:20.079
<v Speaker 2>at working directly with hardware. Yeah, well, with embedded systems,

175
00:08:20.120 --> 00:08:24.720
<v Speaker 2>we're talking about programming things like micro controllers, okay, sensors,

176
00:08:24.759 --> 00:08:27.519
<v Speaker 2>all the components that are like the brains of those devices.

177
00:08:27.720 --> 00:08:31.399
<v Speaker 1>So that blinking LED recipe, that's like a simple example

178
00:08:31.439 --> 00:08:33.600
<v Speaker 1>of C controlling a device.

179
00:08:33.440 --> 00:08:37.279
<v Speaker 2>Exactly, but think bigger instead of just an LED. Okay,

180
00:08:37.360 --> 00:08:41.240
<v Speaker 2>you could be controlling motors, reading data from temperature sensors, right,

181
00:08:41.600 --> 00:08:45.960
<v Speaker 2>processing GPS signals, all sorts of things, making decisions based

182
00:08:45.960 --> 00:08:46.919
<v Speaker 2>on real time input.

183
00:08:47.080 --> 00:08:50.200
<v Speaker 1>Wow. So things like I don't know my smart thrmostat,

184
00:08:50.240 --> 00:08:52.320
<v Speaker 1>my fitness jrugger, even my cars engine could all be

185
00:08:52.399 --> 00:08:53.360
<v Speaker 1>running C code.

186
00:08:53.720 --> 00:08:57.519
<v Speaker 2>Very likely. Yeah. C is perfect for these tiny, resource

187
00:08:57.559 --> 00:09:01.960
<v Speaker 2>constrained environments, you know, limited marine, limited processing power. It's

188
00:09:02.000 --> 00:09:04.120
<v Speaker 2>the workhorse behind a lot of the Internet of Things.

189
00:09:04.200 --> 00:09:06.480
<v Speaker 1>It's amazing to think this language that's been around for

190
00:09:06.519 --> 00:09:09.600
<v Speaker 1>so long is still powering so much of our modern world.

191
00:09:09.799 --> 00:09:12.440
<v Speaker 2>It really is. Yeah. C might not be flashy, but

192
00:09:12.639 --> 00:09:14.559
<v Speaker 2>it gets the job done and it does it well.

193
00:09:14.759 --> 00:09:16.879
<v Speaker 2>It's like having a set of really well made tools

194
00:09:17.279 --> 00:09:18.279
<v Speaker 2>that can build anything.

195
00:09:18.440 --> 00:09:20.960
<v Speaker 1>I'm really starting to see the influence of C everywhere.

196
00:09:21.000 --> 00:09:23.120
<v Speaker 1>It's like I'm seeing the code behind everything.

197
00:09:23.200 --> 00:09:26.360
<v Speaker 2>It's eye opening, isn't it. Okay, Well, before we wrap

198
00:09:26.399 --> 00:09:29.279
<v Speaker 2>things up with this deep dive into C programming, I

199
00:09:29.279 --> 00:09:32.120
<v Speaker 2>think we should talk a bit about what it's actually

200
00:09:32.279 --> 00:09:34.720
<v Speaker 2>like to work with this language.

201
00:09:34.360 --> 00:09:37.039
<v Speaker 1>Right, Yeah, SE can seem pretty cryptic. It's kind of

202
00:09:37.080 --> 00:09:40.240
<v Speaker 1>like we've pulled back the curtain on this whole hidden world,

203
00:09:40.399 --> 00:09:43.799
<v Speaker 1>you know. Yeah, running behind the scenes of our digital lives.

204
00:09:43.960 --> 00:09:46.600
<v Speaker 2>It's fascinating, it is, it is, And you know, C

205
00:09:46.840 --> 00:09:49.480
<v Speaker 2>might be old, but it's definitely not outdated.

206
00:09:49.639 --> 00:09:50.720
<v Speaker 1>No, not at all.

207
00:09:50.759 --> 00:09:53.960
<v Speaker 2>People think it's intimidating, and it can be, but it's

208
00:09:55.360 --> 00:09:58.519
<v Speaker 2>also elegant, you know, like there's a simplicity to it

209
00:09:58.639 --> 00:10:00.720
<v Speaker 2>and once you to understand it, it's really satisfying.

210
00:10:00.879 --> 00:10:03.799
<v Speaker 1>Yeah. I bet. But let's be real. See, he's got

211
00:10:03.799 --> 00:10:08.559
<v Speaker 1>this reputation for being like tricky, prone to errors, especially

212
00:10:08.559 --> 00:10:10.480
<v Speaker 1>with all this low level stuff. We've been talking about.

213
00:10:10.639 --> 00:10:13.519
<v Speaker 1>What kind of challenges do C programmers actually run into.

214
00:10:13.840 --> 00:10:17.279
<v Speaker 2>Yeah, you have to be very precise with C. One

215
00:10:17.519 --> 00:10:21.120
<v Speaker 2>tiny mistake can cascade into a whole bunch of problems,

216
00:10:21.480 --> 00:10:24.399
<v Speaker 2>bugs that are super hard to find. It's a language

217
00:10:24.399 --> 00:10:28.080
<v Speaker 2>that requires, you know, a lot of discipline, a deep

218
00:10:28.200 --> 00:10:29.399
<v Speaker 2>understanding of how it works.

219
00:10:29.519 --> 00:10:31.559
<v Speaker 1>So one wrong step and the whole thing could fall

220
00:10:31.559 --> 00:10:32.879
<v Speaker 1>apart pretty much.

221
00:10:33.000 --> 00:10:35.159
<v Speaker 2>Yeah, remember that buffer overflow.

222
00:10:34.799 --> 00:10:37.840
<v Speaker 1>We talked about, Yeah, with the container and then overfilling it.

223
00:10:37.879 --> 00:10:40.639
<v Speaker 2>Right exactly, trying to cram too much data into a

224
00:10:40.679 --> 00:10:44.559
<v Speaker 2>memory space that's too small. That's one common pitfall that

225
00:10:44.559 --> 00:10:50.120
<v Speaker 2>can lead to you know, data corruption, crashes, even security vulnerabilities,

226
00:10:50.159 --> 00:10:50.519
<v Speaker 2>and that's.

227
00:10:50.399 --> 00:10:52.559
<v Speaker 1>How hackers get into systems right a.

228
00:10:52.480 --> 00:10:55.440
<v Speaker 2>Lot of the time. Yeah, it's why C programmers have

229
00:10:55.519 --> 00:10:57.919
<v Speaker 2>to be super careful about security, especially when they're dealing

230
00:10:57.960 --> 00:11:04.039
<v Speaker 2>with anything from outside the program, user input, or network communication.

231
00:11:04.080 --> 00:11:05.320
<v Speaker 2>You got to make sure the data is clean.

232
00:11:05.440 --> 00:11:07.440
<v Speaker 1>So it's not just about making the code fast, it's

233
00:11:07.480 --> 00:11:09.000
<v Speaker 1>got to be safe too, exactly.

234
00:11:09.399 --> 00:11:12.279
<v Speaker 2>And another big challenge is memory management.

235
00:11:12.480 --> 00:11:15.919
<v Speaker 1>Right, we talked about that a bit, but like, remind

236
00:11:15.960 --> 00:11:17.200
<v Speaker 1>me why is that so tricky.

237
00:11:17.399 --> 00:11:20.879
<v Speaker 2>So in a lot of modern languages, memory is handled automatically,

238
00:11:21.240 --> 00:11:24.840
<v Speaker 2>but in C, yeah, the programmer has to do it manually.

239
00:11:24.600 --> 00:11:27.759
<v Speaker 1>Right, right, So what kind of problems can that cause?

240
00:11:28.159 --> 00:11:31.399
<v Speaker 2>It's really easy to mess up, Like you might forget

241
00:11:31.440 --> 00:11:34.399
<v Speaker 2>to release memory that you're not using anymore, and that

242
00:11:34.480 --> 00:11:36.279
<v Speaker 2>leads to what's called a memory leak.

243
00:11:36.519 --> 00:11:39.080
<v Speaker 1>Oh right, memory leaks. What happens then, Well.

244
00:11:38.960 --> 00:11:42.360
<v Speaker 2>It's like it's like a slow drip from a leaky faucet.

245
00:11:42.519 --> 00:11:45.080
<v Speaker 2>Each little leak might not seem like a big deal, right,

246
00:11:45.279 --> 00:11:48.399
<v Speaker 2>but over time it wastes a ton of water. Same

247
00:11:48.440 --> 00:11:50.440
<v Speaker 2>with memory leaks. You use up more and more memory,

248
00:11:50.440 --> 00:11:53.840
<v Speaker 2>and eventually your program might slow way down or even crash.

249
00:11:54.000 --> 00:11:57.159
<v Speaker 1>It's like digital clutter, just building up over time. Wow.

250
00:11:57.399 --> 00:12:00.600
<v Speaker 2>Yeah, good analogy. So to be a good sea programmer

251
00:12:01.200 --> 00:12:04.200
<v Speaker 2>it takes technical skill obviously, but also a lot of discipline.

252
00:12:04.279 --> 00:12:07.159
<v Speaker 2>You have to be really meticulous, right because finding those

253
00:12:07.200 --> 00:12:09.799
<v Speaker 2>bugs can be a real pain. It's almost like detective work.

254
00:12:09.919 --> 00:12:12.759
<v Speaker 2>You know, your piece together clues trying to figure out

255
00:12:12.799 --> 00:12:13.399
<v Speaker 2>what went wrong.

256
00:12:13.799 --> 00:12:16.960
<v Speaker 1>I never thought about it like that, but that makes sense. Okay, Well,

257
00:12:17.279 --> 00:12:21.279
<v Speaker 1>this deep dive has honestly been really really eye opening.

258
00:12:22.440 --> 00:12:26.120
<v Speaker 1>C might not be the most like trendy language, but

259
00:12:26.200 --> 00:12:27.919
<v Speaker 1>it's clearly essential.

260
00:12:27.840 --> 00:12:31.360
<v Speaker 2>Absolutely, and as rewarding too. Once you understand it, you

261
00:12:31.399 --> 00:12:32.600
<v Speaker 2>can do so much with it.

262
00:12:32.679 --> 00:12:35.799
<v Speaker 1>Okay, before we go, one last question. The book mentions

263
00:12:35.799 --> 00:12:39.200
<v Speaker 1>something called loop unrolling as a way to make code

264
00:12:39.320 --> 00:12:40.840
<v Speaker 1>run faster. What is that?

265
00:12:41.159 --> 00:12:44.960
<v Speaker 2>Oh? Yeah, so loop unrolling. It's basically a way to

266
00:12:45.279 --> 00:12:47.919
<v Speaker 2>reduce the overhead that comes with loops. So instead of

267
00:12:47.919 --> 00:12:51.480
<v Speaker 2>repeating instructions over and over, you just write them out explicitly.

268
00:12:51.480 --> 00:12:54.279
<v Speaker 2>It's kind of like streamlining a factory process. Okay, yeah,

269
00:12:54.320 --> 00:12:57.120
<v Speaker 2>instead of having one worker do the same thing ten times. Yeah,

270
00:12:57.159 --> 00:12:58.159
<v Speaker 2>you give each step.

271
00:12:57.919 --> 00:13:00.639
<v Speaker 1>Its own station, right, right, so things move faster, I

272
00:13:00.639 --> 00:13:01.559
<v Speaker 1>guess exactly.

273
00:13:01.679 --> 00:13:04.120
<v Speaker 2>Yeah, but it can also make the code harder to read.

274
00:13:04.320 --> 00:13:06.799
<v Speaker 1>It's a trade off, right, So programmers have to decide

275
00:13:06.840 --> 00:13:08.320
<v Speaker 1>what's best for each situation.

276
00:13:08.600 --> 00:13:10.519
<v Speaker 2>Yep, It's all about finding the right balance.

277
00:13:10.679 --> 00:13:13.600
<v Speaker 1>This has been amazing. We've gone from blinking LEDs to

278
00:13:13.879 --> 00:13:17.399
<v Speaker 1>encrypting files, from memory leaks to debugging mysteries.

279
00:13:17.679 --> 00:13:20.519
<v Speaker 2>It's been fun. I hope everyone listening has learned something

280
00:13:20.519 --> 00:13:24.360
<v Speaker 2>new about this, this amazing language that shapes so much

281
00:13:24.399 --> 00:13:25.279
<v Speaker 2>of our digital world.

282
00:13:25.399 --> 00:13:28.960
<v Speaker 1>Me too, and for all our listeners out there, keep exploring,

283
00:13:29.240 --> 00:13:32.120
<v Speaker 1>Try writing some C code yourself. See what you can create.

284
00:13:32.279 --> 00:13:35.120
<v Speaker 2>Yeah, get your hands dirty, dive into those recipes we

285
00:13:35.200 --> 00:13:39.039
<v Speaker 2>talked about, and never stop asking questions until next time.

286
00:13:39.159 --> 00:13:41.200
<v Speaker 2>Happy coding, everyone, Happy coding,