Hacker News Reader

I don't think that Agile is always about being more risky. Sure, Waterfall is a safe way to go in most projects, but what about the possible losses in costs and effort that may come from it? However, I do get your point regarding safety for the client itself, that don't want to risk shipping an "unfinished" product.

View on HN

It is inherently risky in that it encourages shipping first and fixing stuff later. This is the opposite of what you do with something like someone's bank account. (Yes, ETH Solidity developers, I'm talking to you.)

I absolutely love the agile process and I'm a big believer in pair programming, which was part of the original doctrine but is hardly mentioned today. That being said, no one is smart as all of us and there are inevitably things in your code which you (two) as developers won't immediately discern. Waterfall, though protracted and boring, is crucial for identifying and fixing those problems before they ship.

Reply on news.ycombinator.com