Re: Marketurds vs Reality
In my experience, most modern software seems to fail miserably when it invariably does due to having been written to implement more or less only the shortest and most complication-free path between A and B, invariably keeling over as soon as (more than) one unforeseen factor takes it out of whack. And that is exactly why agile is unfit for purpose with anything that must work reliably: because the whole idea of fully specified requirements is that they're the only way to consider the implications on everything on everything.
Now, this is not to say that non-agile guarantees that those implications are fully and correctly considered; it's not even to say that agile couldn't, in theory, re-consider every single relevant interaction on-th-fly. Rather it is to say that it is not possible for humans using agile to do that in practice, ever, full stop.
It's hard enough even for excellent programmers to hold the entirety of the context of a problem in their mind all at once even when they go brick by brick starting from foundations - sometimes completely impossible already with large enough systems. But trying to do the same thing based just on diffs makes it flat out impossible for anyone, all of the time.
Biting the hand that feeds IT
