Simplify! - Introduction
Motivation and table of contents

When I look around, I see two evolutions that in combination worry me a lot:
Motivation and table of contents
When I look around, I see two evolutions that in combination worry me a lot:
Layers of systems never cleaned up (part 2)
In the previous post, I discussed several relevant drivers that lead to ever-increasing complexity of the IT landscape, creating layers over layers of technology over time that never get cleaned up. As the post would have become too long otherwise, I left out the mitigation options.
Layers of systems never cleaned up (part 1)
In the previous post, I discussed several drivers of accidental complexity on the implementation level and what we can do about it.
Accidental complexity at an architectural level (part 2)
This post is about mitigation techniques regarding accidental complexity in the architectural level.
Accidental complexity at an architectural level (part 1)
In the previous post, I discussed the technology explosion we could observe in the recent years, its drivers, how it often creates unneeded complexity, reinforcing drivers and what we can do about it.