Mon, 28 Aug 2006
Two claims about clean code
Agile depends critically on programmers keeping the code
clean. Lots of us know important steps in making code cleaner:
rename methods and classes as their purpose changes, be wary
if statements, check if methods
are composed, move methods that
envy, and the like.
I make two claims.
A lot of the craft of being a good programmer is how you
sequence those individual steps, how you make them work
Standards of cleanliness ought to be situational.
consider an application in an
extremely fluid domain, one where there's a considerable
business advantage to having a code base that's ridiculously
flexible, one whose capabilities suggest new
features. Contrast it to a
app. The first ought to be much more aggressive about
naming, I bet, and I wouldn't be surprised to see the
programmers favoring embedded domain-specific languages.
(As someone once said,
"All large systems eventually end up with a Lisp implementation
I wonder how I could learn more about that? The best way would be to
work with other people on several disparate systems for a long
time—which is not in the cards.
## Posted at 11:17 in category /agile