Live data from Hacker News

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

triplebyte.com

181–190 of 351 posts

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

#181
post #58

> When they sat down with me they said, “we want you to build an email something.” As I understand Paul began work on Gmail in 2001 at the time Yahoo Mail and Hotmail were market leaders. Interesting Google execs knew they could do better, even though Gmail didn't officially launch until over 3 years later.

it's been widely reported that gmail was a 20% project to start with. That seems inconsistent with this version of events.

Maybe he was already working on something email-y, and they noticed?

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

#182

Earlier quoted context omitted.

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.

Sounds amazing, not even 40 hours! Not everyone has that luck. I've been in shops that required 8 - 6 since your lunch hour doesn't count. I've also been in shops where I WFH and have 40 hours requirement but no oversight in how I use it. It all depends on where you work - but I'd argue the average is not as friendly as yours.

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

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

We have software engineering diplomas, and CS majors at large are indistinguishable from them in their output.

We also have certifications. They're not evidence you are a good software engineer.

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

#185
post #109
post #71

Earlier quoted context omitted.

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

I will, anonymously, in a few months. It's going to be good fun, both for the readers and for me.

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

#186

Earlier quoted context omitted.

(only including people who wrote massive amounts of important and complex code themselves and quite possibly dozen median engineers wouldn’t have cut it) John Carmack Dennis Ritchie Ken Thompson Bill Gates Donald Knuth Jeff Dean Brian Kernighan

It's a combination of finding someone really talented, putting them in an area where their talent gets well used, and giving them lots of freedom to implement as they wish.

Being there at the right time helps as well, there were lots of low hanging fruit waiting to be picked.

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

#187

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.

If your job is sufficiently badly managed, they simply might not notice you leaving.

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

#188
post #184

The title could really benefit from an Oxford comma.

This is my new pet peeve, especially when it's at all programming-related. Anyone dealing with code should know readability is a big deal. I can parse a sentence better with that extra comma without having to reread any part of it. I don't see why its ever left out.

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

#189

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?

This question misses the point I think. The differences aren’t going to be that they type 1200 wpm or something that would be interesting or obvious on video. It would more likely look like someone spending time thinking carefully, not (necessarily) at a keyboard, thinking about really needs doing, how to best do it, what the user needs and will value, and they might write 1/3 of the code of a median engineer. The ac…

I’m not saying 10x are fast at typing. I just wanted to see how fast someone can use emacs as the person from the interview.

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

#190
post #153

Earlier quoted context omitted.

> Is there a name for this type of fatigue Stress. (One of the smyptoms of)

Is it? To me the situation in question seems like the complete opposite of stressful

Yeah, this sounds like too _little_ stress to me. Imagine a bell curve with stress on the X axis and performance on the Y axis, and there's a sweet spot in the middle where you're getting enough of a kick to motivate you, but not so much that you're drowning.
Post reply on HN