Best way to relate code smells to a non technical audience?

Posted by Ed Guiness on Programmers See other posts from Programmers or by Ed Guiness
Published on 2008-11-26T14:23:04Z Indexed on 2011/03/19 8:18 UTC
Read the original article Hit count: 386

I have been asked to present examples of code issues that were found during a code review.

My audience is mostly non-technical and I want to try to express the issues in such a way that I convey the importance of "good code" versus "bad code".

But as I review my presentation it seems to me I've glossed over the reasons why it is important to write good code. I've mentioned a number of reasons including ease of maintenance, increased likelihood of bugs, but with my "non tech" hat on they seem unconvincing.

What is your advice for helping a non-technical audience relate to the importance of good code?

© Programmers or respective owner

Related posts about code-reviews

Related posts about communication