<div class="hs-featured-image-wrapper">
<a href="http://blog.quali.com/blog/reinventing-the-wheels-in-devops-doesnt-scale.-platform-ops-does" title="" class="hs-featured-image-link"> <img src="https://blog.quali.com/hubfs/6point6%20blog-Jul-14-2020-07-41-33-37-PM.png" alt="Reinventing the Wheels in DevOps Doesn't Scale. Platform Ops Does." class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"> </a>
</div>
<p style="padding-left: 40px;"><span>The topic of scaling DevOps is far from new. As many of us painfully realize, it’s difficult to go beyond the little science experiment (an experiment with one application team—usually an internal application—with the luxury of being 100% cloud-native and container-based, as well as having 100% kick-ass developers that are 100% Infrastructure-as-Code experts). Such initiatives tend to provide very little insight on how to go on from there. They give no clues into how to form a viable strategy for cross-organization adoption of practices that make DevOps work for the organization, and not the other way around.</span></p>
<img src="https://track.hubspot.com/__ptq.gif?a=480344&k=14&r=http%3A%2F%2Fblog.quali.com%2Fblog%2Freinventing-the-wheels-in-devops-doesnt-scale.-platform-ops-does&bu=http%253A%252F%252Fblog.quali.com%252Fblog&bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; ">