Live data from Hacker News

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

triplebyte.com

101–110 of 351 posts

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

#101

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?

Notch coding Minecraft comes to mind: https://www.youtube.com/watch?v=MhQ70O1MiXc

See also https://www.gun.io/blog/what-i-learned-from-watching-notch-c...

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

#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 curious if this has been studied at a psychological or neurological level. As in, why do we feel tired/sleepy in these kinds of environments (as opposed to say anxious or restless)? Personally I've experienced it at least some of the time at almost every desk job I've ever had.

I don't think it's merely boredom alone. Being bored / doing nothing at home doesn't feel the same way.

I also don't think it's the same kind of mental exhaustion you experience when working on something really challenging, like trying to crack a very hard math problem or something. Clearly in these situations the problem is that the tasks at hand, if any, are neither complex nor difficult.

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

#103

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?

I'm reminded of the "Feynman Algorithm":

1. Write down the problem. 2. Think real hard. 3. Write down the solution.

This is a joke of course, but much of the real 10xness is invisible. It certainly doesn't look like typing. Perhaps quite a lot of it occurs off screen, in conversations, whiteboards, on the computers of colleagues. I'll give you two analogies:

In some ways it's like one of those "bullet hell" shoot-em-up games, but played out over weeks or months. There are all manner of mistakes that can derail a project but only become obvious later (e.g. poor dependency or architecture choices), and there are all manner of techniques that may let you skip a section or avoid a whole category of problems, perhaps at the cost of requiring more immediate skill (e.g use of higher level but unfamiliar programming languages like Haskell or APL). Someone with 10xness dodges all the bullets and takes the correct shortcuts, while people with less talent and experience mistake the one for the other or don't see it coming.

Or there is "bug sniping", which I think is the place I've been able to make "10x" contributions: it's possible for your colleagues to be simply stuck on something, consuming a lot of time for no progress. Maybe they can manage a workaround, but at an efficiency cost - like people driving slightly broken cars which you have to open the passenger's side first to unjam the driver's door. This is the field in which puzzle-solving ability really helps. It's just that the puzzle has been created accidentally by other developers or yourself.

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

#104
post #98

Earlier quoted context omitted.

More a task for a Lamborghini than a Ferrari I would think.

There literally are Ferrari tractors :)

Lamborghini began as a tractor company, so I think the joke is pointing towards history. https://en.m.wikipedia.org/wiki/Lamborghini_Trattori

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

#105

Earlier quoted context omitted.

Netflix have Chaos Monkey, Spinnaker and Jaeger. Maybe not industry leading but still better than Apple.

Jaeger is Uber.

You're correct there. My bad.

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

#106
post #21

>there's a whole industry evolved to make us unhappy—it's profitable for us to be unhappy because then we'll go buy “solutions” for our unhappiness. I like how it's a win-win now for me acting revolutionary by being happy.

Looks like his answer assumes that "before", people were happy. I don't think this was ever the case. More so, being unhappy might be itself an evolution tool.

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

#107
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

Stress. (One of the smyptoms of)

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

#108
post #36

Earlier quoted context omitted.

Facebook, Google, Apple, and Netflix still have some of the best talent in the bay. They also push out a lot of amazing projects (PyTorch, React, Go, Chromium, Tensorflow), although Netflix much less so. At the end of the day they have the money, and they do provide ridiculous perks.

But you will only ever be a tiny part of those big projects. If you want big challenges or big recognition perhaps a smaller startup will make you happier...

Not necessarily. You can go to a team that works on a tiny part or you can go to a team that affects the entire company. You'd be surprised how few people want to work on the latter. Especially because the tiny parts are usually new press release type "fancy" stuff and not boring things like build systems, security, etc.

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

#109
post #71
post #57

Earlier quoted context omitted.

99% of people within FAANG are the most friendly people ever. E.g. for Google not being a dick is a hiring criteria (Googleyness).

> 99% of people within FAANG are the most friendly people ever I worked at one the FAANG and I found in my team and some of the neighboring teams the most insecure, unfriendly, back-stabbing, conspiratorial bunch of technically semi-competent losers I ever had the displeasure of working with. Other people were competent, trustworthy, confident in themselves and thus enjoyable. I also interviewed at other FAANGs and m…

> I worked at one the FAANG and I found in my team and some of the neighboring teams the most insecure, unfriendly, back-stabbing, conspiratorial bunch of technically semi-competent losers I ever had the displeasure of working with.

I think a lot of people would enjoy a blog post elaborating on that experience (possibly under a pseudonym to protect you from vengeance).

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

#110
post #25

> Someone who can do that is ridiculous. Talk about 10x engineers. That's more like 1000x. And it's good, clean code too. Literally no number of median engineers can do that. You can give me a million median engineers and they would never be able to do that. They would just make a huge mess. This is probably one of the most truest thing I've read about our profession. Linus Torvalds, Steve Wozniak comes to mind, who…

The difference between quality and quantity. In professions that tend more towards art than science this more pronounced. There is only so much you can solve by throwing resources at it.

On the other hand, if your problem is to simply produce more of something no 1000x genius will get you far enough. Farer than the mediocre resource, but even for these people a day has only 24 hours.

Post reply on HN