Live data from Hacker News

Amazon Pip Horror Story

linkedin.com

81–90 of 771 posts

Re: Amazon Pip Horror Story

#82

As much as I feel sorry for this person and their experience, it seems to me this wasn't the best way to handle this situation. It would have been more pragmatic to fire up leetcode, take a few interviews, and leave the job professionally. This probably would have come with a small pay bump, even with this persons limited professional experience. Maybe I'm just lucky and I've never had a bad experience like this, but…

What are your thoughts about when the wives of the EA developers came together and sued EA? “Perhaps they should just be quiet”? When are the abused allowed to speak? Edit: nevermind. Comment history suggests I’ll never get a response.

I wasn't suggesting anyone should "just be quiet", in fact, I'm happy this person was able to express themselves and their situation openly on LinkedIn.

My point was simply this wasn't a very pragmatic approach to handling the situation. Some employers may not like to see this type of content on their professional profile and it may hurt their career.

Re: Amazon Pip Horror Story

#83

As much as I feel sorry for this person and their experience, it seems to me this wasn't the best way to handle this situation. It would have been more pragmatic to fire up leetcode, take a few interviews, and leave the job professionally. This probably would have come with a small pay bump, even with this persons limited professional experience. Maybe I'm just lucky and I've never had a bad experience like this, but…

100% agree. Everyone knows Amazon is toxic but I sure as hell wouldn't hire someone who posted this

Then you're contributing.

Re: Amazon Pip Horror Story

#84

Earlier quoted context omitted.

Performance improvement plan. Either a manager writes a plan of measurable goals focused on improving, or a manager and the target employee both work on the plan together. It can be used for actual performance improvement or it can be used as something the employee cannot meet as a way to fire them or get them to a different team.

You would be nuts to treat it as anything other than loading the bullet into the gun that terminates you. All it is is to make sure that the bullet is legal.

I don't get this. From what I've heard, in the US, you don't need an excuse to fire anyone. Why bother documenting an excuse then?

Re: Amazon Pip Horror Story

#85
Stories have two sides, someone on blind posted the following, and no one's challenged it so presumably it's true:

> The guy made 24 CRs in his entire career at amazon, all in just one CDK package.

> 50% of his CRs are merged without approval.

> So, yeah, there you go !

Re: Amazon Pip Horror Story

#86
post #44

Earlier quoted context omitted.

pip needs to be put on a PIP (although to be fair pip and the python package ecosystem has come a long way in the last few years)

Python needs to be put on PIP :)

It was fired in macOS 12.3, but you can bring it back as a contractor with the xcode installer.

Re: Amazon Pip Horror Story

#87

Yeah, vibes with my experience working there. Toxicity beyond pale. Good riddens, they contact me every week to try to get me back. Fuck off Amazon, you have no integrity, you abuse your employees from white collar to blue collar. You literally fired people who emailed Jeff Bezos to report abuses, after you told them to, when the NY Times "crying at desk" expose came out. Bezos instilled this shite culture into Amazo…

> Technologically, AWS is built like a fucking house of cards with spit, tape, and glue. There

Still making more money than GCP and Azure (both of which are worse to use, IMHO) so...who cares?

Re: Amazon Pip Horror Story

#88
post #44

Earlier quoted context omitted.

pip needs to be put on a PIP (although to be fair pip and the python package ecosystem has come a long way in the last few years)

Python needs to be put on PIP :)

Python might actually need to be sacked and blacklisted from the industry.

Re: Amazon Pip Horror Story

#89

Earlier quoted context omitted.

HR at Amazon is a shit show. I had $100 of pizza stolen from the fridge at Amazon and I mentioned it casually to HR, as something notable but not too important. And HR then decided to tell my manager without my knowledge. The manager then berated me over communicating about a "trivial matter." So yeah, wouldn't put much stock in HR at Amazon.

I know it's not the point, but how/why did you have $100 worth of pizza in the refrigerator? Edit: I'm trying to imagine scenarios where that could happen, I have two so far. You ordered pizza for a meeting that got canceled, and the office refrigerator was huge. Or you ordered from a fancy pizza place that had waygu or something as a topping. I'm sorry, I don't know why this is bothering me so much.

it's clearly a lie!

The value of pizza is inversely correlated to the time it's been out of the oven. Once it's in the refrigerator it's worth max 1%

Re: Amazon Pip Horror Story

#90
post #9

>I submited 51k lines of code in January that is well beyond real.

It’s not a useful metric. Starting a new project with lots of generated code will have thousands of lines of code & it won’t do anything useful.

It’s absolutely a useful metric. I have managed many developers who insist their low LOC is in no way indicative of their productivity. They’ll say others are padding their code with comments, or writing bloated inefficient code, or that they themselves were tackling very tough problems that result in small (but tricky) fixes. Yes, we’ve all encountered that killer deadlock or memory leak deep in the runtime that takes three weeks to debug and then it’s a 2-line fix. But some people pretend that’s how all their work is, when in reality they take a week to fix a css misalignment, or take a week to refactor some simple python script and add one new command-line argument, and they average 50 LOC or whatever.
Post reply on HN