skj

Unless something big changed since I left two years ago, the org chart is totally visible to the entire company, and so are levels except when someone explicitly opts out (most do not bother).

Are you knocking the knockers? No one is suggesting they be arrested. They're just being ridiculed.

Pretty uncommon at tech companies, but it's entirely based on the company's policy. The company can fire you at any time (as long as it's not one of several specific bad reasons like racial discrimination), but it's the company that employs you, not your manager. So only the company can fire you.

Generally big tech companies don't give your manager the authority to blindly fire you, but only because that's a decision the company made.

My former boss too! That message was sort of the beginning of the end for the trust I had. Very disappointing.

Yeah but it's a lot easier to not care.

What I tried, in a similar situation, was being clear that I did not support the company or its leadership and for them to never contact me again. It worked.

She didn't.

eh?

Pretty low chance that the status page is automated, especially via health checks. I imagine it's a static asset updated by hand.

Little known fact: "Bob Dole has died" were his last words.

It's GCS.

When we designed the security model for Google Cloud Build (I do not work there anymore), we decided that containers were not valid security barriers. So, all partitioning was done on the VM and network (configured outside the VM) level.

It wasn't hard to convince anyone that this was the right way to handle things.

I don't think "this is a dangerous idea because people might need it to function" is a great take.

Last I checked, which was not recent, it was hosted out of an S3 bucket.

Google uses map reduce extensively... where it's appropriate.

True time helps with things like spanner transactions. It's just a totally different use case.

Well.... bye!

I measure distances in the time it takes light to traverse them, don't you?

The host can put their CDN inside the operator's network. And, generally, a centrally operated CDN can be smarter than p2p.

Hmm cloud build spoofs it :) if the customer build accessed the underlying VM's metadata it would be very confusing (though not a security issue).

It was not straightforward. I learned a lot about iptables and docker networking.

Ok, now I understand that survivor bias meme.

A self-made mining billionaire? Indeed that is fascinating. He must have been working really hard down in those mines to make that much without any help.

"this context" is using a map from the beginning and not having that slice.

With big python projects it's often difficult to figure out what code is going to be executed next due to inheritance and mix-ins.

With Go, it's usually pretty straightforward. Yes, there are interfaces, but they're used in places where people actually want the choice of code to be dynamic, rather than people just having fun building up crazy hierarchies in the name of DRY.

So, with Go I find it very easy to read because of high code locality and the ease of following to the correct destination with function calls.

For things that are already local, "ease of reading" is just code for "familiar". Go is strictly easier to read because tracing through is strictly simpler. Anything else is just spelling and those barriers disappear with only minimal experience.

The limit there is likely that no one has figured out how to make an annual fruit or nut tree.

How close are we to a black hole?

You can definitely hear the difference between many guitar models. Are you suggesting that pickups are the only difference?

It ABSOLUTELY is a SPOF and was responsible for several high profile outages at GCP last year.

In Google, auditing is handled separately.

The availability guarantees necessary for basic authorization are far more strict than auditing. Auth fails closed, audit fails open.

Anything that can be stripped out of auth should be, even if we're talking about a best effort extra rpc from the auth service.

Auditing typically needs more information than auth as well, and making the auth pipe wide is a risk.

"there must be a reason" hahahahahaha

Some commits cannot be cherry picked. This is because there is no coherent diff for them, like with merge commits.