Storage greybeard: DevOps, plagiarism and horrible wrongness

Ralph Vandermeer

There's nothing new under the Sun

A penny-farthing bike - re-inventing the - vintage - wheel

StorageBod Recently I ve been spending time thinking about what DevOps really means to my teams and to me.

As an application programmer, I was expected to do the deployment, support the deployment and be involved with application from the cradle to undeath.

As a systems programmer, we scripted and automated in a variety of languages; we extended and expanded functionality of system programs.

We plagiarised and shared scripts – mostly internally but also, at times, scripts would make their way round the community via the contractor transmission method.

Many DevOps engineers would look at how we worked and find it instantly familiar… although the rigorous change control and formalised processes might freak them out a bit.

I ve boiled DevOps and the idea of the Site Reliability Engineering function down in my mind to the following:

Fix Bad Stuff

Stop Bad Stuff happening

Do Good Stuff

Make Good Stuff easier to do

It turns out that my teams are already pretty much working in this way; some folks spend more time dealing with the Bad Stuff and some spend more time dealing with the Good Stuff.

Ralph Vandermeer
Zupyak is a free content platform for publishing and discovering stories, software and startups.