3 ms·
I feel like this post has some nuance or clever wordplay that I'm missing. So if that's the case, apologies for adding noise. But in the real world, the waterf
by llm_nerd 2y ago
I feel like this post has some nuance or clever wordplay that I'm missing. So if that's the case, apologies for adding noise.
But in the real world, the waterfall model was absolutely not a "strawman", but instead was literally how almost all software was built, up to even the turn of the century and beyond. Software projects were smaller in general, compiling was a major undertaken, you collaborated on projects by sending files around or, best case, working on a shared network directory. The pace of change of tooling and "libraries" was much slower and more predictable.
As we got source control, intellisense, massive knowledge bases, and then the rapid iteration of code sharing in the form of libraries and so on, things started changing because the model was too slow. But it was absolutely real and the norm.
- mixmastamyk 2y agoNot exactly. From first principles, it could only possibly work if the project was very well-known/trodden ground already. So of course mistakes were either fixed when discovered or the project failed. (Yes, some govt projects pretended to follow a strict process. What’s new?) But even Brooks’ original MMM (1975) encouraged iteration as a way to validate assumptions.