Reading this article has given me a profound realization: As a software user, I don't want the products I use to ship new features at "three, five, or ten times what they shipped a year ago," at the expense of "probabilistic" stability and reliability.

I want software that works.

Yet the economics of the software industry, and perhaps the economy as a whole, seem to inexorably push toward the former.

> We are rapidly moving from deterministic engineering to probabilistic engineering, and our tools, our training, and our organizational instincts are still built for the old paradigm.

There's some bad news: it's never been a non-probablistic engineering.

A key word is Failt-tolerance.

The engineering has never been fully deterministic. Same as running the systems.

So nothing's changed in this area.