Seems like a slim use case, no?
236 karma · joined August 9, 2018
Our GIS clients run WS as a Deskstop OS with ESRIs ArcGIS Pro. Incredibly common.
And once you have that - add in Active directory, DFS and random Windows Servers for running archaic proprietary licensing services.
After acquisition - we were handed down the order to migrate to AWS.
This was after (in the mess of the merger) the colo contracts were basically ignored and not renewed. Once someone within the company realized the issue, it was the 11th hour.
After many, many attempts to discuss our (Operations team) concerns, we abandoned our protests. It was clear the new CTO wouldn't cave and sign the contract.
Some superficial testing was conducted and the order came down to move...NOW.
We began moving hundreds (maybe thousands) of very resource hungry DB servers first (there was no way to use something like RDS without major app/config changes).
Once the AWS bill came in, the CFO blew their lid and within 90 days we were migrating BACK to our DCs (and the millions of dollars of hardware we left idling).
Granted the jury is still out on Intel (IMO) but it was certainly a signal of a culture shift.
He described nausea quite often when I saw him but the results were pretty astounding.
He then hit a wall where gastroparesis would happen quite often and I happened to be at his house when one of these bouts got very severe. He went from feeling bad, to hunched over in pain and started projectile vomiting in the span of 30 minutes. He said it was clearly the meal he had eaten several days ago...it was awful.
I believe this happened to him several more times - and AFAIK he stopped taking it, and promptly regained some weight back.
https://github.com/microsoft/Microsoft-Win32-Content-Prep-To...
Outside of the existing issues with Bedside nursing (long days, physically demanding) - the primary issue is staffing. Pre-pandemic the ratios were already bad but now many are leaving for travel contracts which carry significantly better wages. It quickly becomes a loop where employees leave for Travel Contracts, and then can only be backfilled with Travel Contracts. The remaining FT staff nurses are left making much less money, and have to assist "training" with the outside Travel nurses. And while this is nothing against them - The travel RNs also often have a different "vibe" as they are much less focused on long term improvement or problem solving within the Unit.
Also ICU/PCU/ER nursing throughout the pandemic was a terribly depressing place to be. Leaving many of my Wifes colleagues (including herself) with what is essentially PTSD with little or no support from the Hospital System.
Ended up going with a handful of Ruckus r610 used off of Ebay. When re-flashed with the "unleashed" firmware, configures one to act as a local controller for the rest. I've been very happy with it so far.
Your giant list of of terminology isn't making much of an impact on me. In fact many of those sounds terrible.
So giving your post the benefit of the doubt, when can I expect to be disrupted out of a job by even a single item on your list?
As we grow, our goal remains the same: empower developers and businesses to ship better products faster by eliminating DevOps. We’re working to end the tyranny of complexity forced on developers by cloud providers who’d rather sell certifications than focus on developer productivity.
My Wife, a ICU RN+CCRN spent most of her 2020 on the COVID floor. It was pretty brutal for her.
She has coworkers, of equal status, who experienced pandemic alongside her first hand - who were extremely hesitant to get the vaccine. This includes several months after the initial rollout to staff.
Enterprise may not be the targeted market at this point, but its a cash cow that would be hard to chase (Especially given M1 hurts the consumer side). A number of VDI/Terminal protocols solved this problem a long time ago.