3 ms·
Isn't this just waterfall? Prep the shit outa everything requirement and design wise, then make it in sequential fashion?
by langsoul-com 5y ago
Isn't this just waterfall?
Prep the shit outa everything requirement and design wise, then make it in sequential fashion?
- TuringTest 5y ago> Isn't this just waterfall? I don't think so, because the article is talking about prepping up the tools and infrastructure needed for the project, not the requirements and design needed for the program's business logic.
- mkl95 5y agoIt is also agile done wrong by companies that don't understand how iteration works.
- sparcpile 5y agoThe author re-worded iterative development where you start with a skeleton and slowly build out. Their example was to build out a simple build pipeline with stub projects that are replaced over time. The Practice of Programming(Kernighan and Pike 1999) https://www.cs.princeton.edu/~bwk/tpop.webpage/ https://www.cs.princeton.edu/~bwk/tpop.webpage/ goes into much better details of the iterative development that is actually being done by the author. If you know the overall design of your program, you build out the skeleton with everything stubbed out. As you iterate through development, those stubs are fleshed out into fully working components. The analogy of mise-in-enplace works if you have a ready for reusable components (COTS, FOSS, or personal) that you quickly pull off the shelf and combine into the larger product. Mise means having everything ready to go; you have your set of reusable components and subsystems that you can quickly pull together to make a new product.