No Other Way to Find Out
Coding Horror: Version 1 Sucks, But Ship It Anyway:
Reasons for failure on a… project are legion.
At the end of the development cycle, you end up with [a system] that is a pale shadow of the shining, glorious monument to… engineering that you envisioned when you started.
It’s tempting, at this point, to throw in the towel — to add more time to the schedule so you can get it right before shipping… Because, after all, real developers ship.
I’m here to tell you that this is a mistake.
Yes, you did a ton of things wrong on this project. But you also did a ton of things wrong that you don’t know about yet. And there’s no other way to find out what those things are until you ship this version and get it in front of users and customers.
Labels: leadership, links
Delicious
Facebook
posted by Mark (the Brush Valley Brewer) @ 2/02/2010 08:00:00 AM 2 CommentsLinks to this post
![Subscribe to Posts [Atom]](http://www.personal.psu.edu/mhl100/img/feed-icon-28x28.png){kind=icon}
2 Comments:
In Guy Kawasaki's Rules for Revolutionaries he calls this the "Don't Worry, Be Crappy" rule. The corollary of course is, "Better, Better be Coming." Get it out there, but fix it fast.
Spot on.
You know I'm not suggesting we just throw junk out there.
Here is what I — we — are saying:
Some people would rather do nothing for fear of their something being wrong.
Get over that!
Of course it will be wrong.
The sooner you find out how it is wrong, the sooner you can fix it!
Post a Comment
Links to this post:
Create a Link
<< Home