Chapter 1. The Software Industrial Revolution Has Arrived
We asked developers from a variety of organizations and industries a simple question: how long will your application continue to work if you are not allowed to touch its code? What we found was that the more modern the application, the more quickly it would be in jeopardy.
The reason? Software used to be built. Today, it is increasingly assembled from off-the-shelf components in the form of open source software (OSS) and third-party APIs. Unlike similar components we might use to build a physical product, software components evolve independently at their own rate. Enterprise organizations don’t control that evolution. And what happens when you fail to keep up? The software becomes less secure, gets harder to maintain, and eventually stops working.
As an industry, we’ve accepted that keeping assembled software components up to date is considered technical debt, a term originally used to describe self-imposed coding issues that become debt to the organization, compounding daily. One survey suggests that 30% of daily engineering time is spent on technical debt, and we can see this increasing year over year as codebases continue to grow. While technical debt amassed from third-party code is something beyond a development team’s control, they are often blamed for accruing this debt and not keeping up with the evolving third-party software. This can be hugely demoralizing and demotivating to development teams. We should not have ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access