Kevlin Henney, editor/author of 97 Things Every Programmer Should Know, discusses the book and the programming process. He talks about how he compiled the essays for the book and lists some of the items he found most surprising and thought provoking. He also assesses the issues related to programmer training, including some of the things not taught in school.
Things Every Programmer Should Know
Tagged with software programming code kevlin henney interview podcast itconversations
Also huffduffed as…
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
-
Things Every Programmer Should Know
Possibly related…
-
Things Every Programmer Should Know
Kevlin Henney, editor/author of 97 Things Every Programmer Should Know, discusses the book and the programming process. He talks about how he compiled the essays for the book and lists some of the items he found most surprising and thought provoking. He also assesses the issues related to programmer training, including some of the things not taught in school.
Tagged with programming
-
Devnology Podcast 011 - Interview with David Anderson
Devnology heeft als doel de community van software ontwikkelaars in Nederland te voorzien in mogelijkheden om vakkennis en ervaring op te doen en uit te wisselen. Ze wil een brugfunctie vervullen tussen de theorie en praktijk van software ontwikkeling.
http://devnology.nl/nl/podcast/10-content/138-devnology-podcast-011-interview-with-david-anderson
-
Deep Fried Bytes Episode 35: Why Comments Are Evil and Pair Programming With Corey Haines
In this episode Keith and Woody sit down with friend and traveling developer Corey Haines. Here’s a question, how many times have you written comments in your code? Probably a lot! In this show Corey gives some valid reasons why developers shouldn’t have comments in their code (with a few exceptions). The guys also discuss pair programming, what it is, how it is done, and the benefits of doing it.
Tagged with podcast programming
