I think that what you say is what DevOps was intended to be, but to be honest, most developers I met have zero interest in the Ops part and they don't care. So, it kinda morphed into a position for individuals with skills at Ops and Dev trying to get some value from the original idea.
"...most developers I met have zero interest in the Ops part and they don't care..."
This is a tough one. Some do, some don't, some move from Dev To Ops, some Ops move into Dev. IMO, everyone in an organization should care about the product/service the organization exists for. A dev who does not care about the output of their labor is, honestly, not someone I would want to work with. The laissez-faire attitude spreads and the next thing you know no one cares and people start leaving.
This has been my experience as well. It is true that not all developers want to do operations things and it's even more true in the vice versa. However, I believe that is a trend that is going to change and must change if folks want a face paced, quick iterations, and effective CI/CD environment.
I'm with you in the idea that you should care about the complete lifecycle of what you do. The problem is that reality is what it is and in more or less 10 years I have found 3 kinds of attitudes towards Ops from developers:
They don't care as long as the build is green. (most of them)
They have zero interest in Ops but they don't want to depend on other teams and so they learn DevOps to have freedom. (usually, highly skilled developers that pursue feedback as quickly as possible)
They care about Ops and eagerly learn about it. (I have met about 3 or 4)
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.
I think that what you say is what DevOps was intended to be, but to be honest, most developers I met have zero interest in the Ops part and they don't care. So, it kinda morphed into a position for individuals with skills at Ops and Dev trying to get some value from the original idea.
"...most developers I met have zero interest in the Ops part and they don't care..."
This is a tough one. Some do, some don't, some move from Dev To Ops, some Ops move into Dev. IMO, everyone in an organization should care about the product/service the organization exists for. A dev who does not care about the output of their labor is, honestly, not someone I would want to work with. The laissez-faire attitude spreads and the next thing you know no one cares and people start leaving.
This has been my experience as well. It is true that not all developers want to do operations things and it's even more true in the vice versa. However, I believe that is a trend that is going to change and must change if folks want a face paced, quick iterations, and effective CI/CD environment.
I'm with you in the idea that you should care about the complete lifecycle of what you do. The problem is that reality is what it is and in more or less 10 years I have found 3 kinds of attitudes towards Ops from developers:
They don't care as long as the build is green. (most of them)
They have zero interest in Ops but they don't want to depend on other teams and so they learn DevOps to have freedom. (usually, highly skilled developers that pursue feedback as quickly as possible)
They care about Ops and eagerly learn about it. (I have met about 3 or 4)