A witty quip, but probably wrong. The author's conclusion was important:
> Launch your [site] before you core functionality is done. You’ll fix the bugs you don’t know you have.
Some places can't afford to do that - things where lives are at stake (medical, engineering, etc) or companies who don't get a chance at do-overs at all.
But for most small ventures, you're in for a much bigger risk of abandoning the project by delaying endlessly than you are of having a huge rush of potential users, not being able to serve them, being unable to fix that, and having a reputation for that stick.
And most people building medical devices, engineering, or rolling something out for a huge corporation with a lot of buzz know who they are. The post is good advice for the rest of everyone else.
There's an enormous difference between launching before a site is polished, and launching before the site is actually functional. You launch with a minimum viable product. If your car doesn't have wheels or an engine, it's not a viable product.
Show it to people early and often, get as much feedback as possible. Launch when it works.
> Launch your [site] before you core functionality is done. You’ll fix the bugs you don’t know you have.
Some places can't afford to do that - things where lives are at stake (medical, engineering, etc) or companies who don't get a chance at do-overs at all.
But for most small ventures, you're in for a much bigger risk of abandoning the project by delaying endlessly than you are of having a huge rush of potential users, not being able to serve them, being unable to fix that, and having a reputation for that stick.
And most people building medical devices, engineering, or rolling something out for a huge corporation with a lot of buzz know who they are. The post is good advice for the rest of everyone else.