|
|
|
|
|
by All4All
1341 days ago
|
|
This is great. It brings me back to the early days in my undergraduate trying to get a grasp on programming. The "Intro to Programming" i.e. Java 101 was my first experience with programming in general, and nearly made me drop out of the CS program altogether. Something about the high-level learning and lack of understanding what was going on behind the scenes made it very difficult to grasp. It wasn't until I took a course in C the following semester that I finally began to grasp the actions behind the code I was writing. Although the code was much more difficult to write, I found the laborious process of writing C made it much easier to grasp the underlying functionality. There's benefit in not having to understand the underlying intricacies of the code that you're writing, but there is something about that knowledge that makes it just so much more engaging. |
|
I don't know. All these abstractions eventually leak. We often run into problems that can only be solved by fully understanding the software layers we're building on top of. I think that this cancels out any initial benefits.
> there is something about that knowledge that makes it just so much more engaging
Agreed. It's such a joy to discover the underlying technology. Lots of people don't care about these "already solved problems" but I find them deeply interesting.