Live data from Hacker News

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

triplebyte.com

211–220 of 351 posts

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

#211
post #34
post #8

Earlier quoted context omitted.

I was at a talk last week given by a startup founder and he said something similar that went along these lines: The bigger the company, the smaller your role's coverage. You get well-compensated and aren't worked too hard, but your job might effectively be "you're responsible for these two screens of this one component of this particular application". The conflict is that the bigger the company, the higher the bar fo…

One of my colleagues complained a while ago to management that "you hire brain surgeons and put them to work to peel potatoes". Quite a poetic way to express the same idea, I'd say :D

>One of my colleagues complained a while ago to management that "you hire brain surgeons and put them to work to peel potatoes".

I work in one of the top tech companies that is not FAANG, and the sentiment is the same. They hire only PhDs for a big chunk of the company and they pay relatively well - most of the people who complain about this cannot get a better paying job.

A friend of mine even said to his boss 6 months after he was hired "Why did you hire a PhD like me for this job? This work is not even close to requiring a PhD".

While I feel for him, my counter is "OK. Where would you rather work where you will do work worthy of a PhD?" They'll usually name the same few places, and not realize that those places are already "full". And they all pay less.

The reality is that there are many more qualified people than positions for the interesting work. If my company decided that yes, you're right, we don't need to hire PhDs for the job and we'll just hire MS folks, then the very people complaining would be in another company, getting paid less, and complaining about the same thing.

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

#212

Welp, now that my Imposter Syndrome has returned in full force, any concrete advice on leveling up in engineering skill (other than getting hired at Google circa 1999)? Edit: I now see that Paul coined the "Don't be Evil" slogan[0]. I'm curious what his thoughts on its removal and what that portends for Google today. u/paul? [0] https://news.ycombinator.com/item?id=22540

I quit my job to hack on things and to read. My skills have gotten like billion times as good as when I quit.

Who are you hacking for or talking about what you read with? It's easy to believe you are getting better when no one is around to give a reality check.

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

#213
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…

Dale Carnegie, in his book "How to Stop Worrying and Start Living", raised a similar point. I won't quote directly, as I read it in Polish; the following is based on my notes:

In one the latter chapters, he has a rule about "summoning your own enthusiasm". The primary observation in that part of the chapter was that it's really hard to truly exhaust someone physically, and even harder to exhaust them mentally, if they're doing something they actually care about. He gave some examples, one involving special forces people, and concluded that the primary source of tiredness for most people is lack of motivation - lack of interest, or not being able to feel there's a goal to all the work one is doing.

While my opinion is that Carnegie was exaggerating a bit here, I won't deny that this rings very true to my experience. As a programmer, I don't get physically taxed by work, and I very rarely get mental exercise too (most programming on regular web jobs is just plain tedium). But I do feel really tired on the job very quickly, and - back when I was a regular employee - the feeling used to evaporate almost immediately when I clocked out for the day.

I can even give an example from yesterday - lots of work and a visiting a doctor made me really tired by the evening, but I decided to sit down and write some code for a side project. My tiredness was gone immediately, and after 2 hours of cranking out code, I had to force myself to go to sleep, in order to have any energy for the next day.

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

#214

Anyone have videos of someone programming fast or a video of a 10x engineer working or a comparison output of a 10x vs above average?

George Hotz Coding a SLAM algorithm from scratch. Really insane.

https://www.youtube.com/watch?v=7Hlb8YX2-W8

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

#215
post #65
post #61

Earlier quoted context omitted.

>for Google not being a dick is a hiring criteria Wonder what the false negative rate is?

Probably quite high. Google's culture and hiring process is so well documented at this point, I suspect any suitably talented individual could appropriate some cultural fit. Of the (current and former) googlers I know personally, they are a mixed bag but there are some traits that are more common. Self assurance and the uncanny ability to never be seen to be demonstrably incorrect are prevalent tbh - but that applies…

> the uncanny ability to never be seen to be demonstrably incorrect

I think that may be very easy to do, just state that everything you say is just a theory or your opinion... but this is just a theory.

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

#216
post #66
post #40

Earlier quoted context omitted.

They've already done so much more than either of those. Bell Labs delivered a fair bit of tech, but Xerox PARC did great demos. Xerox PARC == Magic Leap or something like that.

Don’t know why you were downvoted. Xerox parc did in fact release nothing to the general public iirc. But they got great tech which got ripped off, unlike magic leap maybe ?

The Learning Group at PARK did release Smalltalk, but guess that's not "for the general public".

I was under the idea they never really wanted to release a product for mass consumption.

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

#217
post #37

Earlier quoted context omitted.

But you're not competing with those brilliant people on technical merit, but in the political game of building a fiefdom in a large company. That takes very different skills, and many people find it distastful.

Some might be surprised at what are the most effective strategies in fifedom building and rising in a large org. It very often has much more about making deliberate choices to help those around you succeed, to actively recognize others and help others arond you sieze opportunities. And that kind of demonstrated leadership is what will propel your own rise in status within an organization. It’s a mistake, and will set…

>It’s a mistake, and will set you back to think of politics as a zero-sum game.

I think we have a bit of a meta-false-dichotomy here. I agree it's a mistake to think of it as a zero-sum game. I also would say it's a mistake to think your advice will reliably work.

I've often sat in career advice talks and they often give the same advice you gave. Invariably during Q/A someone will point out they followed that exact advice and got screwed. The responses by the panelist fall into two categories:

1. I don't believe it and there must be more to the story.

2. You're in a poor organization. I suggest you find a better place to work.

So yes, the advice is good, but only when it works :-)

As a company gets bigger, the likelihood of faulty incentives existing goes up. The likelihood that what's good for my team + boss is bad for the company goes up.

Personally, I don't have illusions. I've worked in jobs where the advice you gave won't work. And I side with the second answer. Instead of playing bad politics, it's just a lot better to find an organization that is worthy of me/you. The advice people who had been in the org gave me was consistently "Forget about what's good for the bigger picture and the company. Make your boss look good even if it's a bad solution and will waste others' time and money." I didn't follow that advice and I paid for it. At the same time, my time and effort is valuable - I'd rather use it for something better than this. Either I work to change the organization's culture, or I leave.

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

#218
post #151

Earlier quoted context omitted.

I have ADD (diagnosed) and this happens to me every day at work. Around three o'clock in the afternoon I get so sleepy I start to literally fall asleep at my desk, but if I go home I'm immediately refreshed and back to full capacity for another eight hours.

I don't have ADD and it happens to me every day.

I tried to hint a doctor once to maybe test me for this, but she wouldn't give. I feel like adult ADD isn't yet recognized in my country as a legitimate thing.

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

#219
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.

Because software development is engineering and not science. It's absurd that my job title can be regulated. I applied for software engineering, I interviewed for it, the company hired me to do software engineering, I'm paid to be a software engineer, the official documents that allow me to legally stay in the US say my job title is "Software Engineer"... Yet I'm not a software engineer because my bachelor's degree s…

Do you think it’s absurd that titles like Doctor is regulated? You may not think it’s neccessary to have a professionalized version of Software Engineering but what about code running RTS, critical health care systems etc?
Post reply on HN