» ‘Move fast and break things’ is not a tenable paradigm for this industry today — if it ever was. In the light of our experience, with the outcomes of an industry that became fixated on pumping out minimally viable products, it’s a paradigm that heads towards what we could conventionally label as criminal negligence.«

»Every time you decide to solve a problem with code, you are committing part of your future capacity to maintaining and operating that code.«

My takeaway from these stories is this: Once you’ve learned enough that there’s a certain distance between the current version of your product and the best version of that product you can imagine, then the right approach is not to replace your software with a new version, but to build something new next to it — without throwing away what you have.

For decades, discussion of software reuse was far more common than actual software reuse. Today, the situation is reversed: developers reuse software written by others every day, in the form of software dependencies, and the situation goes mostly unexamined.