That's a rather lame quip. I still don't know what the tradeoff is. Dijkstra wasn't asked to do that, and just because the other guy did it once doesn't make his software methodology superior.

The point is that the other side of the tradeoff (of COURSE we would like things to be correct as they can be) is getting it done. I question that this is not somewhat obvious.