Takeaway: DevOps methods are first rate staff, second class assets. Helluva difference from Enterprise IT.
When I’m working with people on IT Infrastructure, the existing habits (learned responses?) of IT managers is to invest heavily in high cost, high quality systems from known vendors that have high maintenance costs. These first class assets are expected to have low cost of operations & high reliability.
Cost can be saved by hiring second rate staff who don’t understand technology but know enough to operate the systems to a lesser or greater degree.
Proof point: compare the demonstrated skills of big cloud providers using low cost, no support, no maintenance assets.
DevOps is the reverse
Working with DevOps, its quickly becomes clear that formula is reversed but comes out with the same result. In DevOps, hiring first class staff is critical. Staff who are high cost, high quality who are able to self-motivate, self-organise and adapt to multiple requirements, languages and evolving changes in their platforms. Those staff are also ‘high maintenance’ needed time to retrain, retool and replace their skills constantly.
In a DevOps environment, the use of high quality, high cost systems is not needed. Customers can choose to run on low-cost, second-class assets.
Can You Run First Class Assets and First Rate Staff
Sure you can. The question is whether this level of spend/investment will produce a return. Having high staff costs AND high infrastructure costs (don’t forget the maintenance/service contracts here) doesn’t seem to make a lot of sense.
Thats why public clouds use low cost infrastructure.