Amazon Pip Horror Story
linkedin.com
Amazon Pip Horror Story
1–10 of 771 posts
Re: Amazon Pip Horror Story
#2Fuck you bezos!
Re: Amazon Pip Horror Story
#3I ended up switching teams and had a decent time at the company, but the nightmare situations are very real. You are replaceable and there’s no mercy
Re: Amazon Pip Horror Story
#4Principles are things like Integrity, Honesty, Respect -- not Amazon's fuckwit bulletpoints like "Be right a lot" or "Frugality."
Technologically, AWS is built like a fucking house of cards with spit, tape, and glue. There is no real cohesion or organization, just a bunch of teams doing their own practices and gluing their rando codebase into the Yellow Console. Sorry, but just making the frontend look unified doesn't undo what the backend spaghetti is... That's why the outages of late will continue. It's all bubbling up from the absolute toxicity in lack of basic humanism at the core.
Re: Amazon Pip Horror Story
#5 $ npm updateRe: Amazon Pip Horror Story
#6So they go on the offensive and try to manage the dev out before senior management realises that yet another dev doesn’t want to work with them.
Re: Amazon Pip Horror Story
#7Re: Amazon Pip Horror Story
#8Maybe his manager is a piece of shit, but I can't believe there's no one to report to above him that can see this for what it is and make it right?
Re: Amazon Pip Horror Story
#9that is well beyond real.
Re: Amazon Pip Horror Story
#10I’ve worked at Amazon. I made it a few years, but was almost pipped in the first few months. Management dropped a huge project on me, a brand new tier 1 service, with full dns resolution, api, database, distributed system, along with micro services. The deadline was three months. Brand new tech stack. When I was struggling to meet the deadline, we started having “performance conversations”. I ended up switching teams…
In the past, I thought of putting myself in positions like these to increase my understanding in short time, at the short term expense of personal life. I wonder if that's just a stupid thought that leads to nothing but burnout, or actually a viable short-term strategy to get up to speed with some of the tech stack you know but haven't really used in prod at the scale of Amazon.
Nowadays, I have health issues (go figure) so it's off the table and all I can do is wonder :).