Good stuff. However, I don't think that "learning to code," ins being used in the same sense that Terence Eden meant. I think what Quinn Rohlf is trying to say

Good stuff. However, I don't think that "learning to code," ins being used in the same sense that Terence Eden meant. I think what Quinn Rohlf is trying to say is, "Learn how computers work." And what Eden is trying to say is, "Learn how to be logical." And for a hat trick of HNs submissions, what Andrew Wulf is trying to say over at thecodist.com is that in general you should just, "Learn how to keep learning." Taken as a sum of collective knowledge, I think everyone is right in this case. I think the general idea people are trying to get at is this: 1. To work in technology, you must love learning. (Don't get steamrolled). 2. To work in technology, you should know how computers really work. (Learn about C.) 3. Working in technology is not about learning where to but the curly brackets. It's about learning how to think logically. (Learn Computer Science.) In this sense, I think a great way to get started is by working on a project that you love and in a medium you love. Then as you start hitting limits, descend to C and learn algorithms.