Live data from Hacker News

Amazon Pip Horror Story

linkedin.com

101–110 of 771 posts

Re: Amazon Pip Horror Story

#102
post #77

Earlier quoted context omitted.

Never worked for AWS, but I'd imagine its different depending on division/team. Before starting a job once I had an ex-colleague warn me against the company, saying he had friends there and it was brutal (none in the team I was joining, but its a big company). Turned out to be the opposite for me, and in fact was far nicer than the company I worked for when I was working for him. Big companies are often far less cons…

It can even be different in the same team. It's about who wins the bully lottery just like in school. Some will go through school totally oblivious to the fact that some people gets so bullied that they decide to end their lives a few years down the road. Once I came in to work in the evening, I had forgotten to bring my phone with me. There I find one of my coworkers crying his heart out because the women treat him…

The women treat him like shit? What was he optimizing?

Re: Amazon Pip Horror Story

#103

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…

Guys, what do you think of a ratemyprofessors.com for bosses at companies? Optional anonymous reviews and to be fair and balanced the boss can respond to each review.

That way people can do what jiawei did but without the risk of professional self harm.

Re: Amazon Pip Horror Story

#104
post #45
post #21

How it started - https://i.imgur.com/7Cyia1U.jpeg How it is going - https://archive.fo/pdYHy#selection-525.105-525.423

That first post, is that the acceptance speech for a Nobel prize?

Are you not on Linkedin? This self-aggrandizing cringe is 95% of the content in the feed, I'm always amazed people can write this with a straight face.

Re: Amazon Pip Horror Story

#105

Earlier quoted context omitted.

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 tak…

[deleted]

Re: Amazon Pip Horror Story

#106
post #21

How it started - https://i.imgur.com/7Cyia1U.jpeg How it is going - https://archive.fo/pdYHy#selection-525.105-525.423

He's still just a youngin' with plenty of time to figure out what he did wrong. Everybody's gotta learn sometime.

Re: Amazon Pip Horror Story

#107

This is a phenomenon common to all low grade/incompetent dev managers: When a dev asks for a team change they view it as a slap in the face because it has happened to them so often in the past and they take it as a personal offence. The fact is they are lousy managers and usually incompetent and nobody wants to work in their team. So they go on the offensive and try to manage the dev out before senior management real…

Then senior management should be wondering why so many low performers are ending up with certain managers...

Re: Amazon Pip Horror Story

#108

(dare I ask what a dev plan (pip) is?) quick google check... Development plan is a regular plan which you do with your manager, where you are focusing on your career progress. You focus on your strengths and weaknesses. Based on this plan you will get tasks which will utilize skills you are good at and also help you to improve skills you want to have improved. PIP is a plan which is assigned to employees with unsatis…

It’s how you fire people in tech companies. You put them on a PiP, give them some tasks to do and then fire them when they don’t deliver. Obviously nobody survives the PiP because for an engineer not on a pip, taking 9 weeks on an 8 week project is pretty good, but on a pip 9 weeks for an 8 week project is a failure to deliver and you’re out. Obviously this is evil bullshit, but I’ve been in this industry for a very long time and this is what seems to happen.

Re: Amazon Pip Horror Story

#110

Earlier quoted context omitted.

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 tak…

[deleted]
Post reply on HN