Oh, your code structure isn't pefect?

I think that perfectionism is a hard thing to overcome for anyone that has a lot of passion in their work, both for the final product and the work that lead up to it. Writers and painters are some of the hardest critics of their own work. Why should this be any different from programmers?

When I am blazing new territory like prototyping an idea I write my code in a style that will allow me to see a percent of the final product. If I notice things that should or come be upgraded or simplified I write a comment near the section of code and continue on with my current task.

I think that if I were to stop and "fix" I would lag behind in production schedules and I may miss a key element in the first run through of an idea.

As for you screenshots, it is always nice to have some thing to show off and I like the familiar style. 

I have found myself in this same boat all too many times.  What helped me to overcome it was money.  Customers don't tend to care if it's perfect they just want it done, and when you finish it they pay you.  From that I have learned to have an "acceptable" standard and a "personal" standard.  Where the acceptable is does it work?  Is the customer happy?  Are there bugs?  All in all there's few times that customers pay to maintain their works, more often they simply contract a fresh new build of the entire project ground up with new features and targets and what not.  As such, as long as the structure of the code remains viable throughout the coding process the first time you can be lax on return coding a bit.  That's not to promote poor coding practices but a way to let yourself actually be productive instead of a perfectionist.  When it all comes down to it my goal is to make stuff, I'm not big on the fight with the computer to get there so productivity over pretty in my book.