Working code is way better than broken code. And there's the aphorism of "If you're not embarrassed by your initial release, you're launching too late." I say release now; if nothing else, it should drive you to improve what you've got.
Agreed. Some is better than none, and fugly code is better than no code. As long as you have a clear mention that you're working to improve the code's quality, most (competent) people should respect that.
Comments
Working code is way better than broken code. And there's the aphorism of "If you're not embarrassed by your initial release, you're launching too late." I say release now; if nothing else, it should drive you to improve what you've got.
Agreed. Some is better than none, and fugly code is better than no code. As long as you have a clear mention that you're working to improve the code's quality, most (competent) people should respect that.
Thanks for the feedback and the push, guys - I'm going to go for it! (and have already started taking the next steps to do so)