Oh, 1000%. I could write a book on how monumentally stupid the whole process is (and most Amazonians agree), but the fundamental points are:
Most fundamentally of all...very few companies do this. It died with Jack Welch/GM and Gates/Microsoft, after they saw the same downfalls. Amazon is yet to learn their lesson, and it shows in how poorly the "Amazon Management School" under Bezos are performing. The other big tech companies also now do this, although less severe, and surprise surprise, they're all going downhill - making awful decisions, delivering nothing of value, and ignoring customers over leadership.
I hate to break it to you, but plenty of Amazon employees work weekends too, especially when big launch dates are coming up.
Source: Work in an org at Amazon where people have paged us regarding feature work on the weekend.
The best way to do this is to correlate downtime with main providers. If a cloud provider goes down when AWS has outages on related services, it's probably using an AWS service.
That's not a bad spread. Should probably add that it's back bacon, and not streaky bacon that the yanks eat.
Animal Well is stellar. If I were Dunkey I'd just give up now and call it a win over the games industry.
The point is that some VP probably pushed for the use of AI, and a director and senior manager chasing promotion decided to deliver it, despite there being no clear use for customers.
I'll die on this hill.
If you want an easy language for beginners, Ruby is a much better alternative. It's like a simpler Python, and aside from a crazy loop syntax teaches clean programming principles better than most languages.
With that said, Rails IS a ghetto, and many of the kinds of companies that use Ruby as their main language are stuck in the past or are full of the biggest toolbags you'll ever meet. DHH, in particular, built a reputation on being a programming contrarian, so much so that there's a golden rule where if he says something, the opposite is probably the correct choice.
They had some solid songs after this, but I kinda feel that this is where the downfall started to happen as they moved away from the angry, angry stuff and towards more of a rock sound.
While I'm all for this, the problem I see with high-density buildings is that it's easy to put them up, but it's hard to then build the services that this many people need. You can put an apartment block with hundreds of new residents, sure, but where are the doctors, the schools, the hospitals, the public transport routes, etc?
All very solvable problems, but one that high-density living often fails to cater for, because some rich developer cunt is happy to throw a high rise up and forget the rest.
True, paired with Amazon moving many roles out of North America and into India.
With that said, a lot of people (like myself) joined Amazon when remote working was encouraged, only to then be told to go in 3 days a week. We lost loads of really great engineers that didn't have opportunities in their local area. We'll likely lose a LOT of people again, myself included, unless opportunities open elsewhere where I can transfer to a new area. Amazon are tricky, though, and they'll preempt this by reducing transfers or laying people off soon to ensure that those that cannot adhere to 5 days a week are considered to have "resigned voluntarily".
That's all to say that a lot of bad faith on Amazon's part will likely scare people away from joining. After the NYT article dropped almost a decade ago, Amazon got around it being hard to hire by having great transfer opportunities and high salaries. Neither of those exist now, and with all the anti-worker rhetoric and lies about internal AI performance "saving x hours on upgrades" I don't see Amazon ever getting top talent again. Amazon will slip into boomer tech soon enough.
@EnderMB
@lemmy.world