Duct Tape Coder

The way I look at it is this, if it's worth spending 5 minutes on, it's worth spending an hour on. The reason is simple, if the code requires maintenance anyway, there's a good chance it's going to require maintenance in the future. If I only spend 5 minutes on it, the fix is probably going to be a duct tape fix. If I spend an hour on it, I can be sure to come up with something that is maintainable/sustainable. Maybe I'll even spend some of that leftover time during that hour to do some other refactoring/write tests.
I feel it's a good rule of thumb, for new/experienced coders alike.

Completely agree. in this day and age it's all about speed and cost cutting. However from a developers point of view, it's much better to take some time to fix it the right way the first time, so you don't keep coming back to the same issues over and over again.