News for hackers. Stuff that matters.
Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by bitwize on Saturday November 14, 2026 @11:06AM (#50498117)
"Waterfall" is a pastiche of mature development practices used by Agilists to sell their programmer-centric snake oil. It's basically a phased development process kinda like PRIDE, but it explicitly doesn't incorporate feedback between the phases. PRIDE explicitly allows, for instance, new requirements discovered during the design phase to feed back into the analysis phase. But it is explicitly based on the idea that "A system is a product that can be designed and manufactured, just like any other product." And that the exact same management principles from the manufacturing and construction industries apply to information systems development. It is always a phased process that starts with requirements—identifying what the needs are, followed by design—producing a blueprint of how those needs will be met. This is how bridges, buildings, cars, and consumer goods are built; why not systems? Milt Bryce used to say, "If this country built bridges the way it builds systems, we'd be a nation run by ferryboats."

A counter to this is "requirements change quickly, therefore the system needs to change quickly too." But the actual case is: most organizations don't really know how to do systems analysis. So this results in one of two scenarios: either the organization wastes a lot of time and money in the analysis phase struggling to do what they cannot, or they punt on requirements analysis altogether and wait for requirements to surface at implementation time. This is called "Agile" today, but was described by Milt in 1983: "do a superficial feasibility study, do some quick and dirty systems design, spend a lot of time in programming, install prematurely so you can irritate the users sooner, and then keep working on it till you get something accomplished."

PRIDE is like a textbook on how to build a system, from requirements analysis through design, implementation, and maintenance. It was the first methodology for doing so, and it transformed information systems from arcane art into a proven, repeatable science. It should be the industry standard, but is now at risk of being forgotten, largely due to programmers holding the industry hostage.

AI is taking programmers out of the equation. PRIDE is relevant again.

Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by rpdillon on Saturday November 14, 2026 @11:33AM (#50498335)
Ah, so more like spiral development. I don't think we know what development methodologies will be relevant; things are changing too quickly. Your comments come off as a bit over-confident, given the level of uncertainty about this topic, but I appreciate you mentioning the methodology, since I suspect we'll draw on those lessons as we formulate the new best practices.
Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by teyc on Saturday November 14, 2026 @05:53PM (#50501860)
[delayed]