DevOps DevOps DevOps

By | June 12, 2014

So I’ve spent the last two weeks in The States at a couple of tech events. And aside from the usual learning about new technologies and the likes, one thing that’s come up over and over again is….. DevOps DevOps DevOps…..

The new IT admin has to know coding, and has to be comfortable with APIs.  He/she has to be part developer, part operations.  Hence the term DevOps.

Last week I was on the Speaking In Tech podcast, talking about exactly this. And then this week at HP Discover in Vegas, I couldn’t move without hearing comments like “Companies need to be hiring 24yr olds” and “Companies need to be embracing APIs to enable them to adopt cloud and next-gen IT“.

Anyway…. I just thought I’d point at a couple of good places to start learning some of this DevOps jazz (happy to know about more)…. –

Pluralsight (DISCLAIMER: I work for these guys… but the content they have is top-notch)

Code Academy

I’ve given links to Python stuff, because from where I stand, Python is looking like may be the best Devops style language to have. But the sites mentioned above have much more than just Python. For example – shameless plug – I’ve done some Storage and Linux for Pluralsight.  And of course they have Java and Ruby stuff too…

Anyway….. The future’s bright, the future’s APIs!

Oh and if you’re a traditional IT guy that’s used to the CLI and GUI, don’t be scared off by thinking that you need to be able to code like Guido van Rossum. The DevOps guy isn’t gonna be a full blown developer.  But obviously the better you are with it, the better positioned you’ll be.

Oh and I’ve got this for my kids – they don’t know yet, I’m keeping it as a surprise – coz I’m such a cool Dad 😀

One thought on “DevOps DevOps DevOps

  1. Kevin Stay

    Hmmm… I have thought about this post from time to time in the past few weeks. While I agree with what you state I also somewhat disagree. The ability to write solid code is definitely a lot more important to an infrastructure engineer these days and that will only become more so the case in the coming years. However, that does not change the fact, especially for larger companies, your ‘go-to’ infrastructure unicorns still need the same core attributes and in this order of importance: IQ, formal education (as close to real engineering or CS as possible), and experience.

    Nothing makes up for insufficient intelligence. Not all of the infra team need to be brilliant, but those team foundation engineers absolutely need to be ~2 standard deviations above the mean.

    No amount of training or self motivation can replace a formal degree in engineering (mechanical, electrical, etc.) or the hard sciences. The knowledge, methodologies and approaches to everything you do cannot simply be learned “as you go along” or in some other way; not going to happen.

    Finally, the rate at which you accumulate valuable knowledge and skills from experiences is proportional to both your intelligence and your formal education. Twenty years of experience for someone sporting an IQ of 116 and one of these made up candy-ass business degrees in Computer Information Systems is simply NOT the same as twenty years of experience for someone with an ME degree and IQ of 129. Not even close.

    Anyone with the requisite intelligence, real degree, and experience can be trained in Python or the like. Compare that person with any 24 year old ‘hot shot’ and you get two things: foolish companies thinking the kid is the way to go and companies with even a modicum of brains sending their actual senior engineers to get trained in relevant coding/languages as needed.

Leave a Reply

Your email address will not be published. Required fields are marked *


You can add images to your comment by clicking here.