Suppose you have code that says, "if object can't send email, send a fax". You end up writing an alerter-management object, then. I suppose you could keep going, but this would just create turtles all the way down until your program was nothing but objects and messages, just to avoid "scary" predicates before OO hype made this un-PC. If you want 1000 lines of code when 100 will do, be my guest.
Re: Re: Re: Re: Short Refactoring Tip: let the object do it for you