Teach Yourself Programming in Ten Years by Peter Norvig (2001)
1–10 of 32 posts
Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#2Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#3It good though...
Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#4This gets posted about once a week here. It good though...
Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#5Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#6I'd be interested in current opinions on this. e.g. is there something one should look at before Icon if they want to lean about coroutines?
Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#7I think this article gives excellent advice, and it has certainly worked for me. I always recommend it to people just starting out.
Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#8http://news.ycombinator.com/item?id=3278080
In a brief email exchange I Had with him, he even suggested he may rewrite this essay to address the fact that it is often used (inappropriately, obviously) to bludgeon new programmers into thinking that they're not actually programmers.
I think often on HN this essay is used to create some kind of caste system based on longevity in the biz or number of hours coded, which is horse shit.
Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#9This gets posted about once a week here. It good though...
Yes - hardly counts as "news". Why does this get posted so often, and how on earth does it get to the front page of Hacker News?
Why does it get to the front page? Because it's relevant and good, of course, unlike almost everything that is merely new.
I'm pleased to see more classics turning up on HN; Periodic reviews of the classics are the only way to get new visitors onto the same page as older ones.
Re: Teach Yourself Programming in Ten Years by Peter Norvig (2001)
#10Learn at least a half dozen programming languages. Include one language that supports class abstractions (like Java or C++), one that supports functional abstraction (like Lisp or ML), one that supports syntactic abstraction (like Lisp), one that supports declarative specifications (like Prolog or C++ templates), one that supports coroutines (like Icon or Scheme), and one that supports parallelism (like Sisal). I'd b…
See also: Actors, async and reactive programming