Maintaining and reworking technical debt
Every aspect of creating an IDP up to now represents a technical debt. Idealists would tell you that if you’ve made smart decisions, there is no technical debt, but frankly, that’s not accurate. A once-thriving open source project can be shuttered with no notice or an unexpected CVE can appear. There will always be debt, regardless of best efforts. What’s critical for organizational health is the ability to manage the fallout from such events and maintain a reasonable pace for innovation.
Own your technical debt
Owning your architecture means owning the technical debt that it incurs. While this sounds like an abstract concept, it’s very easy to realize the breadth of impact when we start assessing the components of our architecture. Remember this important note from Chapter 2?
Important note
The environment you choose for your platform automatically prescribes some parts of your platform, whether you like...
