There are a lot of excellent ex-FAANG programmers I've worked with, and a lot of terrible ones, and my experience is that usually the ones with the most prestigious titles show up, do 3 months of junior level work which we end up having to rip out later, and then leave to their next high-paying gig.
But the upside is that it’s a competitive advantage for startups that intentionally build different hiring pipelines.
I would say it is more of a fault of compensation structures.
Why would one stay for 3 years and get very meh comp increases every year, when they can switch to another company and instantly get a 30-40%+ increase (up to a point). It is also somewhat disheartening to see new hires get paid significantly more than you are for the same level.
i just don't understand this at all - why would someone who is working for you be a threat? They cannot take your job - it's not like them being a good programmer would somehow make them a good dev manager or "boss".
When this terrible thing was done, we immediately realized we needed to add validation. We had thought that by limiting who could call through access controls, we'd never have a malicious user. So naive.
Sadly, at that point we couldn't add it because his awful project was running in production.
No one suggests I am at fault if you break into my house and steal my stuff.
And arguably this principle holds for most team members in any organization - since it’s only very few at the very top that actually get held accountable for overall team success.
It's weird to have to say this, and some people probably think it's naive, but I stand by it.
Once my team owned a service that did X. Among it's functionality, it had an API that, as a side effect, stored some data that could be retrieved. Sadly, this service had no validation that the data being input made any sense in the context of what this service did.
A developer on a neighboring team had a big promo project on the go. As a simple hack, and as a way to save time, his project used our service as a basic key value store database. They already called this service for the correct functionality, so they had access keys. The stuff he was storing could be argued to kind of make sense, but as the owners of this service we said "no fucking way, we aren't your database". He escalated to management who knew he was going to quit if he didn't get his promo. They overruled and last I heard that service was still being used as that asshole's database. He did promise to fix it right after the project launched, but the second he had his promo he changed orgs.
For some reason, Amazon is full of this sort of terrible tech debt and they can't figure out why everyone has to be on terrible on call rotations.