With more and more organizations focusing on DevOps, it’s not surprising to see the number of toolchains — and the complexity of those toolchains — multiply. Afterall, automated testing for function, security, and deliverability is at the core of improving a team’s DevOps.
But, at what point are more tools and toolchains creating more distracting work for your team than they save? Is the complexity of these automated tools actually leading to a better development lifecycle, product, or service? Of course, there’s no simple answer to what the right number of toolchains or tools is, given the complicated and diverse circumstances different teams of developers face.
