Group items tagged

How can there be a DevOps engineer? I often see vacancies with the job title DevOps engineer and always think, this makes no sense. DevOps is all about collaboration between two different expertises. In this blog post, I want to share the history of DevOps and my thought about the role of DevOps engineer.

DevOps cannot be a single role. What do you think?

DevOps is een reactie op de onderlinge afhankelijkheid van software development (Dev) en operations (Ops). De spreekwoordelijke muurtjes tussen de Dev en Ops afdeling bestaan niet meer binnen DevOps. De implementatie van DevOps resulteert in een versnelling van de ' time to market' en een verhoging van de kwaliteit van delivery. DevOps gaat een stap verder in de richting die met Agile werken al is ingezet. Waar bij Agile werken frequent werkende software met de meeste toegevoegde waarde wordt opgeleverd, gaat DevOps nog een stap verder door de applicatie delivery te versnellen.

I've been interviewing candidates for a DevOps opening that Interactive Intelligence has available and I keep getting asked by candidates, 'What does DevOps mean to you?' If you were to google 'What is devops?' you'll find pages and pages of blogs and articles answering just that. I've read a few of them but I still find myself struggling to give a clear answer. I think the trouble with anwering this question is that people generally expect a 2-3 sentence answer and it's difficult to encapsulate all my thoughts on the subject that concisely. Another issue is that when I'm talking about DevOps, I feel like my attempts at explaining it come off as if it's some magical, fundamental, paradigm shift that exploded onto the scene and if followed will lead to peace on earth and an end to all hunger.

DevOps is going mainstream as large, complex organizations credit DevOps with IT transformation. Author and DevOps guru Gene Kim details how leaders have successfully transformed enterprise IT.

Bent je nog druk met Agile implementeren? Wees je er dan van bewust dat de volgende vloedgolf aan veranderingen er al weer aan komt. De golf DevOps maakt af wat Agile begonnen is: technologische en procesmatige integratie tussen ontwikkeling en beheer. Waar Agile zich primair focust op klant en it-vernieuwing, wordt met DevOps definitief de laatste muur geslecht: die voor de beheerafdeling. In deze blog licht ik een tipje van de sluier van DevOps op.

In a fit of rage caused by reading yet another email in which one of our customers proposed creating a "devops team" so as to "implement" devops, I tweeted that "THERE IS NO SUCH THING AS A DEVOPS TEAM." Like all slogans, there's plenty of heat to go with the light, so here's the scoop [...]

There is lots of talk about what DevOps is and means, even a Wikipedia page, to which I may soon give some much needed love. However, a friend recently asked if I knew anyone worth hiring for a "devops" role, and I found myself asking clarifying questions about the sort of person he had in mind. Seemed worth writing down. The friend was looking for engineers. So what does it mean for an engineer to be devops-y?

"I have worked in environments where reacting was the "normal" way to approach issues and being proactive was just a waste of time... *facepalm* The seemingly simple idea of changing the workplace culture from reactive to proactive was hard to pitch, let alone implement on my own. 18 months ago, I knew there was a better way of doing things and I was determined to find something. I had been watching developers implement Agile Development processes with great envy and I was starting to see concepts that would have great outcomes if adopted in a traditional operations environment. Finally having something tangible to explore I started looking into Agile Operations, which led me DevOps. Lurking in the shadows for a while, I digested as much as I could of the DevOps movement. I thought it was  time to talk to some of the developers and get them on board. 6 months on and here we are... "

Devops is still a new topic for lots of people, and this introduction is a nice place to start. It provides a bit of the history, along with explaining Devops with a focus on culture, automation, measurement and sharing.

DevOps is evolving from what started as little more than a rally cry, into a culture for continuous delivery of IT services. As more pieces of the puzzle fall into place, we understand that DevOps is primarily a matter of human collaboration -- assisted, but not encompassed by, certain tools and technologies. This essay is my take on DevOps, and why I think it is about embracing distributed, autonomous operational methods that support scalable human-computer processes.

DevOps Days has celebrated 5 years since the initial conference in Ghent in 2009. With events in Helsinki, Vancouver and Tel Aviv just in the month of November, the DevOps Days series has taken place across multiple cities all over the world in these 5 years. InfoQ talked to Patrick Debois and Kris Buytaert, part of the team that organized the first event 5 years ago.

The Shutl engineering team has been operating with a DevOps mentality for over two years. We started by rebuilding our infrastructure under Chef and embedding our operations engineers into our agile product development process. We made great progress and saw a big improvement in delivery and quality as all team members were responsible for getting things live and ensuring their long-term maintainability. But… we still had a silo. Only a few of our team were doing the lion's share of the work when it came to maintaining our infrastructure, and on-call duties were shared by just a small number of people. Over the past six months, we've changed that. So, rather than extol the virtues of this approach - there are plenty of articles doing that! - we thought we'd share some of the steps we took to make every engineer a DevOps engineer.

We wrote back in August about 3 "litmus test" questions about #DevOps in your organisation. We'd like to add 3 more questions that focus on the more operational aspects of DevOps.

DevOps Knowledge Base - This knowledge base includes topics of: Software Configuration Management, Continuous Delivery, Infrastructure Orchestration and DevOps

Have you ever felt like people were conspiring to make DevOps fail? They probably had good intentions but they just made DevOps more difficult than it should be. What if it was actually intentional? The resistance gets organized…

A discussion of the important difference between automation and devops, in particular with regards hiring for impact. Don't hire an automation specialist as your devops strategy.

Job titles are important because they describe what we do, which shapes our identity and guides our activity. It's important that job titles are rational and make sense. If they don't, it causes confusion and stress for individuals, teams and organizations. This is why I have a problem with using the term "DevOps" in job titles. This is becoming more and more prevalent in our industry, mainly for self- promotional and recruiting reasons. DevOps is hot… and therefore marketable.

HOW DEV VS. OPS BECAME DEVOPS The founder of DevOps explains how the movement started and where it's headed.

Until recently I was not able to clearly articulate what DevOps is. Then one day, when trying to describe what we are building at Nirmata to an investor, I said something to the effect of, "its all about enabling developers to perform operations, using automation". That made sense to them; and, I've since started using the following definition for DevOps: Developers doing Operations using Automation

Arrested DevOps is hosted by Matt Stratton, Trevor Hess, and Bridget Kromhout. ADO is the podcast that helps you achieve understanding, develop good practices, and operate your team and business for maximum DevOps awesomeness.