36 ms·
I would argue with waterfall model (naïve translation of engineering to software) being out of favor for decades now, almost nobody actually makes "blueprints"
by varjag 10y ago
I would argue with waterfall model (naïve translation of engineering to software) being out of favor for decades now, almost nobody actually makes "blueprints" for software. Agile, XP and TDD is basically "put something together and make sure it doesn't fall apart when we ship it".
Now what actually requires engineering is a whole another perspective. I'd argue most software development jobs are closer to "renovate the kitchen" than "calculate building wind load" type of work. Also remarkably in construction, the latter task turned out to be much easier to automate.
- js8 10y ago> most software development jobs are closer to "renovate the kitchen" And why people need different kitchens? Cannot the differences required be resolved by configuration, do they have to be resolved by programming? I argue that everybody having different kitchen is inefficient and wrong approach to software development. Waterfall was never in favor - IMHO programmers (or software engineers) always recognized that there software has no good analogue to reality, and there is nothing like a blueprint for software.
- varjag 10y agoThere are ISO standards for what is known as waterfall model, from block diagrams (the actual blueprint) to project flow. It was the only model in widespread use before time-sharing systems and then personal computing came to dominate the market. The Mythical Man-Month was written as an argument against established practice in the field then. > And why people need different kitchens? Cannot the differences required be resolved by configuration, do they have to be resolved by programming? Sure, if all your want is say IKEA kitchen with IKEA appliances. Some people have genuinely different needs.