53

DevOps is about maintaining code, is that correct? DevOps is not "just" about code, or systems, or any one thing. DevOps is a very general term that covers all things related to software delivery. Site Reliability Engineering is a term popularized by Google. From this article https://landing.google.com/sre/interview/ben-treynor.html we can distill their ...


23

Dave Swersky already posted an excellent response above with Ben Treynor's definition of SRE, which is as poignant today as it was in 2003. Fundamentally, it’s what happens when you ask a software engineer to design an operations function. So, in an attempt to further define "DevOps", here's an excerpt from the book Effective DevOps by Jennifer Davis &...


18

Site Reliability Engineering falls under more or less traditional operations, but heavily automated and version controlled, what is also called Infrastructure as Code. It is a well defined vertical role. In modern DevOps this is the vertical slice that relates to Operations. You can have a team of SRE. DevOps as such is a cultural change for an organization....


11

There are four main reasons why you can feel your team is understaffed: Poor organization and planning of work Doing work someone else should be doing Doing work that should not be done at all Being actually understaffed Start with a review of the first three points. Read the Phoenix Project on ideas how to do the first. Ask yourself for every task you ...


10

From the "how it should properly work"/"how it was meant" perspective there is no real "DevOps engineer" because DevOps is a methodology/culture which emphasizes also on technical practices which should stretch across as many roles as possible and feasible. How can we apply the CALMS (Culture, Automation, Lean, Measure, Share) mantra here? (Taking into ...


8

Background: Besides for providing support to our current infrastructure and to our Developers, we do monthly planning as a DevOps team for what we want to accomplish on top of helping dev teams within sprints and new projects that are launched. However, during the month we often notice extra things that need to be done and improved, which we then add to our ...


8

I believe DevOps is orthogonal to your question, i.e., it changes nothing compared to a "classical" approach (or to hiring any team at all, not only for software development). You identify what your key needs are (for example, an "architect" who is able to structure large software systems; some "hacker" who is able to fix a Kernel driver if needed; a "tester"...


6

I actually take a page from the SRE Handbook on this one, which I think is very relevant. DevOps specialties are not meant to grow horizontally with an organization. Rather, if you see that things aren't getting done then it's a signal you're not properly empowering developers to self-service. Evaluate your processes and see how they align to the commonly ...


4

I apologize for the novel length response, but I want the industry to start having these discussions as the potential advantages are huge. The problem is not that it is necessarily more complicated but that it requires experience that is difficult to find today and which goes against traditional models. This is not an uncommon occurrence in the computing ...


4

I assume this team of two is going from project to project and establishing DevOps stuff there (creating CI/CD pipelines, supporting the other devs creating Dockerfiles, or whatever technology you are using). In other words, type 3, 4, 5 or 6 as per http://web.devopstopologies.com/ . In this case, a sign of shortage is simply too much workload for those two;...


3

Since DevOps is a hot trend in IT, companies are seeking top-notch DevOps talent. However, before you begin assembling your team, there are a few things you should consider: What kind of DevOps? Imagine a rock band is searching for a new guitarist. There are lots of people who know how to play the guitar, but there are so many music styles that can be ...


1

AFAIK, there is no boundary for DevOps engineer. When it comes to questions you have put together, it is general misconception to consider DevOps engineer as administrators. DevOps is change in culture, change in mindset and change in approach. DevOps culture fills the gaps development and operations. DevOps mindset allows engineers to try out of the ...


1

I was under the impression DevSecOps was a mindset, not a team - if you have a Dev(Sec)Ops "team" you're doing it wrong... I'm trying to wrap my head around putting two "DevOps Engineers" together and calling them a "DevOps Team." We have development teams, SCM, Application Security and Systems Engineers all working in tandem for a rapid deployment/release ...


1

I'm currently extending my DevOps team, without forgetting skills, for me, the most important thing is the "mindset". Amazingly, not a lot of people around with the right mindset of continuous improvement.


1

DevOps is a "team" of people that includes the development and operations teams. (security/compliance combined). You shouldn't think about the devops "team" as a separate entity but part of the larger organization. Checkout http://web.devopstopologies.com/ for organizational structure. You can see it's about moving together.


1

Your probably looking more at the calibre of your platform engineers. You don't want to make developers jobs hardware nor do you want your software engineers to need to handle more complexity, it's simply contrary to your goal. Instead it sounds like you are looking for a platform engineer who is able to wrangle the relevant technologies together so that ...


1

Another way to describe differences between Site Reliability Engineering and DevOps is to look at Wikipedia's explanation of a Site Reliability Engineer, which starts like so: Site reliability engineer (SRE) is a job description given to software engineers focused on reliability, scalability, and the development of cloud computing infrastructure, known as ...


Only top voted, non community-wiki answers of a minimum length are eligible