[rmc00]

Very true. I recently inherited an application at work that has a dark corner where a past co-worker wrote a crappy, I-hope-nobody-sees-this-code prototype. While the code does produce correct results, it's very messy. Most of the people who really understood how it works have left over the years since it was built too. I've been trying to understand exactly how the application works, and it's way more effort than it should be.

The point is this: build your software right. At the very least, only take reasonable shortcuts, and make sure you come back around to fix your crappy design at some point. The longer it festers, the worse it will get.