4 ms·

So if it is a "devops engineer" why not call them just "ops" if they don't do software engineering?..

by Svoka 5y ago

bckr 5y ago
Because the point of their role is to not do the same manual work over and over but to gain leverage over time by developing software to automate ops
bovermyer 5y ago
The name war continues unabated. I'm a "devops engineer." Besides pipeline code and maintaining/building out infrastructure, I also write CLI applications to handle complex infrastructure tasks. At what point is a "devops engineer" not a software engineer? [p.s., I prefer the term "platform engineer," personally]
- chadcmulligan 5y ago
  So you spend all your time looking after dev infrastructure? Can I ask how many devs there are where you work?
  - bovermyer 5y ago
    Somewhere around 75, if I had to guess.
    - chadcmulligan 5y ago
      fair enough, thanks. Just yourself or a team?
philipswood 5y ago
It’s just software engineering with more obstinate, less tolerant components and without an IDE.
- mdaniel 5y ago
  > without an IDE. There's an IJ plugin for cuelang but I'm not at my desk to know if it would be helpful for use with Dagger or not
dijksterhuis 5y ago
Historically the devops name comes from the methodology where "dev" and "ops" teams got merged so there'd be at least 1x dedicated ops person for each team of developers, only focussed on that team's operational needs. Point was to break out of the Developers versus Operations silos and actually be more productive as a single team. Back in the silo'd days... the ops teams would just flat out refuse to release any code on a Friday. Which doesn't work if you're twitter. Hence the switch. A lot of my time as a "devops" engineer is reiterating that I can fix and automate as much as you want me too, but if your developers don't think about the infra the code eventually runs on in prod then your software is just gonna keep breaking --- "but it worked fine on my local machine". So, while I agree the "Devops Engineer" name is a bit ridiculous, and not in the spirit of the original methodology, half of my job is writing software that tries to help developers not break production and the other half is attempting to change the culture, even slightly, towards "oh, wait, will this run in production?".

So if it is a "devops engineer" why not call them just "ops" if they don't do software engineering?..

by Svoka 5y ago

So if it is a "devops engineer" why not call them just "ops" if they don't do software engineering?..

bckr 5y ago

Because the point of their role is to not do the same manual work over and over but to gain leverage over time by developing software to automate ops

bovermyer 5y ago

The name war continues unabated. I'm a "devops engineer." Besides pipeline code and maintaining/building out infrastructure, I also write CLI applications to handle complex infrastructure tasks. At what point is a "devops engineer" not a software engineer? [p.s., I prefer the term "platform engineer," personally]

chadcmulligan 5y ago
So you spend all your time looking after dev infrastructure? Can I ask how many devs there are where you work?
- bovermyer 5y ago
  Somewhere around 75, if I had to guess.
  - chadcmulligan 5y ago
    fair enough, thanks. Just yourself or a team?

philipswood 5y ago

It’s just software engineering with more obstinate, less tolerant components and without an IDE.

mdaniel 5y ago
> without an IDE. There's an IJ plugin for cuelang but I'm not at my desk to know if it would be helpful for use with Dagger or not

dijksterhuis 5y ago

Historically the devops name comes from the methodology where "dev" and "ops" teams got merged so there'd be at least 1x dedicated ops person for each team of developers, only focussed on that team's operational needs. Point was to break out of the Developers versus Operations silos and actually be more productive as a single team. Back in the silo'd days... the ops teams would just flat out refuse to release any code on a Friday. Which doesn't work if you're twitter. Hence the switch. A lot of my time as a "devops" engineer is reiterating that I can fix and automate as much as you want me too, but if your developers don't think about the infra the code eventually runs on in prod then your software is just gonna keep breaking --- "but it worked fine on my local machine". So, while I agree the "Devops Engineer" name is a bit ridiculous, and not in the spirit of the original methodology, half of my job is writing software that tries to help developers not break production and the other half is attempting to change the culture, even slightly, towards "oh, wait, will this run in production?".