Ah yes, you can always fix it later. Yup, I believe that. (Did you sense the sarcasm?)

Learning design patterns will help you identify when to change things. But you don't always recognize the issues until you have to add functionality.

>Since that's almost never done, we have the "there's never time enough to do it right, but there's always time to do it twice".
>
>IMO, the "when you get the code working" is a bit hard to measure. When is the right time to do that. Perhaps it's when you look at it and feel like saying (or do say) "which moron wrote this?". By then you know enough to do it right this time, and still haven't forgotten why you did it that way the first time.