de tomKronieken

I respect Martin Fowler. I really do. But blog entries like this one make me ask this question: "what the hell are you doing?" If you make a change to a program, is it really that important to call it "optimization" or "refactoring"? Things like this are generally the result of too much belly-staring: nobody gives a shit, but you think you're pondering the Most Important Question in Life. There are more useful things to think about.

Oh, I can think of one occasion when this might be important: you're manager has read a book about XP, and wants to be hip and implements XP, but asks you to categorize the work in your timesheets between "optimization" and "refactoring". In this case, try to talk some sense into the guy. Or run, run like you've never run before.