Leaked Zoom all-hands: CEO says employees must return to offices because they can't be as innovative or get to know each other on Zoom
Leaked Zoom all-hands: CEO says employees must return to offices because they can't be as innovative or get to know each other on Zoom
Zoom CEO Eric Yuan discussed the benefits of in-person work in a leaked meeting.
Leaked Zoom all-hands: CEO says employees must return to offices because they can't be as innovative or get to know each other on Zoom::Zoom CEO Eric Yuan discussed the benefits of in-person work in a leaked meeting.
You're viewing a single thread.
They should try using Teams, should solve the problem.
Better upgrade then networks dawg
The only problem teams solves is "why are people too happy with remote work", and it's very effective at fixing that.
I actually charge a teams tax on my wage requirements if I find out they're using broken last-gen weak shit like teams, Ansible, or vro.
last-gen weak shit like teams, Ansible, or vro.
A role I worked had this holy trinity. Moving to teams was nail in the coffin for me. Out of interest, what is "broken and last gen" about Ansible? And what's newer and better than it? I find it to be okay for infra patching tasks...
What's wrong with Ansible?
I dunno man, that's what I was trying to find out.... I thought I was out of the loop on something here.
Tribalism will affect how this is received, like cursing out vi or apple in a crowded room, but it's important to see what else is out there and what they offer. Hint: If Ansible is bolting things onto the side of itself like event-driven triggers and connecting to AWX, then you have a good idea of what Ansible needs crutches to do and keep up to last-gen tech. One can only bolt so many bags on the side before the entirety falls apart, and IBM no longer has the goodwill to keep enthusiasts doing the heavy-lifting -- even if IBM is repeating what Canonical did a decade or more ago without repercussion.
Patching shouldn't need an automation scaffolding. I'll leave that there, that it's entirely possible to patch your systems in a very automated, patchset-promoted fashion and not need to touch what we currently call Automation. I've seen and done it 20+ years, but to be fair that's only how long I've been in the Enterprise space where that was the focus vs the relaxed tolerances of the soho/robo market.
This-gen tech is responsive and self-organizing from the ground up, and responds in real-time to changes. Comically, it's usually a collection of well-established components like consul that powers the this-gen stuff.
I joined a job with this holy trinity, but they pay the tax every paycheque. I "dead sea" left a toxic mess with failing puppet managers a FIN coup had installed but with good tooling, to a great environment with known faces and good management left behind after their arrogant toxicity couldn't cope with remote-first workers and bailed. The fact the tooling is complete shite is just a feature we cope with in this awesome environment, and while the environment stays excellent we'll solve that technical challenge or we'll bail if the environment gets toxic again first.