3 ms·
The Apollo space program is a good example: It probably wouldn't have worked very well if they "launched early and launched often" Actually, they did iterate a
by stcredzero 18y ago
The Apollo space program is a good example: It probably wouldn't have worked very well if they "launched early and launched often"
Actually, they did iterate and take small steps. They started with unmanned suborbital launches, went to manned suborbital launch, then manned orbital launch. And that was just the Mercury program. Next, they went to launching 2-man capsules, spacewalks, and on-orbit rendevous in the Gemini program.
It would also require too many suicidal astronauts ;-)
You have an implicit assumption that rapid iteration means poor quality control. It doesn't have to. I've met people with formal methods tools who say they are capable of rapid iteration. (And yes, these are marketed to the aerospace industry.) Also, if you manage a project from the start with automated testing, low defect rate is very doable.
Aeroplane manufacturing is the same thing: Either it works or it doesn't.
Uh, no. There are lots of examples of planes that kinda worked. This is why test pilots have to be so good. You have to be very good to get a kinda-working plane back on the ground in one piece, or sometimes even to just manage to eject from it.
Your point may be good, but it suffers from drawing from examples which you don't have very good knowledge about.
- mixmax 18y agoSorry about the examples :-) And reading yours and the other comments in the thread, I'm not so sure I'm right. Oh well, you learn every day...
- Tamerlin 18y ago"You have an implicit assumption that rapid iteration means poor quality control. It doesn't have to." I would actually go a step farther and assert that strong quality control facilitates rapid iteration. My 15 years of experience in software bears this out -- the (extremely rare) projects with quality control were far smoother than the ones without. In ones without solid QA, the software become so convoluted and messy that rapid iterations became entirely infeasible. There was no way to change the software without re-writing large chunks of it, or putting in a large collection of hacks that broke as much as they fixed.