It would be interesting to explain concretly what it means for each persona. Because everybody is worried of change, so when we start using new words, one might be afraid.
The automation and streamlined processes are key to achieving DevOps. It might means:
a dev. will also be able to help deploying/operating/monitoring. The idea is for the dev to be involve in what's happening on production. Use metrics, obversability... Meaning start/think to use prometheus metrics for example. Don't wait for Ops to make a comment/ticket!
an ops. will also be able to help making code change (scary word i know!)
Some are totally hermetic to code, but once they discover ansible/terraform/, they realize it's not that bad, and green pipelines are great.
both Dev & Ops might add useful pipelines, helpful to everybody!
most devs might be afraid to be on-call, so don't enforce it if your goal is to promote DevOps. But it might be interesting to be in the shoes of Ops from time to time. Pairing is a great way to do that.
an ops could be more implicated from the beginning of a new feature, rather than the day things are deployed on prod. Having dedicated time about this.
Pull Request and pipelines approbations are hugely helpful to share information and making checks. Use them!
....
Some companies keep separate roles (Dev vs Ops), but try to make them work smoothly, openly and with a clear and honest communication, in a friendly and working environment. Some others dissolve both roles into "DevOps" and everybody experience increase as anybody should be able to help on any step of the release process.
Which do you prefer?
I believe both roles skill sets overlap somewhat and it's nice knowing some operations from developers lense. But when it becomes serious business, large scales, both roles require different expertise that I don't think many people could be highly specialized in both domains.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article to describe what is DevOps.
It would be interesting to explain concretly what it means for each persona. Because everybody is worried of change, so when we start using new words, one might be afraid.
The automation and streamlined processes are key to achieving DevOps. It might means:
Some companies keep separate roles (Dev vs Ops), but try to make them work smoothly, openly and with a clear and honest communication, in a friendly and working environment. Some others dissolve both roles into "DevOps" and everybody experience increase as anybody should be able to help on any step of the release process.
Which do you prefer?
I believe both roles skill sets overlap somewhat and it's nice knowing some operations from developers lense. But when it becomes serious business, large scales, both roles require different expertise that I don't think many people could be highly specialized in both domains.