There are always excuses and extenuating circumstances and heartfelt resolutions are made to change, but it seems that once a project has become large and complex and still hasn't shipped (or at least garnered outside interest and stakeholders), there's very little chance that it can turn around. The leading causes of perpetual shipping delay seem to be featureitis, perfectionism, and vanity, which usually come together, as a trio, and manifest into what is essentially the fear to release something small and targeted due to insecurity that it won't be well received and will shatter the grand vision. They are reality-avoidance strategies. And these problems become more and more dangerous as the project grows in size and scope, because there is more and more surface area for the featureitis to latch onto, and each new feature requires unanticipated time to make 'perfect', and exposes new unfulfilled use cases that lead to more features and so on, and no one's ever satisfied with the whole picture. It's horribly Sisyphean and demoralizing to toss one's creative energy into such a maelstrom.
In fact in improv, failure is an important introductory lesson. Without reducing fear of failure by actually failing, improvising would be impossible except for the bravest of souls.
One basic lesson goes like this: make up a pun about what the bartender said about 1,001 light bulbs when they went into the bar. In general, the results are terrible, but the class is told to erupt in applause and support for the improviser for having attempted a pun.
Good luck with the project!
That's what my old boss always said, he sold his company for a few millions :-)
But please use basic security.
Bcrypt, etc.
