*Shudder* DevOps

• George Beech Thoughts and Rants

I think the first time I heard the term DevOps I didn’t think all that much about it, in fact I vaguely remember thinking “oh great another group of developers that think they don’t need sysadmins and they can just code themselves out of any systems problem.” Of course, at the time I was working in a soul crushing job, with incompetent programmers who thought their job was to push out code and as long as it ran on their laptop everything was just fine. So, I may have had a slightly … jaded view of things. At that point I just put my head back down and got back to work. It’s been about two years now since I first heard the term DevOps, and you know what - i still don’t likp>I think the first time I heard the term DevOps I didn’t think all that much about it, in fact I vaguely remember thinking “oh great another group of developers that think they don’t need sysadmins and they can just code themselves out of any systems problem.” Of course, at the time I was working in a soul crushing job, with incompetent programmers who thought their job was to push out code and as long as it ran on their laptop everything was just fine. So, I may have had a slightly … jaded view of things. At that point I just put my head back down and got back to work.

It’s been about two years now since I first heard the term DevOps, and you know what - i still don’t like it. However, now I don’t like it for completely new reasons.

The first, and I think biggest problem I have with the term DevOps is simply this - it shouldn’t exist. Simply, what people are calling DevOps should be shortened to “SysAdmin.” That’s right every SysAdmin should be working this way - there shouldn’t need to be a new term. Every SysAdmin should have a basic set of skills, a common ground we are first and foremost IT workers - that means we craft raw computing power into usable and complex systems. Those systems are not built by hand after the first time. They are built by automation, automation lets you not have to worry about the details of a solved problem. Automation lets you know that your complex system will be built correctly the second, third, Nth time.

In my opinion every sysadmin should at a minimum say yes to all of these things:

  • You should be able to script in at least two languages
  • You should have a passable command of one compiled language
  • You should be able to look at a piece of code in any language and have an understanding of basically what is going on
  • Why? So you can talk with your devs, that’s why

There are many people that will wave their hands, and shout “But, But that’s not what DevOps is about - DevOps is about bringing your Developers and SysAdmins closer and getting them to work together for a common good.” Ok, that’s a fair point and brings me to the second problem I have with DevOps. That problem is that the real word you are looking for is TEAMWORK. You shouldn’t need to coin a new term that says the IT department should work together - that should already be the goal.

My boss at my last job but it very well:

The guys in charge don’t care about how things get done. They only care that they do get done. All they see when the Dev and SysAdmin teams argue about anything is “The Geeks are fighting again - I don’t know about what and I don’t care, they just need to figure it out and get it done.”

Everyone outside of IT sees us as a collective but, we still bicker between each other like children a lot. We need to start seeing everyone as part of the same team. We should take the ideals of the DevOps movement and repackage them as how things are done every day in the IT department. No need for special labels, no need to make a huge fuss about it. We just need to drop the label and get to work.

For any dev that reads this and goes “what about me” you can just s/SysAdmin/Dev/g and it still applies - for the most part. I’m a SysAdmin so some things may be slanted that way.

Categories
  • (2) Misc
  • (3) Powershell
  • (3) Life
  • (1) Open Source
  • (2) Tools
  • (5) Thoughts and Rants
  • (2) Teamwork
  • (1) puppet
  • (2) infrastructure

Copyright © 2018 George Beech