What does it take to make Google work at scale?
121–130 of 134 posts
Re: What does it take to make Google work at scale?
#122Earlier quoted context omitted.
If two clocks are stationary with respect to each other, then there is no ambiguity about where the midpoint between them is. Then you just do something like, when your clock hits noon, fire a projectile at a fixed speed toward the other clock. If the projectiles meet at the halfway point, then the clocks are synchronized. And there is no relativistic funny business involved, because the clocks are stationary with re…
"If the projectiles meet at the halfway point, then the clocks are synchronized." And how would either end-point know this exactly?
"Watch" may mean using something like a phased-array radar to measure it more precisely, if you wish...
Re: What does it take to make Google work at scale?
#123Earlier quoted context omitted.
Master Cracking the Coding Interview? Have a positive attitude?
Right, spend all of your free time cramming on algo and data structure questions that you weren't using before and probably wont use at Google.
He wanted the solution, and google interviews are more algo heavy than most. There is also this:
Re: What does it take to make Google work at scale?
#124Earlier quoted context omitted.
The people who are working to it are the Cockroach Labs folks: http://www.cockroachlabs.com/
The Wired article says they're not fully replicating Spanner, esp is time tricks. However, they are replicating a lot of its other capabilities. So, that's still a great tech in development. Thanks for the link. :) Still gotta wait a while for a full Spanner replacement with GPS tricks and all. Or something even better hopefully.
Re: What does it take to make Google work at scale?
#125Earlier quoted context omitted.
Right, spend all of your free time cramming on algo and data structure questions that you weren't using before and probably wont use at Google.
For 20 years of 6 figure salary at one of the most prestigious engineering jobs in the world? Maybe worth cramming a bit?
I've interviewed a couple of ex-googler's (not fired, still employed there) at a startup and we had to turn them down. They could handle a simple coding exercise fine, but then fell over in the component where they had to debug code and extend it with a feature.
That was when I realized a big chunk of Google's employees are going to be a reflection of their interview process (puzzle solvers but not software engineers). This was even reflected in the creation of the Go language. It's stupid simple to deal with Google employees that don't know how to use more advanced features in a language without creating something unmaintainable.
You can get 20 years 6 figure salary in most of the locations Google operates offices working for other companies. Especially in the bay.
Re: What does it take to make Google work at scale?
#126Earlier quoted context omitted.
Right, spend all of your free time cramming on algo and data structure questions that you weren't using before and probably wont use at Google.
If you write any sort of library code, you might actually start using those algos. You might have to start looking at CS papers too if your assigned a large enough scale problem! He wanted the solution, and google interviews are more algo heavy than most. There is also this: https://leetcode.com/problemset/algorithms/
I reviewed lots of CS papers while in uni and it only took a quick search to confirm the algorithm was what I had in mind. Completely unnecessary to memorize each one.
Re: What does it take to make Google work at scale?
#127Earlier quoted context omitted.
Right, spend all of your free time cramming on algo and data structure questions that you weren't using before and probably wont use at Google.
If you write any sort of library code, you might actually start using those algos. You might have to start looking at CS papers too if your assigned a large enough scale problem! He wanted the solution, and google interviews are more algo heavy than most. There is also this: https://leetcode.com/problemset/algorithms/
Re: What does it take to make Google work at scale?
#128Re: What does it take to make Google work at scale?
#129The thing that might be scary working at Google is that you work with tech than no-one else uses.
The one thing that worries me about leaving Google is how much time I'd have to spend building hacked-together imitations of the infrastructure I'm used to using. It's not because I don't know how other things work, it's because I know how these things work and I like them better. At least the build system was recently open-sourced, so I won't have to build that from scratch. But things like Borg and D are both elega…
Re: What does it take to make Google work at scale?
#130Earlier quoted context omitted.
The Wired article says they're not fully replicating Spanner, esp is time tricks. However, they are replicating a lot of its other capabilities. So, that's still a great tech in development. Thanks for the link. :) Still gotta wait a while for a full Spanner replacement with GPS tricks and all. Or something even better hopefully.
You don't _NEED_ the GPS tricks and all, and realistically you can replace some of the HLC code in Cockroach with a time network time server implementation that speaks to GPS / Atomic clocks, if you want.