Article Discussion: Thoughts on the Craft of Programming:Abstraction, Refactoring,etc

If you have any questions or comments on this article then please post them here.

This forum post relates to this article

Absolutely fantastic article.

How many times have we, as programmers, developers, etc... been forced work with the consequences of the lazy programming practices of previous developers (including ourselves)? This article should be the start of a mantra for serious developers to re-think the way they, and the team they work with, look at the code they themselves write.

We ALL have fallen prey to every single one of the unelegant solutions that the author exposes. Sometimes, it takes eating some humble pie to admit the code that we wrote, even a week before, wasn't the most elegant, or efficient. This article was a clear depiction of what to look out for when you're coding, testing, remediating, and of course, refactoring. Great job!

Agreed! Good code comes from good coding practices!

>a Java programmer would automatically write the loop in the Java idiom:

for (int i = 0; i < s.length(); i++)
<

Actually, I think a Java programmer would write it this way:

int strLen = s.length();
for (int i = 0; i < strLen; i++)

so as to avoid calling the length() function multiple times.

That's actually a good tip... I was taught to just keep the "length()" method call within the for loop...

I would re-phrase your sentence to say: "Actually, I think a _good_ Java programmer would write it this way"...