2 ms·
No, that's only half of why waterfall is often considered bad. The other half is because of the unpredictabilities in building software period -- internal rath
by crazygringo 3y ago
No, that's only half of why waterfall is often considered bad.
The other half is because of the unpredictabilities in building software period -- internal rather than external. You can build out one component fully and another component fully and then finally test them together at the end and discover there's a horrific race condition that requires rebuilding both from scratch to fix.
That's why a more iterative process is considered best practice today, to find showstopper bugs earlier rather than later, particularly to catch and address architectural issues sooner rather than later.
(But also, like I said, rewrites are rarely trying to produce a 1:1 copy in the real world. The whole point is usually to fix a bunch of problems with the previous system along the way, not to continue to reproduce the unwanted behavior. I'm not saying there are never perfect 1:1 rewrites that intend to reproduce all the bugs and warts and all, but it's rare.)