Live data from Hacker News

Amazon Pip Horror Story

linkedin.com

301–310 of 771 posts

Re: Amazon Pip Horror Story

#301

The pip quota is a HUGE perverse incentive here. Choosing someone to put on pip is hard because it is in manager's best interest to protect their core team from pip. So if someone is too good for your team, you put them on pip. They are going to leave anyway, so putting them on pip does the least damage to your team. The other pathological result is hiring dummies just to put them on pip, again protecting the core te…

This was the way for Microsoft in the late 90's. Hire to fire.

Re: Amazon Pip Horror Story

#302
post #268

Earlier quoted context omitted.

This is my personal experience, which is why I'd advise people not to go through with the above thought experiment. Then again, I keep interviewing people with 5-10 years of experience, who will go something like this: > How would you manage a server? (leaving out a ton of context about what it means to "manage a server") > Very easy, SSH connection is very fast, reliable, ... > Awesome, love me some SSH, how about 5…

> Even with 500 servers? Not sure what answer you expect here? Just because you have 10 years of experience doesn’t mean you’ve ever worked with more than 25 servers at a time (at least I haven’t). I consider it a source of pride, I think. You absolutely don’t need mega scale for most things (or maybe mega scale, but still not many servers)

[deleted]

Re: Amazon Pip Horror Story

#303
post #232

Earlier quoted context omitted.

I'm convinced human beings are naturally designed to operate at 120% for 6-12 week long periods. \ Hunter gatherer survivalist genes just kick in. YMMV, but I consider it a healthy thing for, at least for some part of your career, to work "Amazon hard." Aka, all the reasons that people list when they say you should really try working for a startup. When you push yourself to your limits at your profession, a lot of st…

It is stupid to work that hard on making a rich asshole even richer.

That's just a side effect, not the reason to do it.

Re: Amazon Pip Horror Story

#305

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 !

> no one's challenged it so presumably it's true Amazon is well known for training employees to defend the company on-line. Aren't you being too generous with an anonymous comment that you provide no link to? Is not possible that is just Amazon propaganda?

Let's assume that it's 100% true. This guy is young and it'd be better for him to delete this. I'm totally going to cyberstalk this guy to see where he goes.

My number one rule is not to sh*t on former companies with my main account.

Re: Amazon Pip Horror Story

#306
Somewhat controversial opinion but from my experience most people at Amazon who got pipped deserve it.

Especially with new grads, they've lowered the bar and stopped doing interviews since it's so hard to hire, that there's a lot of people not cut out for the job so they rely on pip to calibrate quality.

Re: Amazon Pip Horror Story

#307
post #267

Earlier quoted context omitted.

You can care about your career and your self improvement while still maintaining healthy boundaries around the mental effort expended for your job. We’re in it for a long time but jobs come and go

That's not what I'm talking about. Your working life is where you act on the world outside of yourself. If you don't care about what you're doing, you're spending most of your influence on the world on something you don't care about.

Why not? You can care about delivering beautiful code. You can care about ensuring the workplace is a pleasant place to work for all. You can care about your relationships you’re building. You may even be a huge fan of the product you’re building. That doesn’t mean you need to shit a brick when someone comes running in with their hair on fire—it’s not a binary proposition. Caring about things can be done “a la carte” and you can simply just not care about the bullshit

Re: Amazon Pip Horror Story

#308
post #101

Earlier quoted context omitted.

As an Indian, I am starting to notice a pattern of terrible Indian managers from all the stories I hear from my friends. I really hope that these stories make up a biased sample.

I'm from China, I've had only good experiences with Indians. Most of the people I would deem as ass hole level on the scale of Ganesh were in fact white. It would be idealistic to think that all races have an equal portion of ass holes though. I will say that a large portion of SDM's are Indian so your sample is indeed biased.

One reason might be that Indian managers are sometimes ass holes to Indian subordinates in particular, maybe because they are aware that Indians are stuck in perpetual H1B status so they can be abused.

Re: Amazon Pip Horror Story

#310

Earlier quoted context omitted.

50 LOC is industry average. See my earlier comment at https://news.ycombinator.com/item?id=29246318 for a list of citations. One was: > slide 20 of https://www.slideshare.net/ddskier/calculating-the-cost-of-m... ("A world-class developer (e.g. Facebook or Google senior engineer) will write 50 LOC per day") I also found some two scholarly estimates, one at 81 LOC/day and the other at 16 SLOC. On this topic, don't forg…

> 50 LOC is industry average Sorry, I wasn't clear. I'm talking about 50 LOC every 2 weeks or so. Like, seriously low LOC of seriously low-complexity (sometimes trivial) code. I don't actually have a numerical target people should hit. Not at all. It's more like this: on several occasions now (all too common), I've taken over management of a team, and in our initial team meetings and 1:1s, some developer talks about…

LOC isn't a meaningful metric. Flat out. You can think it is, but it's such a toxic, nonsensical concept that you deserve to get pushback for mentioning it. It's a waste of time in the presence of actually useful criteria product/project-related metrics.

Teams of people build things. LOC don't add up to a hill of beans.

Post reply on HN