I’ve been writing software my entire academic and professional career. When writing software in college, software is done when it compiles without errors. (Oh, and when it meets the assignment description.) Out in the business world, software is done when it meets the requirements and the testing person/department rubber stamps it (Not really, but close enough).

What about in a one man micro-ISV? I want to get the first release out as soon as possible, so I’m not packing it with hundreds of features; just the ones that are core to its operation. Extra and whiz-bang features can come in future releases. So I have simple requirements and verified that all of them are met. My experience tells me that it’s ready to go. But something is holding me back from releasing it. Since this is my own personal creation, I want to make sure it is as good as gold. I’ve been testing it to death, making doubly sure it’s solid. Because this is my reputation at stake here. And although probably untrue, I feel that this first release will make or break my dreams of being free from 9 to 5. My feelings and anxieties are probably normal, but for those that have released software successfully, what advice do you have for dealing with this?

(In addition to the software I’m actually selling, I’m also writing software to set up a fully automated sales process integrated with PayPal, and an affiliate program where sales referrals earn you 15% of the sales price, and you get 5% of sales referred by affiliates that you recruit to sign up. There should be more details by the end of this month! But I’m glad to report that I’m in the home stretch now, testing my software and making sure the sales and distribution infrastructure is in place.)