Live data from Hacker News

Google Engineering Management Mistakes

docs.google.com

101–110 of 136 posts

Re: Google Engineering Management Mistakes

#101

There is no perfect review and compensation scheme. People will figure out how to game the system. Perhaps the best scheme is to randomly change it every few years so people can't game the system permanently.

I've often thought about that. I think it would be a worthwhile experiment.

Re: Google Engineering Management Mistakes

#102
post #39

This is great, but I think EVERY tech company struggles with finding the right balance here. Where I currently work, they also fail each and every one of these.

That's not true. I think the traditional management systems do a good job of not setting bad incentives for tech leads.

Re: Google Engineering Management Mistakes

#103
post #100
post #94

Earlier quoted context omitted.

Sorry, the slide deck was there as a presentation to Facebook's VP of engineering. I wasn't about to transcribe my own talk.

Like I said, I appreciate that you took the time. I was just being J. Random Internet Asshole. (But I really do hate slide decks.)

The slide deck was part of a blog post. It's not my fault that news.ycombinator.com only linked to the slide deck and did not provide context: http://piaw.blogspot.com/2010/10/facebook-and-google.html

Re: Google Engineering Management Mistakes

#104

"Stack ranking system was harmful:" whoa! I didn't know Google practiced stack ranking. There is a lot of unnecessary stress generated at Microsoft due to this[1]. I would have thought the Google folks would be wise enough to avoid it. As for ".... SVP response: “If you wanted to get promoted for these non-engineering tasks, move into management" heh! How big company ish is that? The best way to join Google these day…

The massages aren't free. They're subsidized at $20/hour.

Re: Google Engineering Management Mistakes

#105
post #103
post #100

Earlier quoted context omitted.

Like I said, I appreciate that you took the time. I was just being J. Random Internet Asshole. (But I really do hate slide decks.)

The slide deck was part of a blog post. It's not my fault that news.ycombinator.com only linked to the slide deck and did not provide context: http://piaw.blogspot.com/2010/10/facebook-and-google.html

Very true, and the added context is really helpful. Thanks for responding civilly to my not-very-civil bitchery.

Re: Google Engineering Management Mistakes

#106

He says offhand that Google is a better place for engineers to work than Apple, but as far as I can tell, Apple makes none of these five mistakes.

I know several Apple and ex-Apple engineers. Let's just say that the environment isn't even comparable. Google wins hands down. One of my friends at Apple had to file for an information request so that she could debug a problem that spanned multiple layers of abstraction. A Google engineer faced with that kind of inanity would just quit.

Re: Google Engineering Management Mistakes

#107

He says offhand that Google is a better place for engineers to work than Apple, but as far as I can tell, Apple makes none of these five mistakes.

Certainly over the course of Apple's decades they've made many managing mistakes and it would be trivial for an insider to make a list of any five of them, without ordering of "the top five" or anything like this.

It's impossible to be around for so long and to employ many people and not make any mistakes. No company is perfect. Coming away from this presentation thinking "pffft Company X is so much better because they don't do this" is a huge mistake - if you aren't making mistakes, you aren't trying.

Re: Google Engineering Management Mistakes

#109

Any large company is going to have those same mistakes. There is really no way around it. Especially the part about only the big sexy project got recognition and not the little grungy tasks. In a company of 20,000, unless you have a 1:5 manager to employee ration at all levels you can't avoid that. If these are Google's biggest mistakes then I would happily go to work for them.

I think that it is possible to build a culture where the grunchy unsexy work becomes much less un-thanked. Microsoft at its best did it: Raymond Chen was much celebrated for his heroic efforts at preserving backwards compatibility in Windows. In fact, when the Raymond Chen camp lost its political battle, Microsoft got Windows Vista, which arguably cost it billions. I think the stakes are very high in exactly this sort of political battle, and it is worth while for top engineers to spend their time fighting for precisely this sort of culture shift.

Re: Google Engineering Management Mistakes

#110
post #55

biggest mistake is still having a "tech ladder" What does that mean - there there shouldn't be an engineering career track, the only promotions are into management? (To avoid conflict of team leads being evaluated as individual contributors)

See the contextual blog post above and below this comment.
Post reply on HN