riverfreak
macrumors 68000
When they laid off Clippy, they should have pulled his credentials.
They’re the king of mediocrityMicrosoft should investigate why it sucks so much.
I've worked with engineers who have 20+ years of experience and can barely turn on their freaking computer.I'm sure Senior Network Architect.. lets call him "Brad" who was spontaneously laid off last week after working in the Operations team at Microsoft for 14 years could've stopped a bad network change.
But no whippersnapper Cloud Network Engineer, with two years of experience "Tom" definitely never saw that coming.
Ya cause US-East-1 is soooooooooo reliable. AWS has just as many issues and outages as everyone else.
I'm sure Senior Network Architect.. lets call him "Brad" who was spontaneously laid off last week after working in the Operations team at Microsoft for 14 years could've stopped a bad network change.
But no whippersnapper Cloud Network Engineer, with two years of experience "Tom" definitely never saw that coming.
You can tell because productivity temporarily increased when teams actually goes down.I’m not sure I could tell a Teams outage from normality.
Microsoft Azure is completely borked which is what they build on top of, as do a lot of other people.
Again.
Thank goodness we're on AWS. It's not our day to go down today 🤣
Edit: I love the downvote on this because it's actually factual and reported in the tech community elsewhere as well 🤦🏻♂️
Azure also wasn’t as reliable as AWS in my experience, both in terms of service and in terms of their admin panel/console.Microsoft Azure is completely borked which is what they build on top of, as do a lot of other people.
Again.
Thank goodness we're on AWS. It's not our day to go down today 🤣
Edit: I love the downvote on this because it's actually factual and reported in the tech community elsewhere as well 🤦🏻♂️
But at least the new staff is more {} and willing to work for a pittance. /sI'm sure Senior Network Architect.. lets call him "Brad" who was spontaneously laid off last week after working in the Operations team at Microsoft for 14 years could've stopped a bad network change.
But no whippersnapper Cloud Network Engineer, with two years of experience "Tom" definitely never saw that coming.
Oh completely. But they’re both worse than our data centre infrastructure was and are more expensive. That’s the travesty.Azure also wasn’t as reliable as AWS in my experience, both in terms of service and in terms of their admin panel/console.
These days BGP has become the new DNS. It even works in the haiku.maccas.net
dayssince.itwasdns.net