2 ms·

I have no idea how DevOps morphed from having the Dev team and the Ops team working together instead of throwing shit over the wall to a job description that ne

I have no idea how DevOps morphed from having the Dev team and the Ops team working together instead of throwing shit over the wall to a job description that neither side wants to have, yet here we are.

jetbooster 3y ago
I feel like DevOps should be a skill to mention you have experience in (Ops with experience of Dev or vice versa) but somehow morphed into a job description all on its own, defeating the objective of the term completely
- jen20 3y ago
  This happened because people accepted the linguistic uncertainty, pushed by vendors who wanted to sell stuff. The well may be poisoned, but the original meaning is still perfectly well alive.
zo1 3y ago
I can tell you how I saw it happen first-hand from my "biased" viewpoint. It was 100% career-bullshitters within the org wanting to make a name for themselves by "introducing" something that the clients wanted and was a "big gap" for the consultancy. They latched onto this buzzword, and at the same time it was combined with clients latching on to it as well from all the hype it was getting in conferences, talks, articles, and other places where bullshitter evangelists push their drug. Never mind that in every sales meeting with clients we "promoted" this buzzword - so no wonder they "asked" for it. Had one of my projects burning for a year as a result, where we were told by leadership to rely on a "platform engineering" team that had a ready-made platform. Meanwhile it was just a bunch of arcane priests that knew some awful-looking JS/JSON inside a YAML templating language, running on some weird platform tool that manages K8s. Found out about the mess when I inquired after a month where this ready-made "platform" was, and they said they were still "bootstrapping a K8s cluster in AWS", then waited another 2 months for them to "bootstrap" the QA and production environments. Meanwhile the platform engineering team was led by a career-bullshitter and they had just a bunch of guys that basically did some bootcamp courses, certs and minor experience in "Their Chosen DevOps Tech". Leading to such wonderful talks summarized as: "Oh you want to explore the Hashicorp stack and weigh pros and cons? Fuck you, it's a poor-man K8s, we know better, shut up and stay in your lane." Never again. From that point on, this function 100% stayed within the dev team's control. Architecture, platform-ing, SRE, devops, whatever you want to call it.

jetbooster 3y ago

I feel like DevOps should be a skill to mention you have experience in (Ops with experience of Dev or vice versa) but somehow morphed into a job description all on its own, defeating the objective of the term completely

jen20 3y ago
This happened because people accepted the linguistic uncertainty, pushed by vendors who wanted to sell stuff. The well may be poisoned, but the original meaning is still perfectly well alive.

zo1 3y ago

I can tell you how I saw it happen first-hand from my "biased" viewpoint. It was 100% career-bullshitters within the org wanting to make a name for themselves by "introducing" something that the clients wanted and was a "big gap" for the consultancy. They latched onto this buzzword, and at the same time it was combined with clients latching on to it as well from all the hype it was getting in conferences, talks, articles, and other places where bullshitter evangelists push their drug. Never mind that in every sales meeting with clients we "promoted" this buzzword - so no wonder they "asked" for it. Had one of my projects burning for a year as a result, where we were told by leadership to rely on a "platform engineering" team that had a ready-made platform. Meanwhile it was just a bunch of arcane priests that knew some awful-looking JS/JSON inside a YAML templating language, running on some weird platform tool that manages K8s. Found out about the mess when I inquired after a month where this ready-made "platform" was, and they said they were still "bootstrapping a K8s cluster in AWS", then waited another 2 months for them to "bootstrap" the QA and production environments. Meanwhile the platform engineering team was led by a career-bullshitter and they had just a bunch of guys that basically did some bootcamp courses, certs and minor experience in "Their Chosen DevOps Tech". Leading to such wonderful talks summarized as: "Oh you want to explore the Hashicorp stack and weigh pros and cons? Fuck you, it's a poor-man K8s, we know better, shut up and stay in your lane." Never again. From that point on, this function 100% stayed within the dev team's control. Architecture, platform-ing, SRE, devops, whatever you want to call it.