What all the above is trying to say is that when changing some core piece of business logic that is central to how the whole system works it should be very easy to:

• See what it used to be.
• See what it is changing to and how.
• Have a record of these critical changes.

I am convinced that software engineering should continue to be the art of safely and intentionally transitioning code from one state to another state.

But the thing is - where they hype gets it right. So much code isn’t important. So much code can be regenerated blindly.