> Google has hundreds of billions of dollars in cash they literally can't decide how to spend. Those billions of dollars don't code for themselves. You need to

> Google has hundreds of billions of dollars in cash they literally can't decide how to spend. Those billions of dollars don't code for themselves. You need to hire more folks (yes, overtime is a thing at Google), you need to direct them to do the right things (means: more hiring), and more infrastructure. Besides the cafeterias which boil down to "even more hiring" (and why not, we did that twice in our thought experiment already) those devs need office space (of some kind), equipment and server time for testing their thousands of additional commits every week. And more server time to cover the additional test cases (eg. for additional browsers), so this is super-linear. Given infinite dollars (or any reasonable approximation of that), the problem really is how to spend them without ending up finishing nothing because you've just invested them in a giant gridlock situation.