Live data from Hacker News

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

triplebyte.com

121–130 of 351 posts

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

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

People were happy before. Some societies were not happy before or haven't been producing significant quantities of happy people for a very long time.

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

#122
post #9

Earlier quoted context omitted.

So, who's the new 'Google' now?

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.

Ever use Xcode on a day to day basis? Clearly not the best talent there.

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

#123
post #74
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…

I haven't read that much about Woz, but from what I gather he was brilliant, but his code (or hardware) wasn't "clean". He did have great insights leading to performance, but some stuff sounds fairly ridiculous today, like the stuff he did for Apple II's color display: https://www.filfre.net/2011/10/mystery-house-part-1/ Basically: brilliant, but very quirky.

[deleted]

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

#124
post #113
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…

I think it's related to the notion that depression (and burnout and other chronic states of negative emotion and low energy) is caused by a lack of optimism - or a lack of things to feel optimistic about. From an evolutionary point of view, if we're not inspired and excited about what we're doing now or what we expect to be doing in the near future, it makes sense to go into energy conservation/restoration mode and g…

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.

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

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

I’d say what we do is closer to engineering than science. I was fine with programmer and then developer, but fashion in language as well as clothes change, and so here I am an engineer.

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

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

It's a strong feature of Attention Deficit Disorder as I understand it. Hyperfocus often comes hand in hand with extreme fatigue and brain fog in the presence of tasks that don't motivate enough, to the point that you can feel it physically.

I often get it myself, feeling like I can't physically write another line of code until I move onto one of my own projects, then I'm good to concentrate for another 6 hours. I have to work extremely hard to complete tasks that on the surface look very simple and involve solving no new problems. This also extends into my normal life, like cleaning a messy room.

Note: I haven't been diagnosed with ADD and am not suggesting anyone has it if they experience this, I've just looked into it a lot.

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

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

"Software engineer" is a common title - I'm UK based, not even US - and that perhaps helps to differentiate practical development work from more academic computer science work: the two activities truly are quite different. "Engineers" is probably just an evolved shortening of that "Software Engineer" title.

I know what you mean though: Chartered Engineer is a proper thing for example, with exams and governing bodies involved, and anyone in construction who just decided to call themselves a Civil Engineer would likely get into some bother for doing so.

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

#128
His reason for why he’s a vi guy was funny! (He only had 60M free for his Linux partition and emacs wouldn’t fit). It did sound mildly apocryphal but so did most of it.

My reason for vi is equally random. I learned Unix at college, but I wasn’t allowed on the systems because I wasn’t an engineering student. I had to resort to nefarious means to get online, so I needed to keep a really low profile. The easiest way to do that was to remote into unused boxes in the lab. (This was back when it was easy to get onto an intranet and hard to get on the Internet — it’s exactly the opposite now!) The systems that were usually available were these crappy diskless Sun workstations that booted over the network. They didn’t have enough memory to run emacs without paging and paging over the network is a recipe for frustration. Plus if someone logged in and the system was slow the first thing they’d do is try and find out why, which might lead to them wondering why I was on that system, just who I was, etc and that was a bad direction for me. I also couldn’t talk to people in the labs since I wasn’t supposed to be there, so I was entirely self taught, and emacs seems like the sort of thing someone has to evangelize to get you over the initial hump.

Anyway, that’s my story — what’s yours? :)

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

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

Here's a good summary of the history of the term and discussion on "programmer" vs "engineer".

https://www.theatlantic.com/technology/archive/2015/11/progr...

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

#130
post #118
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…

"Boreout" is an established term, it's kind of the inverse of a burnout. https://en.wikipedia.org/wiki/Boreout

That's interesting. I developed an ulcer at my first job out of college in 2004 and didn't know what was wrong until I spoke with a doctor. It was a brain factory with white noise and cube walls so high you had to stand to see your neighbor. I used to work 11-14 hours per day because I was young and foolish, and had a blasé manager. My how times have changed.
Post reply on HN