[mtkd]

If you're using it for a start-up - it's much more important to deliver usable software than quality code - you can always go back and clean up the code - but if you don't get traction it's all over.

Also - consider buying code reviews from developers you respect - even a couple of hours a week can make significant difference to your quality.

[fatalerrorx3]

I'm currently working on a startup and like the OP I was questioning how good of a programmer I am. I'm self taught and have been programming since I was in middle school computer club more than 8 years ago.

Working on this startup project has taught me that in the beginning it's all about delivering a product that works that users want. When requirements are constantly in flux and you're working hard and fast to develop a fully functional prototype there's little time for code refactoring to make it "perfect" because the longer it takes to launch the larger the possibility that someone beats you to it. As long as the code does what it's supposed to do and is not loaded with bugs and isn't terribly slow I say to just go with it.

Requirements are always changing in startup land and a good programmer adapts to make those changes and is focused on producing a workable prototype before their competition does

[saiko-chriskun]

+1 on the mentorship note. _Incredibly_ useful. Not only for yourself but can also be a great exercise for the teacher.

http://pith.org/notes/2011/08/29/programmers-feeling-uninspi...