Read on Twitter
What does "DevOps" mean to you?I think that this is a widely misunderstood term in our field.
In this short thread
I share what "DevOps" means to me.Any correction or clarification is more than welcome
The problem to solve.Development (Dev) and Operations (Ops) don't share goals when they are separate teams.
"Dev" wants to deliver software fast.
"Ops" wants to deploy stable software and the quick pace makes it harder.
When something goes wrong, teams blame each other.
The solution.Joining "Dev" and "Ops" in the same team.
With shared goals they can work more effectively together.
This cross-functional team has all the skills needed to take requirements, build software, and deploy it.
And they can do it quickly, reliably and sustainably
An extended view.The problems of separate teams also occur with other activities, such as QA.
"Dev" wants to deliver software fast. QA tries to find defects. No shared goals.
From this POV, the term "DevOps" is misleading. It deemphasizes QA.
Should it be "DevQAOps"?
In summary.For me, DevOps is a culture where all the traditionally post-development phases (Operations, QA, ...) are integrated into development from day 1 and the team has the skills needed to carry them out.
With this in mind,
What does "DevOps Engineer" mean? 
