Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

triplebyte.com

Post reply on HN
Print view View original

141–150 of 351 posts

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#141

Post by cbzoiav »

bleair wrote: post #63
itronitron wrote: post #7

> Great engineers understand computers all the way from the silicon up through the different layers and protocols and systems. I find this a bit limiting, certainly they should think across multiple layers but some of those layers exist beyond the systems.

As a people style thing I’ve encountered two broad types of engineers - the intuitive types, and the detail types. Neither type is wrong but it’s a different set of desires and interests. The detail type wants to ponder every corner case and every possible use (that the specific engineer cares about). The intuitive type can find this infuriating. They’d rather just build it and learn as they go. They have aesthetic t…

I think I fit both of those. When I start working with something I just want to throw something together and get it working learning as i go. I believe you never fully understand what you need to build until you've tried it.

But then I like to step back, read up on the underlying components and rebuild from scratch making sure i understand every possible flow.

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#142

Post by daylightyotei »

> If you're thinking about joining a startup, how do you tell if the founders are like Larry and Sergey or if they're an Elizabeth Holmes? Right, that's the worst combination: smart and full of st. I think you have to interview them a little bit. Ask hard questions and see if they give direct, insightful answers, or if they're evasive and dismissive.

What are some examples of "hard questions" that we can ask?

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#143

Post by wpietri »

bootsz wrote: post #102

> I didn't have to work that hard, and one day I had this realization while sitting in my gray cubicle (I was in a sea of gray cubicles surrounded by gray walls, listening to white noise and all alone): I'm like, “Man I am so tired. I need to go home and take a nap.” I went home, but as soon as I got there I realized, “I'm not tired anymore.” Is there a name for this type of fatigue (or perception thereof)? I'm curio…

> Is there a name for this type of fatigue (or perception thereof)?

I think of it as lack of motivation combined with low-grade frustration from not being allowed to shift to something worthwhile. Paul Buchheit is obviously a self-winding guy. But put him in a context where he's expected to do things he doesn't care about and is forbidden to do things he does care about and all the air goes out of him. That's certainly what it's like for me.

Companies should learn a lesson from this. When I'm managing I work hard to build close-knit, cross-functional teams that score well on Pink's Autonomy/Mastery/Purpose triad. Purpose is the foundation: you have to give the team something meaningful to do and then connect them to that meaning. Autonomy comes next: you give them broad long-term goals and near-term milestones and turn them loose. They should always feel independent but accountable. Mastery comes from letting them meet and overcome challenges, learning as they go, but it doesn't hurt to support them by providing them coaching, access to experts, and any training they ask for.

Buchheit is clearly exceptional, but I think everybody benefits from environments that support his approach to the world. Every child is curious and exploratory. Many have that beaten out of them by industrial-model education and top-down corporate workplaces. But I don't think it's ever truly gone, and I think businesses really benefit if they deeply engage their staff.

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#144

Post by crdoconnor »

matwood wrote: post #133
crdoconnor wrote: post #95

Earlier quoted context omitted.

>It’s a mistake, and will set you back to think of politics as a zero-sum game. It's a mistake to think that it's not a zero sum game. If there are 5 people and one available spot for promotion, you can get selected by bolstering your appearance or by tearing the other 4 down. Either one works. And yeah, the best tactic is usually "make my boss look good".

> And yeah, the best tactic is usually "make my boss look good". You say this like it's a bad thing. You should be making your boss, your team, and your teammates look good. If you are doing those things, you are probably also making the company look good. It's thinking about the long vs. short term. Focusing only on your own optics may work okay in the short term, but they cap out fairly quickly. Think about how it…

And just like that, the just world fallacy kicks in :)

I certainly don't think it's a bad thing to make your teammates look good, but in general it's more effective to give the lion's share of the credit to the boss rather than them. And credit is a limited resource.

I say that like it's a bad thing because it kind of is.

I believe there are some companies where coworkers rather than management decide promotions and this tactic would not work but they are few and far between.

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#145

Post by vonmoltke »

Sytten wrote: post #120

[Off topic] Can someone help me understand why computer scientists call themselves engineers in the US? Is there a reason beside the fact that it is probably not regulated? Here that would be so totally illegal if you are not a member of the order which requires an engineering diploma.

> Can someone help me understand why computer scientists call themselves engineers in the US?

Someone with a Bachelors (or less) who builds systems by writing code is not a computer scientist. That is a less appropriate title than engineer.

> Here that would be so totally illegal if you are not a member of the order which requires an engineering diploma.

Yes, we know Canada is almost uniquely psychotic about this. I, personally, think it is ridiculous, and I state this as someone who holds an accredited engineering degree (EE) and originally considered pursuing licensure.

That said, I do think software engineering is in dire need of some actual engineering discipline. This industry also is in dire need of title bifurcation; calling everyone "software engineer" regardless of what they actually do, just because they touch code, is ridiculous.

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#146

Post by martinraag »

_ywdj wrote: post #132
naveen99 wrote: post #124

Earlier quoted context omitted.

If you find optimism in the thing you were pessimistic about before that’s ideal. But if you can’t, how do you switch to not caring about it and switch to something else that you can be optimistic about ? It’s hard to know when to quit.

Yeah, that's all part of the technique; breaking down the issue, understanding why you're having negative emotional reactions to it, and deciding whether the problem is your emotional reaction (in which case, change that), or the outer-world situation (in which case, figure out the steps needed to change the situation). It's taken a while to learn it (indeed I'm still learning it), but it's powerful the more it start…

That sounds very interesting. Would you happen to have any pointers (i.e. books, links etc.) for anyone interested in learning more?

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#147

Post by _ywdj »

martinraag wrote: post #146
_ywdj wrote: post #132

Earlier quoted context omitted.

Yeah, that's all part of the technique; breaking down the issue, understanding why you're having negative emotional reactions to it, and deciding whether the problem is your emotional reaction (in which case, change that), or the outer-world situation (in which case, figure out the steps needed to change the situation). It's taken a while to learn it (indeed I'm still learning it), but it's powerful the more it start…

That sounds very interesting. Would you happen to have any pointers (i.e. books, links etc.) for anyone interested in learning more?

Not really any books - I think I'm going to have to write one! My approach comes from a variety of different sources - mostly in-person coaching from practitioners.

But you're welcome to email me (address in profile) and I can send you some links and suggestions.

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#148

Post by Moodles »

bsaul wrote: post #68
Moodles wrote: post #35

Earlier quoted context omitted.

People also call garbage garbage. Sometimes they're right.

I was just like you until a few months ago, when i got really interested in the technical aspect of DLT. Don’t let the digital currency scam blind you : there are some really really interesting things going on in that field.

I had a job in a company obsessed with DLT. I didn’t see anything useful. In fact I’d go as far to suggest that the only use of a blockchain is in cryptocurrency. What have you seen which suggests otherwise?

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#149

Post by bsaul »

spaceandshit wrote: post #112
bsaul wrote: post #68

Earlier quoted context omitted.

I was just like you until a few months ago, when i got really interested in the technical aspect of DLT. Don’t let the digital currency scam blind you : there are some really really interesting things going on in that field.

Any example companies or products you'd recommend looking at?

hedera hashgraph papers and founder talks (you should find them on youtube) made me realize some real people were working on solving real world issues, and not just scam people.

Re: Paul Buchheit on Joining Google, How to Become a Great Engineer, and Happiness

#150

Post by coldtea »

anoncoward111 wrote: post #114
bootsz wrote: post #102

> I didn't have to work that hard, and one day I had this realization while sitting in my gray cubicle (I was in a sea of gray cubicles surrounded by gray walls, listening to white noise and all alone): I'm like, “Man I am so tired. I need to go home and take a nap.” I went home, but as soon as I got there I realized, “I'm not tired anymore.” Is there a name for this type of fatigue (or perception thereof)? I'm curio…

Down here in real world land, I would be fired for voluntarily leaving my shift at any time. I once had a manager tell me, "Show up or be fired. We will judge if you deserve to go home or not." Yes, one should look for a better job elsewhere, and lately the economy has found more room for all of society's laborers regardless of vogue credentials. However, I can't pay the bills with interviews, and often times I lose…

>Down here in real world land, I would be fired for voluntarily leaving my shift at any time.

Not in the "real world land". Just in the part of real world that you've managed to negotiate for yourself.

Others are more (and others less) lucky.

Post reply on HN