We have come a long way and had a lot of improvements over the years, but we still struggle with the ability to simplify things faster than we create complexity. It isnโt enough that each new wave of Really Important Bitsโข comes with its own issues and layers and complexity; we also havenโt been cleaning up our previous Really Important Bitsโข projects. We havenโt cleaned up the successful ones and we havenโt cleaned up the failures.
It is time to start. Honestly, we are looking at an extended stretch of ‘Do More With Less,’ and we need to get our houses in order. Want to do more with less? Start by standardizing. Yes, that one project that used Really Important Bitsโข (or its companion product Really Cool Techโข) was neat and all, but keeping a technology and its layers and pieces laying around for a single project is not great management. In fact, it isnโt management at all; it is letting things happen. Iโd call it chaos, but then weโd have to have a whole conversation about Dungeons & Dragons and, frankly, it is happening in the forum of the overall enterprise architecture so itโs not actually chaos, it is simply excess technical debt.
DevOps was never meant to be a destination, but on this cross-country road trip, our IT car will get filled with garbage if we donโt take the time to clear out the Really Important Thingsโข of last year or the last management team or the latest merger. We cannot continue to layer more on without relieving pressure somewhere. AI has the potential to offer some pressure relief in some areas, but we were already behind, so for a variety of reasons, it isnโt the silver bullet we need. Those reasons are simpleโit is less secure to leave 50 different ways to do the same thing laying around. AI is resolving some problems and freeing up time, but youโre still wasting time and money on redundant or unused Really Important Thingsโข.
Some things simply cannot be cleaned up without a massive investment. Thatโs fineโI hope after years of using DevOps methodologies you have them on a list of things that youโd like to upgrade/replace, but it just isnโt feasible to do so. Focus on the things that you can simplify. The famous low-hanging fruits are fine, just like simplifying things in the early days of DevOps meant that each piece of low-hanging fruit freed up more time to focus on other issues, the same is true now that the low-hanging fruit is generated from DevOps. Or DevOops, in some cases.
How did I get here, you ask? I was writing a simple overview of Git, CI/CD, DevOps, DevSecOps, GitOps, etc., etc. for a newer technologist, and realized that in between those important parts are a whole lot of tools and technologies we thought were important, but which are no longer terribly useful or necessary. I did her the favor of not including the by-the-wayside technology spaces and product markets. I removed the complexity, you could say.
And keep rocking it. No matter how far along you are in your IT career, you can look back at all of the things you have learned. Apply that learning to simplifying and improving. Reduce overhead by reducing redundancy and look forward to the next Really Important Thingโข youโll get to learn about. Keep improvingโboth your knowledge and the environment. And weโll keep cheering you on.





