In my experience it’s the other way around.
Both sides.
I constantly call out juniors who do things like ignore warnings, completely unaware that the warning is going to cause serious tech debt in a few months.
But Ive also unfortunately shrugged after seeing hundreds of warnings because to update this requires me to go through 3 layers of departments and we’re still waiting on these six other blockers.
Pick and choose I guess.
I thought we decided FAANGM was better as FAGMAN.
“Pepsiman” started playing in my head, but instead of pepsiman it was f****tman
It was the Batman theme for me. Na nanana na na… fagmaaaaannnn
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…
But financially bussin’!
And also, it’s actually a complicated question. A one-man boycott doesn’t do anything. If you work at a FAANG, work for a better world when you’re off, and go whistleblower when they do something really evil, I find no fault in that at all.
*If you’re in the US.
Some interns in the US make more than experienced engineers in Europe…
I was kind of assuming that, since FAANG are American, but I’d guess they probably have foreign employees as well.
Canadians make pretty much the same as Europeans, I think. The Americans have a bunch of monopolies, and are characteristically weird and nationalist about who they share the spoils with. (I know, it’s not all of you guys, but it’s definitely some)
they also pay 3000$/mo for a moldy apartment
Yeah, that’s true. It amazes me how some of my team in NYC will make double what I make, but live like I lived when I was a student, and be amazed that I own a car.
You could say the same about eating meat or any other cause. What’s the difference, the animal is already dead anyway, right? Well, it’s not that simple.
Thanks to the growing number of people who eat less or no meat at all, meat production is decreasing. If all of them kept saying that one man boycott makes no difference, the change would not come.
If you can’t find a better job - fine, work for the evil FAANG or whatever. We live in capitalism and it’s clear we need to work somewhere. But at least be honest and don’t look away from inconvenient truth. There’s still something good you could do while keeping the job at
$evil_company. For example, you can support financially those who haven’t got nice jobs in IT.Yeah, I do worry someone will read the “work for a FAANG” part, and ignore the other two things listed. It’s absolutely not enough to go “welp, I’m just a little cog following orders”.
Maybe a one-man boycott is the wrong way to put it. Multi-person boycotts are obviously built from individual people. I guess my real point is that there’s not a one-size-fits-all solution; you actually have to look at the world, look at how you want it to be, and figure out how you can help make that happen from your place in it.
I’m not ignoring the other two things listed, I’m realistic.
You described it like it was something rare for FAANG to do bad things. Or like it was bad only when it required whistleblowing… Think how many things got crushed by EEE tactics, and it’s only one class of examples of why big tech is inherently bad.
I mean, a lot of companies do stuff like that, and yet you still need money to live. Just working there doesn’t necessarily make it your fault; by that logic it would be a sin to work checkout at Walmart, because you’ll have the same blood on your hands as the Waltons.
I don’t really like talking about capitalism as if it’s a well defined concept, but, no ethical consumption under.
I’m not ignoring the other two things listed, I’m realistic.
I didn’t mean you, FYI. I mean someone who does work for a FAANG and is looking for more justification to do nothing for the common good.
Giving up your morals for money is morally bankrupt
Agreed. Just working for somebody bad doesn’t necessarily mean you’ve given up, though. I mean, they made a movie about Schindler, and we all know who he worked for.
Sure but an employee for FAANG and an undercover antifascist aren’t really comparable
Why not? Unlike Schindler you don’t have to worry about how many beatings are necessary to keep up appearances, and you might have a specific role that exposes you to very little evil at all. Meanwhile, you can donate some of that big wage to people like EFF, or volunteer using the flexible schedule.
The other consideration is that pretty much every company you could work for as a software developer is going to try to take advantage of your work. Most companies are morally bad at best and morally terrible at worst. If you discourage any good person from working there, the problem will only snowball from there.
If working at FAANG gives you the resources to support things you’re passionate about, and you’re willing to stand up for your values when they do something bad, there isn’t a problem with that IMO.
You can work in bioinformatics, the pay is lower than FAANG, but your code will benefit society.
Benefit society, or go to support a pharmaceutical company that will in some way benefit society in exchange for making a few people rich?
No ethical
consumptionworking conditions under capitalism.Bioinformatics isn’t used only for medical research or within big companies. Sub-topics like metagenomics, that are helpful in many areas of research, require high level of technical knowledge, that the life science people don’t have.
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.
the rule is flagging a false negative
false positive?
Warnings and errors are negatives not positive. So if it generates a warning that is OK, it’s a false negative.
Just so you know, if your doctor calls and tells you that your HIV test is positive, you probably shouldn’t run out and celebrate.
That’s why I said false negative. The medical test is testing for the presence of a disease. So if they find the disease is considered a positive test (it found what it was looking for). For static analysis on code, its the opposite. Its testing if your code is free of issues that it can detect. If it finds no issues, then the test was positive. If does find issues, the test failed and each issue is a negative that contributed to the test failing.
I’m not debating. It is not a matter of opinion. I’m doing you the courtesy of informing you how the entire rest of the world uses the term.
If action A looks for thing X, and it finds thing X, then the test is positive. If action A fails to find thing X, then the test is negative.
If action A claims to find thing X, but later confirmation determines that thing X is not really there, then this situation is called “false positive”.
If action A claims fails to find thing X, but later confirmation determines that thing X is actually there, then this situation is called “false negative”.
That thing X may subjectively be considered an unwanted outcome has **nothing ** to do with the terms used.
You could say “A static analysis tool is testing for the for the presence of defects” or “a medical test is testing if your body is free of diseases that it can detect” to change how you’re looking at either of the tests in the previous comment.
By your logic it would be a positive for your code to have errors/warnings. And on the latter, that would appropriate if there was a test that determined if you are free from all known diseases (or at least those that it can detect).
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.
