Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Software Engineering at Google

arxiv.org

Post reply on HN
Print view View original

11–20 of 161 posts

Re: Software Engineering at Google

#11

Post by jrockway »

pzh wrote: post #8
gumby wrote: post #3

Earlier quoted context omitted.

> What the heck is the other 991000000? Says right in the article: various config and dependency files, presumably both as caches (where everyone would generate the same product) or as a record of where things stood on at time t. For example: > In some cases, notably Go programs, build files can be generated (and updated) automatically, since the dependency information in the BUILD files is (often) an abstraction of…

So basically somebody can write a script to put this Build file in gitignore, save the company millions of dollars, and get promoted for it?

There are other possible annotations in the build file.

You can get an idea of what it looks like by reading the Bazel docs: https://bazel.build/versions/master/docs/be/overview.html

Storing a few text files at Google doesn't cost millions of dollars, BTW.

Re: Software Engineering at Google

#13

Post by harryjo »

pzh wrote: post #8
gumby wrote: post #3

Earlier quoted context omitted.

> What the heck is the other 991000000? Says right in the article: various config and dependency files, presumably both as caches (where everyone would generate the same product) or as a record of where things stood on at time t. For example: > In some cases, notably Go programs, build files can be generated (and updated) automatically, since the dependency information in the BUILD files is (often) an abstraction of…

So basically somebody can write a script to put this Build file in gitignore, save the company millions of dollars, and get promoted for it?

Then you have to run a tool that processes .go source files in order to perform dependency analysis. Consistency is a virtue.

Re: Software Engineering at Google

#14

Post by harryjo »

aanm1988 wrote: post #2

They have a billion files in their repo, 9 million are source files. What the heck is the other 991000000? I skimmed this. Mostly just stuff any competent company would/should be doing. it's google though, so they act like it's super awesome.

> would/should

There are billions of dollars of difference between "would" and "should"

Who is "they" who act like it's super-awesome?

Re: Software Engineering at Google

#16

Post by jazoom »

Waterluvian wrote: post #7
aanm1988 wrote: post #2

They have a billion files in their repo, 9 million are source files. What the heck is the other 991000000? I skimmed this. Mostly just stuff any competent company would/should be doing. it's google though, so they act like it's super awesome.

Someone checked in a `node_modules` folder by accident.

That would pretty much do it

Re: Software Engineering at Google

#18

Post by dontreact »

harryjo wrote: post #15

Is section 3.1 "20%" time still true?

In my experience, yes. Most people find it courteous to inform their manager but I did a lot of 20% time that led to getting hired with Google Brain, and it was never any doubt in my mind that my manager would approve.

That being said, there were times when I was really excited about the project so I would work 80% time plus 40% time and stay late.

Re: Software Engineering at Google

#19

Post by justicezyx »

gsylvie wrote: post #17
williadc wrote: post #12

Earlier quoted context omitted.

Finance people do.

Good point. I meant software engineers rarely get promoted for saving money.

This does not apply in this post though.

There are thousands of SWEs working on systems to save money for Google.

Re: Software Engineering at Google

#20

Post by nlpleb »

dontreact wrote: post #18
harryjo wrote: post #15

Is section 3.1 "20%" time still true?

In my experience, yes. Most people find it courteous to inform their manager but I did a lot of 20% time that led to getting hired with Google Brain, and it was never any doubt in my mind that my manager would approve. That being said, there were times when I was really excited about the project so I would work 80% time plus 40% time and stay late.

Can you tell us about what exactly you did that led you to getting hired with GB?
Post reply on HN