My experience is exactly the opposite. I don’t work for a FAANG but I’ve been around the block a bit. Its always the junior devs that try and add new warnings etc to the code base. I always require warnings to be cleaned up even if that means disabling specific instances (but not the whole rule) because the rule is flagging a false negative.
It boils down to desensitization/normalization. Warnings (and errors, of course, but tests as well) exist for a reason. If you don’t care about these gauge constructs are telling you, then they have no real diagnostic value. Getting into a place where you’re not looking at how your systems are actually running is generally a bad idea, especially in the long run.
I thought we decided FAANGM was better as FAGMAN.
“Pepsiman” started playing in my head, but instead of pepsiman it was f****tman
Removed by mod
Facebook is Meta, no one cares about Microsoft.
So the acronym is MANGA
and CI/CD goes “f*ck you, no deployment today, Linter is unhappy”
If you work for FAANG you’re morally bankrupt
I work at a FAANG company. I’ve also worked at startups and smaller national companies. They’re all morally bankrupt, just in many different ways.
Hell, I’ve worked for “tech for good” clients that have done reprehensible things that required legal intervention…
