[169-174] I also took a systems programming class, which followed the C programming class that I took the term before. It’s computer engineering, and I’ve always wanted to know, actually conceptually understand how computers work. And this class got me one step closer. It talked more about how the code actually interacted with the kernel of the computer, the basic operating system. And it was challenging, but it went all right. Not too bad. I feel like I learned a lot.
[197-205] So the challenging part about that class was that it was heavily theoretical and conceptual, and involved less programming than I thought it would. It was very much coding theory and how to avoid bad coding practices, and how the actual memory of a computer functions and stuff like that. And I was really not expecting to learn that through lectures. I was expecting to do some coding to figure out how to be better at coding. And it took me a couple of weeks to realize that I have to read the lecture notes. So, when I realized that basically he was going to assess us largely on knowing the theory instead of doing the practice, I started learning the theory.