3 ms·
I have sites live that aren't even complete. Better than giving people a waiting list. > What if something goes wrong? What if its broken? What if there is a s
by git-pull 9y ago
I have sites live that aren't even complete. Better than giving people a waiting list.
> What if something goes wrong? What if its broken? What if there is a security issue?
Then, you'll fix it. They found bugs you wouldn't have noticed unless you put it out there.
It doesn't necessarily mean you'll lose users. Microsoft and Google have tons of security advisories. They patch, and go on building and marketing.
> What if no-one cares or uses it?
If you don't release, you risk a perilous prospect of being the product and service that's "stealth" and never ships. People are sick of those who always play it close to the vest, spin tall tales filled with marketing buzzwords, are the next big thing, but have nothing to show for it.
By you being able to show your project, and incorporate feedback on it, you demonstrate that you can execute things and be part of the club of people who ship, not just talk.
There's a psychological hump everyone needs to get over. It's about self-esteem and failing. You're worth publicizing your own creation and getting feedback, and still getting people to check back to see how you innovate and improve upon your feedback.