Pay to play and keep selling. Understand the liabilities and cover your ass, address the biggest risks.
The point of SOC2 is really demonstrate that you have controls. The other fake compliance areas are scarier for sure. You used to see really blatant issues — I recall early SaaS companies pitching to my enterprise with sales engineers showing me customer data.
Microsoft refused to provide diagrams to the Feds detailing how Azure works. They got the FedRAMP High stamp anyway, because they already sold it to half the Fed. That’s more real… as a situation where a Chinese hacker could compromise data in a dedicated “government cloud” by compromising a certificate in an onprem dev environment should be impossible… yet it happened.
It depends where you are. Most cities in the Northeast you are correct. But coastal areas, big swaths of New Jersey and Long Island IIRC are definitely dependent on power. Towns with water towers usually pump it from the ground.
Alot of suburbs that can't or won't hook into city supplies will sometimes need more active measures to filter their water as well.
I ran an enterprise help desk for a few years. I wasnt in the day to day, but would listen to calls sometimes. The reality is, dumb 5 year olds are often smarter.
We had a large (250k) workforce with a pretty wide variance in roles. We had probably about 100 people in the call center, although some of them did more interesting stuff too. It was a very good support organization with multichannel contact capabilities and really good, well paid staff.
Basically there was a barbell distribution with the lowest ranked people and highest ranked employees
being the worst. (Think attorneys and other special IC and middle managers. Executives had dedicated support and didn’t use this method.) The most expensive 20% of users make 80% of the calls. The high ranking ones were dumber to deal with and took more time, the low ranking ones called too often for dumb reasons but resolved quickly.
I cannot imagine the hell on earth the general public could be.
It absolutely is. I did some consulting work for an environment where they have to churn out code to meet certain unchanging schedules, usually you can dumb down the process to make it more deterministic.
These guys had to manage very complex calculation engine based on we’ll just let it changes every year had to be correct had to be delivered by a certain date every year.
They had an army (100-200 people depending on various factors) of marginally skilled coding drones that were able to turn out the Java, COBOL or whatever it was predictably on that schedule without necessarily understanding any of the big picture or have any having any hope of so. Basically a software factory. There was about a dozen people who actually understood everything.
Microsoft was always afraid of being IBM. They are more IBM than IBM.
When they started flying people in the beg that I buy 100 Surface Laptops, that was the confirmation of everything I had been thinking. All I could think of was IBM flying a dude from Italy in to talk for 15 minutes about their version of TeamViewer back in the day. We ended up talking about shoes.
Which is sad because the CEO's job is not to focus on the individual body parts but to make sure that the whole system is strong, beautiful, and healthy.
They can afford people who would do better. Windows 11 is trash. Azure is trash. Onedrive is trash. Outlook is trashier than it has ever been before, but it's not quite trash yet. Word is trash. Excel is rapidly enshittifying. Copilot is hot flaming radioactive tar cancer.
Does microslop even have a single thing left that isn't either completely terrible or worse than it used to be a mere 5 years ago?
Both. "New" outlook doesn't work with all of the add-ons and plug ins that "classic" outlook did. Both new and classic have copilot wedged into them. Classic has unasked for and unwanted Linkedin integrations that have to be turned off on a per-user basis, and it is patently clear that microslop has every intention of abandoning classic outlook the instant they believe that they can do so without severely alienating their userbase.
They really aren’t. They package benefits to try to hit different price points. Obamacare accelerated consolidation of providers and most regions have a cartel of 2-4 health networks.
The point of SOC2 is really demonstrate that you have controls. The other fake compliance areas are scarier for sure. You used to see really blatant issues — I recall early SaaS companies pitching to my enterprise with sales engineers showing me customer data.
Microsoft refused to provide diagrams to the Feds detailing how Azure works. They got the FedRAMP High stamp anyway, because they already sold it to half the Fed. That’s more real… as a situation where a Chinese hacker could compromise data in a dedicated “government cloud” by compromising a certificate in an onprem dev environment should be impossible… yet it happened.
reply