A much-anticipated sequel to the Phoenix project, the Unicorn project was launched late last year. Here are my thoughts:
With the launch of the Unicorn project, I revisited the Phoenix project. Seeing as my previous review was a mite lackluster, I decided to revisit that, too.
The title of this post might seem a bit on the conceited side. After all, who am I to claim to be a DevOps practitioner, much less thinker? I will simply say that I am working to implement DevOps principles in my day to day life, am spending more than a little time reading, thinking, and writing about DevOps, and though I may not be considered a DevOps thinker today, I certainly aspire to join their ranks. The title, then, is a statement of aspiration, more than a statement of achievement.
When I wrote my blog post about important features of a service management tool, I wrote “I am increasingly coming to believe that the change management process is perhaps the most important one for success in ITIL – not to mention DevOps – adoption” – and I stand by that assessment. Not because change management is such a revolutionary idea in and of itself, but because of what true management of change means for a business.
I have, for some time now, been reading up on DevOps. One thing that, for some reason, keeps coming up, is that people seem to think that there is a fundamental incompatibility between DevOps and ITIL. The more I read, however, the more it becomes clear that there is no disparity at all between them. If you have been following my blog for a while, it should be fairly obvious that I have drunk the ITIL Kool-aid. Simply put, I think any operations shop that is not implementing ITIL is doing it wrong.
When performing a task, one will often be in the position to choose either doing something quickly, or doing something right. In many cases, either example is fine, as the job gets done satisfactorily. Still, I believe that you are better off with doing it right each and every time. Now, before you think I am preaching about my own level of perfection, know that this is not the case, and that I fail to do this more often than I would like to admit. This is not an admonishment; it is a level to which I aspire.
The first time I worked IT support in a professional setting, I was seventeen years old. I had gotten an internship (one day per week) with my uncle’s firm as part of my third year of vocational training, and spent a day per week with them. In the beginning, I was mostly hanging out with the IT staff, not really providing much of any use to anyone.