Live data from Hacker News

Why I Quit Google to Work for Myself

mtlynch.io

641–650 of 783 posts

Re: Why I Quit Google to Work for Myself

#641
post #116

Earlier quoted context omitted.

In my experience this often just becomes a popularity contest/give to whoever you eat lunch with. I can have my head down all week neck deep in code but because of this I'm not interacting with people around me as much and basically get punished for focusing on work.

Yes. You can't change people. Your actual job description is worth 20% or less of your workplace success; as long as you're doing enough to stave off disaster, you are pretty much fine. There is a simple metric for workplace success: if most people are happier while you're around (including and especially anyone above you in the chain of command), you're winning; if not, you're not. This can probably be summarized as…

> I have a theory that the more a person cares for niceties, appearances, and superficialities, the more it shows that they're incapable of operating at a level any deeper than that

The third category, of whom I’ve known several, is “capacity/competence, with an attention to the superficialities because they know how much those matter.”

That is, I haven’t found it to be an inverse relationship. I find it to be a 2x2, and if you happen to be someone with less capability and more ability to BS, then yes, you lean on your strength to obfuscate your weakness. But you can also be strong in both, or weak in both.

I also think there are a lot of jobs where deep mastery doesn’t generally exist (eg, mopping), and so those people just have no idea what deep competency discussions are like. It’s like flatland, only the third dimension is expertise and complexity.

Re: Why I Quit Google to Work for Myself

#642
post #556

Earlier quoted context omitted.

And if you think there's no political games in your company then you're very naive. Your either not seeing it (which is bad for you) or its being hidden from you (which is also bad).

Why do you believe there MUST be a political game?

Politics is how people organise and group. There are always ploys for control and expansion. Politics is practically biology, there is a pecking order and it is inescapable. What determines in and out group varies but it is always there if there are three or more people present.

Re: Why I Quit Google to Work for Myself

#643

Earlier quoted context omitted.

Yes that's true, which is why I said "why not both?" The manager should do more, but so should the employee. Sitting there and saying "I'm blocked, woe is me" is garbage compared to saying "I'm blocked. Can you please help me Mr/Ms XYZ?"

I think your specification of a "correct way to report a problem" is company specific, or your personal preference, or the way that you think an ideal problem report would be stated. We're humans. Unless there's been a training day or a Readme file explaining HOW to report a bug, I think it's perfectly reasonable to expect this protocol to work: "I'm blocked!" "Why?" "{reason}" If nobody ACKs the "I'm blocked" messag…

"I'm blocked because on compile I get such-and-such error message and I don't know how to fix it. Who is the right person to ask about this?"

I just cut your protocol complexity by half. ;-)

Re: Why I Quit Google to Work for Myself

#644
post #600

Earlier quoted context omitted.

relatedly, a friend of mine worked at a place where everyone was on "20% time = bug time". You were expected to spend ~ 20% of your time taking bugs from the bug tracker and fixing them. Bugs closed were part of a metric towards bonuses. People were taking one bug, breaking it in to 3 or 4, then closing all of those. "Add button for X" became * "add button on form" * "add CSS for button" * "update CSS for button" * "…

It sounds like you need a 'reasonable person' clause - when considering bonuses, each metric gets looked at by a randomly selected group of peers and they can jointly decide if someone's gaming the system. To take a narrower view, it sounds like that place needed to assign weights to the different bugs, so that the big scary bug was worth 20x (or whatever) of the trivial 'tweak the CSS' bugs.

The simple solution is that grooming is done as a team, so everyone agrees on "size" before tickets get assigned or picked up.

Re: Why I Quit Google to Work for Myself

#645
Hate to be the guy who says matter of fact things so matter of factly, but the author just stated that when he was programming he was happy and when he was calculating how to exceed at the game, he almost got promoted, but wasn't happy.

When he was only focusing on the metrics, he was ignoring everything else. That is unethical. That is calculated. That is unreal. That is the yellow brick road to unhappiness and a horrible career.

The main problem was the constant reorg. He couldn't get a project done with completion.

Re: Why I Quit Google to Work for Myself

#646

To author: you lost the political game. I busted my ass at a startup for years and also lost the political game. So I'm speaking from experience here. You can either get all mad and worked up and pissed off about it, and waste years of your career (as I did) being pissed off, stubborn, and refusing to change. Or figure out how to play. I'd like to think there are places with better politics but I think it's pretty en…

[Manager here] I don't really see what the political game is here that he lost. What I think he failed to do was show impact in a clear a visible way. Don't get me wrong, there is salesmanship required here in terms of clearly demonstrating your value, but it's not like Google was giving the promo to some other guys who always went out to dinner with his boss and sucked up to him, or the guy the boss went to college…

As an engineer my job is to engineer.

As a manager it's your job to figure out what my impact is.

If you make it my job to show what my impact is I (and everyone else you are responsible for) will simply spend my time coming up with ever more creative ways of doing this instead of engineering.

But hey, maybe I'm being silly and your company has no problems finding competent engineers, all your projects ship on time and under budget etc. etc. etc.

Re: Why I Quit Google to Work for Myself

#647
post #577

Earlier quoted context omitted.

And even if everyone completely ignored them when they direct messaged their teammates... why do nothing. Why not dig in and figure out how to get it to build and update the Readme? I don't understand why someone would just sit there and do nothing instead of trying to fix the problem.

I did that once and then rewrote the repo. Everything was fine for months on our team until another team merged their exact copy with new changes that broke what I was doing. Everyone senior left my team and it looked like I was doing nothing for 4 months. Communication should come first and the manager needs to step up.

I agree that communications is important and was the primary thing wrong here. It was more that even on top of that, they just sat there doing nothing vs. at least trying to be productive and figure it out for themselves.

And didn't you have backups of that repo?

Re: Why I Quit Google to Work for Myself

#648

Earlier quoted context omitted.

What makes my stomach turn is the interpersonal aspect. How can all your teammates see you fail through no fault of your own for days and pretend they don't notice. Unfortunately in my experience, that's not a rare occurrence.

I can give some insight from my own experience. In my current position, there are a large number of "things" that I've had to figure out, either by reverse engineering, reading code, or intuition. So I get constantly bombarded with helping others get unstuck. Well, when it comes time for a project meeting, those on the meeting are far removed from the other groups that I constantly have to help out. And it sounds lik…

For your own sake, I'd spend less time working and more time figuring out the emotional driver behind why you work so much.

Re: Why I Quit Google to Work for Myself

#649
post #279

Earlier quoted context omitted.

I think the author said it in the article: Optimize for promotion. Work from day 1 to game the metrics. If it helps your metrics, do it, if it doesn't approach with caution. If you start that from day 1 you'd be 2 years ahead of the author. Honestly, it sounds like a really shitty way to live. I personally prefer doing great work and having faith that it will work out. It has, a lot slower than that, but I'm proud of…

There's another position that's similar but less gross, which is to have some humility about what you think is important vs. what work your manager/manager's manager think is important. Try to work on what they think is important not (just) because of a cynical desire to game the system and get ahead, but because they have probably more experience and (often a lot more) context than you do. Of course, this only works…

But the author's manager gave him very high ratings.

Re: Why I Quit Google to Work for Myself

#650
post #575

Earlier quoted context omitted.

> What I found most off putting, was when meeting my skip-manager (your managers manager) for the first time during my exit interview, all doors for a senior level promotion were suddenly open, to incentivise me to stay. Doesn't feel great when negotiations with your employer are comparable to those had with your cable provider. Wow, that's one hell of a way to look at things. Thanks for that perspective.

Yeah that’s a great way to phrase it. I always got frustrated with counter-offers upon resignation, as it’s the most vivid “yeah we could definitely have paid you this because you’re worth it, but only if we know you’re really mad”

On the other hand isn't it also a face saving out allowing you stay? - I'm sure many people quit without being 100% sure :)
Post reply on HN