DevOps

My experience with technology operations started about 1998.  I had it ingrained into me that the right model was Plan Build Operate.   I was never entirely happy with the model.  It worked. But it was very waterfall paradigm.  The Planners were usually oblivious to Operational issues and usually they had moved onto the next project so had no incentive or interest to fix problems.  More often than not Test added no value other than letting Operations know what didnt work when it went live.  All in all it was a bunch of silos leading to Operations being the poor citizen with things being blindly thrown over each wall inexorably destined to Operations. Over time I started experimenting with organisational structures to address these short comings.  Letting Developers loose on the network didnt work.  They had no discipline.  If they "fixed" something and it didnt work, they didnt know how to get back to a known state and it was left to Operations to clean up the mess.  The