You can't be in the web development field without hearing about DevOps. It's like this thing that everybody knows about, but nobody really understa...
For further actions, you may consider blocking this person and/or reporting abuse
A common mistake IMHO is to delegate a "DevOps" role to a separate team that works for the other teams. It leads to the "Ivory Tower" issue. There should be one or more people with DevOps role for each team, because the DevOps needs to be part of the daily work of a software project.
I'd go further; there is no such thing as 'a DevOps' - it's not a job, and it's not a role. It's a mindset and a way of working which everyone in the team has to commit to.
I agree that it's more of a mindset, and I can tell it may take a herculean effort to apply such a mindset for some companies. In my experience, companies that apply software factory principles and assign very specific roles and responsibilities to each employee have a hard time moving to DevOps. After all, a software factory treats software like an assembly line. People get used to the assembly line like Charles Chaplin in "Modern Times".There is little room for innovation, processes are long and tedious and there is a lot of friction between different teams. In these cases, it may be a good idea to have a transition plan where there is a "DevOps" role for each team.
Thank you for this incredibly well-written, concise post! Exactly as you said, DevOps was a term I only vaguely knew about and would hear of with developer circles.
I've seen DevOps throughout a few projects, but not many. Is it fairly new?
DevOps is not only useful but it is also (now a days) vital if you're serious about your software.
Ever since software development became a thing, we have had to deal with integrating, building and delivering our software, but only now we are calling it DevOps.
That's because delivering your software fast has become just as important as developing it well. You either get your product on the market fast or someone else will.
You take the operations burden from the developers to let them focus on developing and apply continuous integration to make sure they move forward and never backwards.
Helloooo from DevOps guy , AMA.
Me me!
What does the day-to-day of DevOps look like?
Ah I did not want to highjack the post, but to answer it quick.
Optimize CI/CD pipelines
Work on Performance on infrastructure
Come up with solvable solutions for Devs problem of any kind
Code
Fix Issues that Dev reported with the infrastructure
Help Dev come up with easier way of doing things.
That is a good list, if you take DevOps as “the group who used to do ops and is now automating its work”. Which is in fact a good path to follow if you are “previous style ops” and don’t want to wait to be automated by developers.