Apologies, but this is overly simplistic. We manage this type of change all the time with versioning and other standard engineering practices.

Adding to the model doesn't *require* API changes, unless the new attributes are required and reasonable default values cannot be established.

When (not if) breaking changes are necessary, we deprecate, notify, version, etc.

I applaud the author's intent which is to get our industry to *think* about what we're doing and why we're doing it, rather than to simply continue because it's the way things have "always" been done.