Live data from Hacker News

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

triplebyte.com

261–270 of 351 posts

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

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

My first time using Linux on my desktop I used to have video card issues a lot, which means I’d get locked out of an X11 environment and be stuck in the console trying to fix things. I didn’t have another machine to use to search the web for help so I was just kinda on my own. I used to just hit to get Bash to print all possible commands, and I’d just try random ones until I found one that would let me edit text, and…

That seems both like an interesting and a very scary way of exploring your system. If you're careful, by checking manpages if present and running with the normal --help flags before trying anything else, you're probably fine; but it seems dodgy nonetheless :p

I wager you didn't know about text-based browsers like lynx? I'd say that would have been a solution to your predicament.

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

#262
post #226

Earlier quoted context omitted.

Dave Cutler. The NT/XP/etc. architecture basically stalled as soon as he left and future improvements were incremental. You can tell there wasn't a winer equivalent on the windows 95/98/ME teams

I'm pretty sure Dave Cutler is still at Microsoft. Cloud stuff.

I meant when he left the team.

But yea, now he's doing cloud stuff. I'm pretty sure it's no coincidence that that is now their best performing product line either. Satya can thank him for his promotion to CEO.

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

#263
post #219

Earlier quoted context omitted.

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?

I would argue that regulations are ok when there is a well-developed infrastructure behind the regulation. If we have a lot of evidence that human activity causes global warming, and we have a lot evidence that government regulations X can help global warming, it makes sense to regulate X to solve/alleviate that problem. Or say, we have a lot of evidence that legalize+regulate works very well to solve drug issues (look at Portugal). Do we have any infrastructure in Europe, or US to regulate software engineers? I do not know of one. I studied in UC Berkeley, which is apparently one of the best universities in the world to study CS, and then they gave me a "BA in Computer Science" (the same way you get "BA in Physics" or "BA in Mathematics" ... UC Berkeley L&S only gives one type of diploma), it's kind of awkward to claim that the infrastructure in the US that selects qualified software engineers filtered me out, the same way it filters out some people who wanna be doctors. Btw I do work in a company that handles real time, highly critical insurance data. My employer thinks I'm capable of working in this company; which doesn't mean it's necessarily a good idea, as we saw in cases like Equifax, but I cannot think of an alternative. I love my job and I believe I'm qualified to do it, so I'm gonna be pragmatic about this...

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

#264

Earlier quoted context omitted.

> And yeah, the best tactic is usually "make my boss look good". You say this like it's a bad thing. You should be making your boss, your team, and your teammates look good. If you are doing those things, you are probably also making the company look good. It's thinking about the long vs. short term. Focusing only on your own optics may work okay in the short term, but they cap out fairly quickly. Think about how it…

And just like that, the just world fallacy kicks in :) I certainly don't think it's a bad thing to make your teammates look good, but in general it's more effective to give the lion's share of the credit to the boss rather than them. And credit is a limited resource. I say that like it's a bad thing because it kind of is. I believe there are some companies where coworkers rather than management decide promotions and…

Since you're talking about 'credit' you have completely missed the point. I'm talking about making the whole team look good by making them better. That means helping team members get better. That means helping your boss get better. If the whole team looks good, guess who benefits the most from that? Your boss. And, who cares who decides promotions. If every team you end up on becomes great, you will end up where you want to be.

This also has nothing to do with a just world fallacy. This is thinking long term. Rarely can someone politic all the way to the top. In order to lead, you need the support of your team. You get that by being a great team member yourself.

/rant

Finally, I'm tired of hearing how awesome people are, but their team sucks or their boss sucks (doubly so for people working at FAANG, because the low bar is so much higher). If they are so awesome, then get out there and help the team improve. Instead it's I'm so smart, but everyone is holding me back. I'm stuck on a crappy team, etc... Grow up.

/rant over

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

#265
post #232

t. I think you have to interview them a little bit. Ask hard questions and see if they give direct, insightful answers, or if they're evasive and dismissive.> Actually, letting charismatic founders deliver a triple-scoop of their enchanting story isn't the technique I'd recommend. Both the good ones and the bad ones got this far by being very persuasive. Do reference checks instead. Find people who worked with them f…

He isn't suggesting letting them deliver a triple-scoop of their enchanting story, he's suggesting that you filter it through your own logic & experience and try to poke holes in it.

Elon Musk was once asked in an interview "How do you judge whether a highly-technical expert really knows what they're talking about?" His reply was along the lines of "You ask them questions of progressively increasing levels of detail. Someone who's actually an expert will understand a subject on many levels; they'll be able to give you the ELI5 version, but then will have good answers every time you probe a level deeper."

Larry & Sergey's elevator pitch was "We built the best search engine in the world", but if you asked them "What's it running on? How many machines? How many pages does it index? How do you handle duplicates? How many queries/day do you get? What are people looking for? How do you rank pages?" etc. you'd get good answers for all of them.

Elizabeth Holmes's elevator pitch was "We're going to revolutionize blood testing with finger-stick tests", but then if you asked "Which tests do you run? How many molecules of __ are in a drop of blood? How much variance is there between people?" you would very quickly run into either evasions or outright lies. Once you start asking questions on top of a lie their story usually falls apart pretty quickly, because few people can remember everything they just made up 5 minutes ago and still make up some logically coherent detail on top of it. (This, BTW, is why improv theater is so hard, and why most improv shows are comedy, where it's just funny if you end up with a non-sequitor.)

The same technique works well for reference checks, but you can't blindly trust whatever the reference tells you. Most people cherry-pick their references; it's easy for a charismatic charlatan to find some people who are still super-enchanted by them. Many people are also pretty unwilling to talk (particularly about litigation-happy scam artists like Holmes), for fear of defamation lawsuits.

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

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

Honestly, I have a ("proper") engineering degree and the boundaries between working on hardware design ("proper" electronics engineering) and working on software are pretty blurred. You have a desired outcome, you apply design thought to it and then you have a work plan, you execute (whether by writing software or simulating circuits or documenting or whatever) and then you test it works and make changes.

There's a spectrum of software engineering like there's a spectrum of any engineering. It's called software engineering because it's applying an engineering approach to software.

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

#268

Earlier quoted context omitted.

It didn't matter if they had an off-putting personality or were "OK." Either way, I just wasn't feeling it. On the other hand, the same happens wherever I go. Maybe Google's reputation of attracting certain personalities led me to believe there would be others that were similar or like-minded. Instead, they were mostly unhealthy judger types (though I'm not sure if the source is reliable, a few years ago 23.6% were s…

You seem to mention the Myers Briggs a lot in your posts... I’m not sure how useful it is. The reduction of individuals to acronyms sounds to me like unhealthy judgment, so maybe Google did a better job than you realized in attracting “like minded” individuals!

It's not that useful, but is another way to help illustrate what I'm trying to say.

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

#269

Earlier quoted context omitted.

True. I have a new catchphrase that I use: Google does everything at scale. They waste talent at scale.

And it’s such an utter shame with their resources; they could be the next Bell Labs or Xerox PARC.

They probably are. There's a ton of interesting research going on at Google that is not being capitalized on economically. They just need a few ambitious visitors or ex-employees to "liberate" it, the way Steve Jobs and Bill Gates did to Xerox. In some cases (eg. TensorFlow, Chromium, protobufs, or LevelDB) it's already been open-sourced.

Note that neither AT&T nor Xerox were the prime beneficiaries of technologies developed at Bell Labs or PARC, respectively.

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

#270

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?

As far as being able to visualize what it's like to be a 10x developer, such a person can continuously type whatever is needed to get to the next step, whether it's code or sql or whatever, while maintaining adequate performance and quality.

They don't have to type fast, but they're also not relying on Stackoverflow for learning concepts.

Most web applications start as prototypes written by one guy in 90 days or less, then just re-labelled as "production."

Post reply on HN