4 ms·
This is getting more and more ridiculous. I even heard about GitOps (ops that use git). What is next? CliOps? Thank you for all the buzzwords without which poo
by trabant00 5y ago
This is getting more and more ridiculous. I even heard about GitOps (ops that use git). What is next? CliOps?
Thank you for all the buzzwords without which poor sysadmin old me would've never heard of coding, automation, security, version control and so on. /s
- gls2ro 5y agoI think we miss some other Ops: ProdBizSupportUxGitDevSecOps - one person doing everything (or maybe I am msising some other Ops) On a more serious note I think there is a trend to ask a lot of deep knowledge from one single person in too many areas.
- skywhopper 5y agoGitOps does have a meaning beyond just “use git”. But you aren’t wrong that the strength of the meaning is rapidly fading as does any phrase that catches on with product marketing.
- hkt 5y agoI think this is an important point: startups hawking product are a strong source of entropy, undoing the work of practitioners who are trying to say coherent things to their intended audience of peers. It'd be nice to have a safe space away from those people, even if it was closed to the world at large.
- gls2ro 5y agoI like Git and probably GitOps does mean something. But I really don't like that has the name of a specific technology. What if someone is using Mercurial shoult it call themselves MercurialOps. I also find the definition odd: "GitOps is a way of implementing Continuous Deployment for cloud native applications" [0] At least DevOps is more generic and not JavaOps or DotNetOps or PythonOps. Also I would have nothing against naming things like this except that along with naming things like this a bunch of hiring people starts asking for this very specific skills as it is like basic literacy that everyone should know or (a little bit worse) suddently appearing 1000 courses and materials from 0 to XOps in 29 minutes and suddently Github and Twitter is flooded with small projects copying at infinitum the same exercise without being able to actually teach people the hard skills of solving problems and then translating solutions into a specific technology(ies). [0] https://www.gitops.tech/ https://www.gitops.tech/
- grafelic 5y agoMy sysadm colleagues and I have been doing "GitOps" for the last ten years. Puppet, chef, ansible, terraform et al. are not really valuable without version control and some form of deployment pipeline. I am close to getting the same allergic responses to BuzzOps words that Cayce Pollard has to corporate logos.
- chazu 5y agoGitOps is a deployment methodology. Sure its a buzzword, but product devs have plenty of those as well. I _do_ agree that DevSecOps is a pointless concept - as is FinOps and other xOps crap - its become a way to throw work over the wall, which is what DevOps was trying to fix. This endless taxonomy of terms for the people who do shit that we don't want to do is a definite drag on _actual_ acceleration of SDLC in the cloud.
- goodpoint 5y agoI even heard "ChatOps", when your some IM system while doing your operational work. I hoped it was a parody. Making up fancy names for ordinary things - I wonder if it's hubris or immaturity in the industry.
- q3k 5y agoChatOps as a 'movement'/philosophy is especially weird to me. Like, when you've done your homework properly and your production deployment system is automated, ACLd, auditable, programmable, well documented and reliable then adding something like an IRC/Slack bot to it is trivial to the point of being mundane. It ends up just being another trivial integration, another tool/frontend, and more of a quality of life improvement or something cutesy than something revolutionary. When you haven't done your homework and your system is a mess, then yeah, integrating with IRC/Slack is a journey, requires you to use some superstar ChatOps tool from GitHub, requires you to spend weeks integrating your five different cloud providers into it, and you end up spending so much time on this that you have to turn it into a philosophy to justify the effort. But maybe, just maybe, you should focus on other things first. And maybe you shouldn't end up centralizing all of your deployment workflow on a third-party chat app.
- kazen44 5y agoheck, my collegue has been doing that since the 90's. (an IRCbot which shows snmp traps)