Mar 13 2008 at 9:08am
When you can’t just start over, revisited
A few months ago I wrote about the frustrations involved with working with someone else’s outdated code. 37 Signals has a similar post today:
Here’s something I don’t say often: Suck It Up. If you work on more than a few projects, they can’t all smell like today’s fresh linens. It doesn’t mean you’re a bad programmer. It simply means that you’re prioritizing.
And I think that’s something that goes for any type of project. There’s rarely enough time or money to make everything perfect, whether it be a programming project at work or the paint job in the dining room. You have to find the point of balance and decide when it’s worth it to put in the extra time and/or money. Does this really matter in the big picture?
This can be a difficult thing to get over and, as a perfectionist, I know I often spend time on things that don’t matter that much.


