The way the author defined water fall makes it sound pretty good to me.

Put your hand up if you are ever programming with poor specs?

Put your hand up if you have a better idea of what really was wanted after the first cut?

And what I really dislike is those that try to design a Swiss Army knife from day one when they haven’t a clue. Jump immediately into over complexity.

▲

anilakar 2 days ago | parent [-]

Wasn't the whole waterfall model originally a caricature to higlight all the issues one will inevitably encounter if they eliminate feedback loops and go with a strictly sequential development paradigm?

	▲	LAC-Tech 2 days ago \| parent [-]
		Author here. Yes, that would be the first paper I linked to in the article, "Managing the Development of Large Software Systems" (Royce, 1970). The first diagram is the classic waterfall diagram, used there for illustrative purposes as an example of what not to do. Highly recommend it to people - it's short but a real breathe of fresh air. Mostly still applicable today.