4 ms·

Devs don’t want to do ops

11 points by sylvainkalache 4y ago

jollyllama 4y ago
And yet, these same devs will often wish that decision makers would try coding just a little to see what they are up against.
_8j50 4y ago
If you are gonna have a strong opinon on ops, better learn to want to do ops. Read the story "belling the cat".
- verdverm 4y ago
  In my experience, you want someone who thinks about ops all the time. The difference in perspective helps reach better solutions when combined with the needs and feedback from the dev team. i.e. you'll do better with a professional cat beller on hand
  - _8j50 4y ago
    You're totally right on that.
cloudbuddies 4y ago
[dead]
oofnik 4y ago
I absolutely think there is a difference in mindset between people who specialize in writing code and people who specialize in operations. The number of people who excel at both skill sets (and enjoy doing both) is vanishingly small, and is likely to remain so. The great majority of developers I've worked with fit the description of not being interested in doing ops. I can count on one hand the number of devs I've worked with who thought their responsibilities extended beyond getting unit tests passing on their local machine. I don't blame them; the increasing responsibilities placed on development teams as enumerated in the article combined with the advent of the "DevOps team" has created a convenient demarcation of responsibility that just happens to recreate the siloed situation the DevOps movement was introduced to alleviate in the first place. I don't know what the solution is, but after a decade of DevOps, the pendulum does seem to be swinging back in the direction of dedicated operations teams. This is not to say that the collaboration has not born fruit (infrastructure as version-controlled code, GitOps, etc.), but I think it's likely that we've reached an inflection point where the fault line between development and operations is re-emerging.

4 ms·

Devs don’t want to do ops

11 points by sylvainkalache 4y ago

jollyllama 4y ago
And yet, these same devs will often wish that decision makers would try coding just a little to see what they are up against.
_8j50 4y ago
If you are gonna have a strong opinon on ops, better learn to want to do ops. Read the story "belling the cat".
- verdverm 4y ago
  In my experience, you want someone who thinks about ops all the time. The difference in perspective helps reach better solutions when combined with the needs and feedback from the dev team. i.e. you'll do better with a professional cat beller on hand
  - _8j50 4y ago
    You're totally right on that.
cloudbuddies 4y ago
[dead]
oofnik 4y ago
I absolutely think there is a difference in mindset between people who specialize in writing code and people who specialize in operations. The number of people who excel at both skill sets (and enjoy doing both) is vanishingly small, and is likely to remain so. The great majority of developers I've worked with fit the description of not being interested in doing ops. I can count on one hand the number of devs I've worked with who thought their responsibilities extended beyond getting unit tests passing on their local machine. I don't blame them; the increasing responsibilities placed on development teams as enumerated in the article combined with the advent of the "DevOps team" has created a convenient demarcation of responsibility that just happens to recreate the siloed situation the DevOps movement was introduced to alleviate in the first place. I don't know what the solution is, but after a decade of DevOps, the pendulum does seem to be swinging back in the direction of dedicated operations teams. This is not to say that the collaboration has not born fruit (infrastructure as version-controlled code, GitOps, etc.), but I think it's likely that we've reached an inflection point where the fault line between development and operations is re-emerging.