Feature Envy vs. Long Parameter List

Why is there always something wrong with code? I can’t make one improvement without sacrificing something else.

I’m not talking about trades between coupling and performance, understandability and speed. Tackle one code smell and you’ve just introduced another, a sick game of Whack-A-Mole.

Parallel Object Model: stink or stench?

Yes, I am here, ladies and gentlemen. I am The Last Man Standing against dishonesty and deceit. I am what sticks in your craw. I am the fired basketball coach who won a game 100-0.

Worry not about those who punish the great, those who chide righteousness, those who are threatened by the truth. God will deal with them.

Don’t doubt me.

I will not apologize for the truth. I will not back down. I will not grant them the power to ruin my day so much as to cause me to abdicate my duties here. If that happens, then the terrorists win.

Let’s roll.

You stink

Greetings to you truth-seekers, refactorites, and code monkeys all across the digital plane. I am here, El MoffDo, your highly-trained web publication specialist, on the Wednesday edition of I Built His Cage, ready for another post of Programming Excellence.

Stu Smith of Hackification.com listed his 10 worst code smells:

1. Long Functions
2. Commented-Out Code
3. Copy-Pasted Code
4. Handled-but-Really-Unhandled Exceptions
5. Large Numbers of Parameters
6. Non-Obvious Names
7. Deep Nesting
8. Beacon Comments
9. Narcolepsy …by which I mean inappropriate sleep() ing.
10. Helper Classes