This kind of absolutism only works in the lab and the journal. The real world of software engineering is enormously varied and each project faces a different s

This kind of absolutism only works in the lab and the journal. The real world of software engineering is enormously varied and each project faces a different set of legitimate constraints and objectives. It's more valuable to discuss how and when to use "assertions, throws, and try-catch[es]" than to pretend that they're universally superceded by some other construct.