The Elastic Leadership Book

 

 

        RSS Feed

Latest Entries

Saturday
May082010

Kevlin Henney – 3 things every programmer should know

During the ACCU 2010 conference in London, I got to get on audio, several of the interesting people who attended and spoke at the conference.

One of them was Kevlin Henney. I first got to see him speaking during NDC 2009 in Norway. He was fascinating in the way he approached sophisticated architecture topics, and his lively and funny way of making everything more understandable.

Kevlin is also the main character behind the book 97 things every developer should know and several other books.

In this 20 minute audio mp3, we start off with a simple question: what are the three things every programmer should know? (you can watch Kevlin on this years NDC in Norway as well. I highly recommend it! (he’s also on twitter)

Download the mp3 – 20 min.

« My team keeps breaking their promises. What can I do? | Main | Interview: Patrick Kua : Agile Coach »

Reader Comments (3)

Last time I checked the ACCU conference was in Oxford, not London, train between the two takes an hour. So by the standards we have here in England they are quite different places.

May 9, 2010 | Unregistered Commenterallan kelly

Interesting interview... I got lost a bit a the end and didn't get what was the thing #3....

May 11, 2010 | Unregistered CommenterDavid

For those who want the short version of the 20-minute MP3. The 3 main points are:
1) Intentional Practice -- writing code, TDD, etc. Just practice outside of your regular duty as a programmer so that you can master whatever it is you are trying to learn.
2) Read -- Everything. Programmer's Blogs, Open Source code, etc. Don't just copy-and-paste code. Understand what better programmers than you are doing. Don't ever stop learning.
3) Learn the Language's Culture -- This one was less apparent to me, but sort of made sense. The culture of each programming language typically has a sort of "best practices" that goes along with it. By learning the culture, you likely get to interact with other coders in the process. A potential for cross-pollination of ideas, if you will.

May 21, 2010 | Unregistered CommenterPretzel

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>