Live data from Hacker News

Steve's Google Platform rant

plus.google.com

281–290 of 418 posts

Re: Steve's Google Platform rant

#282
post #170

It now 404's so I've posted it here: Stevey's Google Platforms Rant I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one.…

Although the etiquette of posting it here is debatable this post is gold, it is not (totally) an ordinary disgruntled coder rant. It's worth reading even for the small list of problems that he gives that Amazon faced when trying to go to an all-services architecture. But if I had to summarize the main point, I would choose: "The Golden Rule of Platforms, "Eat Your Own Dogfood", can be rephrased as "Start with a Platf…

But ... in the one case we are aware of, of a whole company, Amazon, using a service oriented architecture, they did it after the fact. The did bolt it on later, or rather, they (according to Steve) ripped everything up and re-did it in this way. I'm sure it was absolute hell to do this, but that is what they apparently did. So it isn't a requirement to build a platform first, then build everything else. It might be nicer to do it that way, if it's the best prioritization of resources at the time, but that's not what happened in the case being discussed.

Re: Steve's Google Platform rant

#283
post #170

It now 404's so I've posted it here: Stevey's Google Platforms Rant I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one.…

Although the etiquette of posting it here is debatable this post is gold, it is not (totally) an ordinary disgruntled coder rant. It's worth reading even for the small list of problems that he gives that Amazon faced when trying to go to an all-services architecture. But if I had to summarize the main point, I would choose: "The Golden Rule of Platforms, "Eat Your Own Dogfood", can be rephrased as "Start with a Platf…

I would call that very dangerous and very likely a premature optimization. Nobody cares you are a platform until they use your product, and if you spend all your time building a platform, there will be no product to use.

The path requires far more finese than "always create a platform". You need to balance over-engineering with the ability to re-evaluate previous decisions.

I agree Google has wandered far off this path, but imnot sure they are on any more well defined path than Yahoo. They just happen to be earlier.

Re: Steve's Google Platform rant

#284
post #7

I worked at Amazon from before Steve left to sometime later. I remember being excited when Larry Tessler was hired, and dismayed at the way he was treated. Everything Steve says about Amazon is true, only, it was much worse. Amazon was, by far, the worst employment experience I've ever had. I'm not saying that lightly, I worked for a dozen startups, a couple of which crashed hard in the most gut wrenchingly painful w…

So why does anyone good work at Amazon? And if the only people left at amazon are most crappy people willing to take the abuse, how can they build such a thriving company?

They actually do pay shitload of money to senior and especially principal people, mostly in the form of stock grants. They have really strange vesting schedule too: something like 5% first year, 5% second, 45% third, 45% fourth. To compensate for the dropped income they give you sign-up bonus for first and second years.

I left before my first vest as soon as interesting start up showed up (start up didn't survive, but at least it was fun).

Re: Steve's Google Platform rant

#285

Earlier quoted context omitted.

Europe and Australia have forever ruined me with their standard 4 weeks of vacation time. I can't fathom ever going back to anything less.

Six weeks here in Denmark and a maximum work week of 37 hours. You have to wonder how we ever get anything done here...

When we talk about vacation weeks, we mean sets of 5 working days, not 7. Right?

So e.g. 2 week vacation == 10 work days off.

Re: Steve's Google Platform rant

#286
post #7

I worked at Amazon from before Steve left to sometime later. I remember being excited when Larry Tessler was hired, and dismayed at the way he was treated. Everything Steve says about Amazon is true, only, it was much worse. Amazon was, by far, the worst employment experience I've ever had. I'm not saying that lightly, I worked for a dozen startups, a couple of which crashed hard in the most gut wrenchingly painful w…

Interestingly, 3 times in the last 2 days, I've had the amazon.com website give me a 404 on a link on one of their pages. I don't remember ever getting a 404 on their site. In all the years I've been using them, which is a long time.

Your rant paints a bleak picture, and I hope my experience of the last 2 days was coincidence.

Re: Steve's Google Platform rant

#287
post #46
post #27

Earlier quoted context omitted.

> of course, and I had to do it- RIGHT THAT MINUTE- in the middle of the night. There is your problem right there. Why in your sane mind would you even consider fixing it at that moment? You should have told them to FUCK OFF - right at that minute - and gone back to sleep. Right there and then a loud and sound go fuck a rake and fuck off.

You're absolutely right. It would have meant I lost my job. When Bezos is posting on a ticket, everyone knows it. All the pressure rolled downhill right onto me. This means that, even if I did tell them to fuck off, I wouldn't have been able to get back to sleep. On some level I would have felt I was shirking my duties, and after all, I'd lobbied hard to get it fixed, months before. I think, ultimately, it is kind of…

Saying "No" to my boss on a significant issue that got me fired was the most important thing I have ever done in my life.

Re: Steve's Google Platform rant

#288
post #249

Earlier quoted context omitted.

I did multiple internships at Amazon and now I work here full-time. I love it here. But, like other people have pointed out, your experience can be very dependent on which team you join. Personally, I wouldn't want to work full-time on the team that I did my first internship on. The work there just wasn't fun. But my internships put me in a good position to know which teams suck and which teams are great, and so I ch…

My AWS team was good. I enjoyed my work as an intern. However I was warned that work in the group is operations intensive. I could see that myself in those 12 weeks. As an intern I was not given any operations work. Obviously it will change when I join as a full timer. As noted below I am looking at other AWS teams, Kindle silk browser team. I need to find out about these teams.

Yeah, I've heard that some AWS teams can have heavy operational load. If it's important to you to avoid that, you could consider somewhere in WAP/BuilderTools. That's where I work (so yes I am biased), and in my experience the operational load tends to be pretty light throughout the org. On my particular team we almost never get paged. Plus we get to build neat things in this org (remember how Stevey mentioned that Amazon's "versioned-library" system is good?).

Silk is probably a neat team to look into as well. They're building a cool product, they're still a small team, and they have good leadership. The director in charge of it used to be the head of Builder Tools and he's great.

But yeah, talk to a lot of teams and ask them about the things that are important to you (operational load, current/future projects, code quality standards, whatever other things you can think of to ask) and see if any of those teams sound cool to you. I won't lie and say that every place in Amazon is perfect, but if you choose well I think it's possible to find a great team to work on.

Re: Steve's Google Platform rant

#289
post #277
post #255

Earlier quoted context omitted.

That's very normal in the US.

If I recall correctly, the US is the only developed country without mandatory minium paid employment leave (federal employees excepted). Which small-government fans might accept readily, but it also has amongst the lowest actual average vacation times… Apparently free citizens want to work. (One statistic had the Canadian average lower, though) Strangely enough, this doesn't seem to have a straight-forward correlatio…

Italian office hours are something like 8-12 and 2-8 or so. The (official) workday is much longer there,with a nice break in the middle.

Re: Steve's Google Platform rant

#290
post #55

Earlier quoted context omitted.

Yes, that's kind of interesting, isn't it? If those horror stories are true (and we have no reason to doubt they are), it kinda shows that the way you treat your employees doesn't really matter to your success. It certainly matters a lot to them; it matters from a moral point of view; but from a practical point of view the only individuals whose happiness matters are the customers. Of course, if your employees are so…

On the contrary, the way Amazon treats their employees does harm them substantially, they just haven't paid the price visibly to the public (or quite as hard as they will, eventually). Attrition at Amazon is at horrific rates. I know the actual number, though I'm pretty sure that'd violate my NDA to reveal. It's high. It's really high. Guess a really truly terrible number. It's probably higher than that. The stream o…

Considering that I've seen that in a prior bad job myself, and the correlation between that and "bad work environment," I'd say that shitty computers for a developer is a classic red flag.

In my book, it means that bean counting has taken over productivity. That's no place to be a software developer.

Post reply on HN