Category: Programming

Seibel: Though your job now doesn’t entail a lot of programming you still write programs for the essays on your web site. When you’re writing these little programs, how do you approach it? Norvig: I think one of the most important things is being able to keep everything in your head at once. If you

Seibel: Speaking of things that aren’t taught as much, you’ve been both an academic and in industry; do you feel like academic computer science and industrial programming meet in the right place? Norvig: It’s a big question. I don’t think there’s a lot of waste in computer science curriculum. I think that it’s mostly very

Seibel: I’m surprised you think the master-programmer model is such a dumb idea. In your “Teach Yourself Programming in Ten Years” essay you make the point that programming is a skill that, like many skills, probably takes about a decade to really master. And lots of crafts hadmaster/journeymen/apprentice kind of hierarchies. So maybe nobody wants

Continue the Peter Norvig series. The first post was about: What Peter Norvig Learn about ‘Industrial Programming’? now it’s time to talk about the way of learning to work on a team during the time. Seibel: Do you think that learning to work on teams that way also enables you to actually work on bigger

Peter Norvig is known for his technical abilities, for his degree and for being the Director of Research at google. But, he also made a big contribution to the learning discussion about how to learn to program. His famous essay: Teach Yourself Programming in Ten Years. Blogged here: Peter Norvig Paper: Oh shinny! antidote is

Following the Joe Armstrong quotes, there is one about the print statements. Seibel: What are the techniques that you use there? Print statements? Armstrong: Print statements. The great gods of programming said, “Thou shalt put printf statements in your program at the point where you think it’s gone wrong, recompile, and run it.” Then there’s—I

Continuing the ideas that Joshua Bloch gave us, that has started on this post: Joshua Bloch and his tier list of book here we can see an interesting one: Seibel: Why do people get so religious about their computer languages? Bloch: I don’t know. But when you choose a language, you’re choosing more than a

Joshua Bloch a software engineer related, contributor and (in some way) evangelist of Java has been asking at the time Coders at Work was published about the books of every programmer should read. Seibel: Are there any books that every programmer should read? Bloch: An obvious one, which I have slightly mixed feelings about but

The creator of JavaScript, Brendan Eich was asked about the programming languages and the time Seibel: Do you feel at all that programming is a young person’s game? Eich: I think young people have enormous advantages, just physiological advantages to do with the brain. What they don’t have is the wisdom! You get crustier and