According the point of view about the way of doing software, that we can resume that try to develop the solver problem element. Another interesting topic where we can focus is the way to using testing to drive design. Something that now is knowing as: Test Driven Design Seibel: What about the idea of using

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

Joe Armstrong has talked a lot about the topic or being a good programmer as we can see in the previous posts: What Joe Armstrong did to be a better programmer?, Joe Armstrong and the Print Statements and Joe Armstrong and the importance of the writing skills. Now we are point about a side question related

Besides the opinion of Joe Armstrong about What Joe Armstrong did to be a better programmer? and Joe Armstrong and the Print Statements he also has an interesting opinion about other skills not related to programming but which are such a wonderful tool to have, a very strong nice to have we could say. Seibel: