The title is poking fun at the ever increasing complexity of acronyms in the space of writing and deploying code in this day and age.  In all seriousness, it's very much a good thing that these combinations are starting to pop up in the tech world and especially in industry.  For too long SOX and ITGC specifically cast a shadow over IT in non-tech sectors that snuffed out any hope for innovation, as the focus from senior leadership that any changes were not worth the potential regulatory risks.  The processes and tools involved in the DevOps and DataOps methodologies have made it possible to now to placate those less risk-averse whilst still bringing much needed change and updates to processes that are in some cases old enough to draw social security.

I'm not making this post to explain what DevOps or DataOps or SecOps are, but rather to pontificate a bit on their specific need within industry and smaller business.

In larger companies and those with a technology focus, development and 'operations' are very easy to delineate; but as we get smaller or leaner, the lines begin to blur between those responsible for developing solutions and those who implement them.  This may sound great to a leadership team who wants to minimize G&A - but the issue quickly becomes….why the hell would anyone stay doing development work when they can jet for a tech company, not only reducing the stress in their lives but also increasing their compensation as well.

These processes and tools that this plethora of acronyms bring can help solve both sides of this issue (well not the G&A one- sorry boys…you're going to have to pay your people what they're worth).