3 ms·

What a myth here, whats garbage? If you look at the early history of devops, a lot of it was developers who had previous infrastructure experience and roles wr

by UK-AL 10y ago

What a myth here, whats garbage? If you look at the early history of devops, a lot of it was developers who had previous infrastructure experience and roles writing software for automating deployment, and sever creation. It sounds to be me you have chip on your shoulder, any mention of programmer help makes you angry? When in reality programmers appreciate modern DevOps people. What makes you thing programmers dislike you? You seem to assume I am a programmer?

toomuchtodo 10y ago
No chip on my shoulder, nor assumption you're a developer. You said: "Originally yes, it was about being more cross functional instead of separate silo's." Which strikes me as the continuation of requiring someone to be familiar with everything in the stack. So you get people who are mediocre at every skill they need, and not particularly good at any single task. Also, you said: "However operations people had an issue with that" Not in the slightest. As an ops person, I embrace the DevOps model. My problem is when someone like yourself makes a broad, unsubstantiated generalization such as this. Ops people want systems to run smoothly, and also want to have a life outside of work (I'm assuming? Perhaps another broad generalization). DevOps means I work with developers to ensure their code works as expected in production as it did in development and staging, and that they're not just throwing it over the fence to me and hoping for the best.
- UK-AL 10y ago
  I didn't mean issue with it in a bad way. Just that a lot operational people noticed it was trend occurring and adapted to it. They didn't avoid it. As a DevOps can you develop code to automate things, like deployment, builds, ci, server setup? Can you setup servers, networks, monitoring? If you can do all of these things your cross functional. Originally before devops, operational teams and developer teams were completely separate. Often separate rooms. At the company I'm at devops and developers are actually on the same team. Same room and attend the same stand up meetings. We have devops people that have helped create code, and we have developers that are on call for making sure that they are on duty in case their new code falls over. Skills gradually start to overlap. We also have people have switched their focus, developers who moved to more ops skills and vice versa. We aren't different groups of people. That' what I mean by not separate silos.

by UK-AL 10y ago

toomuchtodo 10y ago

No chip on my shoulder, nor assumption you're a developer. You said: "Originally yes, it was about being more cross functional instead of separate silo's." Which strikes me as the continuation of requiring someone to be familiar with everything in the stack. So you get people who are mediocre at every skill they need, and not particularly good at any single task. Also, you said: "However operations people had an issue with that" Not in the slightest. As an ops person, I embrace the DevOps model. My problem is when someone like yourself makes a broad, unsubstantiated generalization such as this. Ops people want systems to run smoothly, and also want to have a life outside of work (I'm assuming? Perhaps another broad generalization). DevOps means I work with developers to ensure their code works as expected in production as it did in development and staging, and that they're not just throwing it over the fence to me and hoping for the best.

UK-AL 10y ago
I didn't mean issue with it in a bad way. Just that a lot operational people noticed it was trend occurring and adapted to it. They didn't avoid it. As a DevOps can you develop code to automate things, like deployment, builds, ci, server setup? Can you setup servers, networks, monitoring? If you can do all of these things your cross functional. Originally before devops, operational teams and developer teams were completely separate. Often separate rooms. At the company I'm at devops and developers are actually on the same team. Same room and attend the same stand up meetings. We have devops people that have helped create code, and we have developers that are on call for making sure that they are on duty in case their new code falls over. Skills gradually start to overlap. We also have people have switched their focus, developers who moved to more ops skills and vice versa. We aren't different groups of people. That' what I mean by not separate silos.