DevOp and why I want to be one – #DevOps Series
Over the last year I have had a number of adventures, some good and some bad – but all of them experiences. Last month I read about a term for the 1st time that really spoke to me, it encapsulated a concept which had been brewing in my head for a while – a DevOp, Developer Operator.
In November last year I was in Madrid attending SAP TechEd, and you could not move for people talking about various platforms and Developers being the new kingmakers – being an Basis guy specialising in infrastructure it may have been boring for many people, but for me the lightbulb was turning on. I was very interested in how to connect technologies together, not just how to build the infrastructure and let other people worry about that stuff. These thoughts fermented a little more, I continued to experiment with Ruby, C# and my Microsoft Kinect – gaining some more skills as time would allow. At Teched I met the excellent James Governor and Tom Rafferty, two analysts from Redmonk who I have a great deal of time and admiration for. After following them on Twitter for a while, I found out about Monkigras, a developer conference in London. I glanced at the attendee list and booked my ticket, paying for it myself as I figured “why would my employer pay for me to go to something so far outside my day job”, took 2 days leave and arranged to stay at my friend’s house.
Despite knowing only 1 other attendee, Monkigras would turn out to be an amazing conference, I heard lots and lots of new words, understood perhaps about 20% of them and had to make copious notes of the others. The thing that I took away from it the most was the developers and APIs are the future, infrastructure is a commodity that just needs to exist – the real value is in the data and it’s manipulation. “It always has been” I hear you cry – well that is correct but instead of putting it into Excel and making stupid graphs or putting it into PowerPoint, lets use applications to perform transformations, link it to other data attributes from another data set through an API and turn it into something amazing – this link is from a speaker who used GitHub and LastFm to create a music map of developers
For me my true love is not code, I like the idea of it and messing with it, but if you tried to get me to write as a job, one of us would be dead in about a week – so I thought some more about what the perfect balance would be. My good friend Simon McCartney came to mind, an exceptional infrastructure administrator and someone who is comfortable working with code, he calls himself a digital carpenter, Hugh MacLeod would call him a digital crofter. The ability to continue to work as an infrastructure person along with the ability to work with scripts and code is a powerful combination which provides a great deal of value to your business and the team.
We are uncovering better ways of running systems by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes over tools
Working systems over comprehensive documentation
Customer and developer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more
There are a number of reasons why I am drawn to the way of the DevOp, most of them are encapsulated above, and perhaps I will explore these personal areas in more detail in public and risk the wrath of various people, then again perhaps not. The one of the main attractions being that with shorter life cycles and products becoming easier to deploy, a multi-talented person who is a solid ‘all-rounder’ will be in greater demand than the 2 or 3 niche people you would have hired previously, as software lifecycles are shorter – living with your mistake is not as long as it used to be.
Another thing I like about development, it the ability to do really smart things with data like this visualisation of Facebook relationships – how totally cool is that picture which is derived from the most basis data which can be queried form the Facebook social graph
So for now I am going to continue down the road of becoming a DevOp, taking every opportunity to deploy a code or script solution to improve my effectiveness and provide increased value for my clients. Ultimately I want to build things, real, virtual and data based. I want those things to mean something, to me and my clients – As Hugh MacLeod would say – I have the Hunger and I am damn well going to use it
I actually like the idea of devops. #sapadmin didn't get the attention it deserves but that doesn't mean I'm giving up on bringing attention to SAP system administration. In my opinion SAP can make a lot of improvements in this area and by doing that reduce operational costs.
Solution Manager 7.1 is an interesting product in that sense, more and more functionality is coming out and there are very useful features in there. There is still a lot of work to be done as well.
Where I also see a good opportunity is SAP Landscape Virtualization Management. The custom operations/hooks/services offer a good way to create automation scripts for a lot of different actions / use-cases.
Ref your personal blog post:
I would prefer to group up and get this show on the road ➕
in my case it's the other way around: I'm a developer but have to maintain my own systems. Lots of fun and challenges.
P.S.: Don't forget to follow @DEVOPS_BORAT on twitter 😉
I see the manifesto on Devops is extension for/of Agile. And it is rightly said we don't look behind for support & maintain at several levels and delay for process in the name of operations. Developers learn step up to operations. Similarly Operations come down to the level of Development, it will be good game to watch if all us think so and not the other way round how it usually is portrayed . No one or role is mean at the end of the day right? Every one is best in their roles 🙂
Fun to watch going forward