If you want to talk about security holes, yes there is time to fix them later.
When you talk sloppy code, that is another story. One developer writes a program and uses a bad design and writes generally sloppy code. The next developer comes along and makes changes or adds functionality but is locked into using the original bad design. The developer after that is then locked into the same cycle, being forced to use bad code and bad design.
I always cringe when I am asked to move onto a project I didn't help write. Too often I open up the code files to take a look and I just want to cry.
* Bad design.
* No organization to the file so you can't find the method you are looking for without scanning through 5000 lines of code.
* No proper formatting to the code.
* No comments.
* No documentation
It may sound like nitpicking but simple organization of your code files and a comment here or there can make a WORLD of difference.
Keep Up with TechRepublic