3 ms·
I agree with Norvig that programming is a long-haul commitment...not much different than any other form of literacy, except in most schools, we're forced to go
by danso 12y ago
I agree with Norvig that programming is a long-haul commitment...not much different than any other form of literacy, except in most schools, we're forced to go through 12+ years of English/math (and even then, a pretty high number of college students are still at a remedial level).
One thing he didn't address that I'd like to see more explored: how much of learning programming is learning the "mechanics"? By that, I mean everything from knowing how to Google effectively, to learning an IDE, to your OS keyboard shortcuts....I'd have to imagine that learning how to program 30 years ago can be fundamentally different than it is now, based on the _conveniences_ we have available to us.
When teaching beginners, I've been trying to stress the importance of good mechanics/practice...I've seen students spend literally 4-5 hours on some typo-caused bug (such as `rm`ing something accidentally) because they didn't take the few minutes to get use to tab-autocomplete. Or use a proper text editor with syntax highlighting. Learning anything is a race against time and energy...the all-night debugging sessions add up, and people who are intellectually capable end up dropping out simply because they've run out of time (or believe they have, which is a sensation that grows as you get older).