Live data from Hacker News

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

triplebyte.com

161–170 of 351 posts

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

#161
post #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…

Kinda similar reason, but the story itself isn't as geeky.

I didn't come from a rich family. Throughout my whole education, I was on hand-me-down computers. They were predictably low-spec but that's how I learned HTML, JS, and CSS in high school, and then Scheme, Java, PHP, C, et. al. in college.

Add to that the fact that our internet connection isn't great either. Alongside learning how to program, I developed a preference for tools that came out of the box. You didn't have to download them and you can be fairly confident that they are compatible with the hardware specs you got. It's for this reason that I was never fond of IDEs ala Eclipse and NetBeans; when I started messing with Linux, I used GEdit. Eventually I started doing AI stuff and, either by sheer nature of the algorithms themselves or maybe my own programming incompetence (or both), running those algorithms made my already poor computer crawl (I had 2GB of RAM back in 2010-2012, when this story took place). So I started to really try to squeeze more resources out of my machine.

Among the first to go was GEdit. I could not prove this to you scientifically but my reasoning was that if it had to draw a window, it was eating on my resources. So I learned vi, another decent text editor that came out of the box with Ubuntu. I would've gone for nano but I thought, if I'm gonna learn how to use an editor that does not render a window, I might as well go for the one with the more geek points.

Eventually, I started working and got relatively better internet connection. I finally learned the difference between vi and vim so now among the first things I do on a new machine is install vim (although in my bashrc I have alias vi='vim'). Learned a few tricks from my coworkers who used vim and started a dotfiles repo with my own vimrc. I still try to stay minimalist though. I don't install plugins so I bet by most vim users' standards, my set-up is horribly vanilla.

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

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

Wow, nice. That's pretty much spot-on

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

#163

Earlier quoted context omitted.

> What job wouldn't fire you for leaving in the middle of the day? Many. Especially smaller shops in laxer countries.

Willing to bet you that it's less than 50% of total shops, therefore less than the word "many".

"many" ≠ "most". There can perfectly well be "many" while still being fewer than half.

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

#164
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 in the United States the regulated term is Professional Engineer (or PE), ‘engineer’ is entirely unregulated.

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

#165

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

I've worked as both a hardware & software engineer. I've generally found that people who make statements like the above, don't really have proficiency across all the layers from silicon to code. Heck, there are probably a few layers that they aren't even aware exist. And yet, despite this "gaping" hole in their knowledge, it barely hinders their productivity at all.

Software, and life in general, is an exercise in abstraction. How do you effectively use abstractions that others have used, without knowing how they really work. How do you figure out which sub-abstractions and intricacies you can safely overlook, because they aren't relevant to your current priorities. And how do you shortlist the ones that you do have to care about, because they have a big impact on your project's success. These are the key skills that effective engineers possess. Trying to avoid the above problems by brute-force learning everything, is going to get you stuck in a quagmire.

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

#166
post #163

Earlier quoted context omitted.

Willing to bet you that it's less than 50% of total shops, therefore less than the word "many".

"many" ≠ "most". There can perfectly well be "many" while still being fewer than half.

You're totally right, I messed up my English! It's too early.

There could be 1m of X and 100m of y, for example

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

#167

Earlier quoted context omitted.

Most places that do "interesting" work do have some elements of distracting and noisy. At my first job on campus at Cranfield university my shared office was a portacabin which was next to the hardstanding between two of the hangers and they used to test run executive jets after being serviced < 100m away now that is loud.

The work wasn't interesting.

Ah that's a problem but at least you where paid fabulously.

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

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

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

#169

Earlier quoted context omitted.

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…

This sentiment is typical of the general HN population - a disconnect on the average person. What job wouldn't fire you for leaving in the middle of the day? Most likely a job where OP has a lot of freedom, trust, and respect - something that isn't readily available everywhere else.

I've just started my first developer job, and my team has the freedom to come and go when they please. As long as we put in the 36 hours a week, it's all good.

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

#170

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

Get hired at any place where good engineering is done, or at a startup where no engineering is really done and you get to make the calls about how engineering is done. Work for 10+ hours a day, and on your free time read about engineering from blogs or books, see conference videos, and go to conferences.

After 4 or 5 years of doing this you'll maybe know enough about how "everthing works" and what books says how to do what, or what company did what in what way, or the "state of the art", at that time you can start doing original contributions in order to not fall back.

Oh and also the Imposter Syndrome sometimes never really goes away :(

Post reply on HN