Take the 2-minute tour ×  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?   migration rejected from stackoverflow.com Nov 3 at
9:28   closed as primarily opinion-based by gnat, MichaelT,
GlenH7, Dan Pichelman, Kilian Foth Nov 3 at 9:28   Can we please
stop using the term code smells? It makes me gag in my mouth a
little every time I hear it. Thanks, yours truly. –  Joe
Philllips Nov 26 '08 at 15:42 Actually I can't say the term
appeals to me either, but sinc