Software Engineering at Google
arxiv.org
Software Engineering at Google
1–10 of 161 posts
Re: Software Engineering at Google
#2They 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.
Re: Software Engineering at Google
#3They 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.
> 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 the dependency information in the source files. But they are nevertheless checked in to the repository.
Re: Software Engineering at Google
#4They 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.
It was very eye opening and helpful for me. Given that at our startup we are just starting to grow and trying to set software development processes and standards to help with the growing number of devs, this info provides a good guidance on what to aim for, and also showed me that we are going in the right path in several ways.
Re: Software Engineering at Google
#5They 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.
See this ACM article on it: http://m.cacm.acm.org/magazines/2016/7/204032-why-google-sto...
Lots of things aren't source files: test data, config files, build files, metadata, documentation, etc.
Re: Software Engineering at Google
#6[deleted]
Re: Software Engineering at Google
#7They 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.
Re: Software Engineering at Google
#8They 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.
> 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?
Re: Software Engineering at Google
#9Earlier 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?
People rarely get promoted for saving money.
Re: Software Engineering at Google
#10Earlier 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?
They don't use git or any other distributed version control system, so there is no incentive to keep it small. And anything outside the source control system isn't accessible to all the tools that use it, so it would introduce complexity.