Re:The Anti-If Campaign
by stcredzero on Thursday June 25, 2009 @11:42AM
(#673840)
And don't forget, lots of those 15 minute intervals can add up to serious money. ("Stovepipe" systems.) You can also set up an opportunity to bill for coming later in and "fixing" a seemingly intractable big mess.
[ Parent
| on HN ]
"Oh, I see the problem right here, Mr. Client. Your previous consultant used 'if' statements. Here, let me replace that function with 80 new class files. You'll be much more agile!"
Re:The Anti-If Campaign
by stcredzero on Thursday June 25, 2009 @12:13PM
(#673911)
I find that the opposite is true: replacing lots of runtime type identification with polymorphism results in placing repeated code in just one place. Don't Repeat Yourself is more agile. Even better: wait until at least the 3rd repetition before refactoring. (But don't wait too long.) This cuts down a lot of unnecessary coding, and leaves the programmer some leeway for good judgment.
Do not attribute to malice what can be equally well explained by stupidity.
Re:The Anti-If Campaign
by stcredzero on Thursday June 25, 2009 @12:14PM
(#673913)
Malice has a better chance of sustained profitability.
EDIT: This is a clue to bad intent. "Follow the money!"
Re:The Anti-If Campaign
by stavrianos on Thursday June 25, 2009 @12:28PM
(#673943)
and yet, the world over, people are still both basically decent and basically stupid.
Edit: correlation?