News for hackers. Stuff that matters.
Re:Stop Interviewing with Leet Code by EdwardDiego on Thursday June 09, 2022 @08:32AM (#31680372)
Cheers for clarifying :)

I'll admit that surprises me greatly, I can't see why it's considered more efficient, but hey, Google.

Re:Stop Interviewing with Leet Code by compiler-guy on Thursday June 09, 2022 @10:52AM (#31681924)
The first program you build in Noogler training takes more compute and io to build than the Linux kernel. The distributed build systems laughs at such a trivial program and barely breaks a sweat at programs 10x that size.

A poor little laptop would break down and cry.

Re:Stop Interviewing with Leet Code by UncleMeat on Thursday June 09, 2022 @10:56AM (#31681993)
Google has a giant monorepo. It is too big for git. (Virtually) everything is built from source. Building a binary that just runs InitGoogle() is going to crush a laptop.

I believe that there are also a bunch of IP reasons for this policy, but from a practical perspective doing everything with citc and blaze is really the only option.

Re:Stop Interviewing with Leet Code by exdsq on Thursday June 09, 2022 @03:02PM (#31685381)
Can you share the order of magnitude we're talking about here?
Re:Stop Interviewing with Leet Code by eutropia on Thursday June 09, 2022 @10:17AM (#31681455)
probably efficient because their codebase size would outstretch local disk space requirements, and also would allow for comprehensive access controls