Episode 20: Clean Code

Listen to the podcast

On episode 20, we discuss clean code. A few of the primary techniques for
achieving human-readable code are tabled, including using descriptive, clear
names, not mixing levels of abstraction, and code that does only one thing
without side effects. An interesting discussion arises on how clean code
relates to collaborative code development. Namely, we explore how code improves
by using consistent project style conventions and remaining humble in
the face of constructive criticism. It is also observed that a well-designed and
easily tested structure is a natural consequence of clean code. Ultimately,
this results in low-cost, easily-maintainable programs that work.

On today’s show our crew of hosts includes:

• Jean-Christophe Fillion-Robin (special guest)
• Luis Ibanez
• Matthew McCormick (moderator)
• Wes Turner (special guest)
• Geraldine Van der Auwera

This week Jean-Christophe Fillion-Robin joins us from Kitware.
He is an R&D Engineer at Kitware working in the
Medical Imaging, Data Management and Software process areas. He is one of the
lead developers involved in the development of Slicer 4.0, a platform for
medical image segmentation, registration, visualization, and analysis.

Wes Turner also joins us from Kitware. He is a
Technical Leader at Kitware working in the Medical Imaging and Bioinformatics
areas. He has been developing software since the ’80s first as a defense
contractor, then as a graduate student, and now as an active participant in Open
Source communities at Kitware. Watching the ascendancy and decline of various
Software Engineering technologies has given him a great appreciation for
well-written, understandable code.

We again have Luis Ibanez, who can now can be considered
regular panelist. Indeed, he was the easiest panelist to edit, likely because
his public speaking skills were polished while recently teaching his
course on open source software practices.

Intro/Outro Music: ‘Dans un petit verre d’eau’ – David Löhstana

Show Links:

1. Clean Code by Robert Martin (http://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
2. How to write un-maintainable code. (http://thc.org/root/phun/unmaintain.html)

Posted in: Episode