(You have 28 days or so left, which is the original schedule for BCC plus twenty days.)
One thing you mention though resonates. You mention perfection. What is it they say? Perfect is the enemy of the good? I really dislike the work of the dilettante or amateur, my ideals are set pretty high and I see myself failing to meet my own exacting standards and this cripples me productively. Also I am a very indecisive person, plagued with doubt. This is great in that I make up my own mind about a lot of things and I don't fall prey to herd-think but it again is a bit of a productivity killer as I flit from technology to technology and methodology to methodology. For instance I've gone from DOS/Windows to Linux fanboy to Mac owner and from C and C++ to the LAMP stack to Ruby on Rails and from nothing to SVN to Git. It's exciting but tiring and their isn't a project out there that I can call my own and there's a directory full of half-baked ideas and scraps of code in ~/Code
It's surprising how often the extra bits you were worried about turn out to not actually occur, once you've learnt more from the initial version, you've understood it better and therefore designed a better approach.
The first version is to understand the problem. The next version (a rewrite) is to understand the solution. Call them "exploratory drafts" if you like.
This question comes up in different forms time and time again and the answers are almost always the same: Just do it. The only thing stopping you doing it is you so stop procrastinating and get on with it or just admit you're actually not that bothered / committed / whatever.
Also, smarts don't matter. You can be the smartest person in the world, but until you do it. It doesn't matter, because you're just like the kid who hasn't read it all. Stop being a theorist and start being the guy in the arena[1].
Love the idea of sharing and aiming for this target with others, bringing in accountability. Let me know how I can get in touch.