#Question 3# ##Problem overview##
On May 18, 2006 Jeff Atwood from http://www.codinghorror.com/blog/ said:
I'm often asked why the book Refactoring isn't included in my recommended developer reading list. Although I own the book, and I've read it twice, I felt it was too prescriptive-- if you see (x), then you must do (y). Any programmer worth his or her salt should already be refactoring aggressively. It's so essential to the craft that if you have to read a book to understand how it works, you probably shouldn't be a programmer in the first place.
There's nothing wrong with codifying refactoring guidelines in a book. But the most important guideline is to watch for warning signs in your own code-- so called "code smells". ##Now, this is what you have do to##
-
What is a Code Smell?.
- Show some brain, share with us your ideas, avoid copying/pasting unless you have to.
-
Give us a Long Method code smell example.
- Again avoid copying/pasting, show some brain, be original.
##How will we pick a winner?##
- +1 point by answering both questions
- +1 point by correctness
- +1 point for the most original code example answer
- Wins the first one scoring 3 point in this example
##What will you win?##
- 1 Caguama or 1 Not too expensive lunch :)
We should've asked for a way to fix that code smell besides just asking for an example.