This is why it is important to consider what kind of software or software components are surviving the tests of time and using them as a guide for future softwa

This is why it is important to consider what kind of software or software components are surviving the tests of time and using them as a guide for future software. As a software dev my gut feeling is that this requires the polar opposite of move fast and break things — instead of going for the obvious solution it requires you to think a bit more how data flows (or ought to) flow through the organizations using the software.