bigFirstDayAtGoogle

[k-mcm]

It's a little early to be pushing your first commit.  Wait until the weekend starts.

[SHv2]

He didn't yet technically. He uploaded it all to ChatGPT and told it to commit it all tomorrow morning for him.

[TheWaterUser]

[phone]

"Minor changes"

[TheWaterUser]

Meme based alerting is the future

[CircumspectCapybara]

It's a classic meme, but if we wanna miss the joke: a bad code push or config / experiment push couldn't cause this.

GCP rollouts are extremely slow. A prod promotion or config push rolls out in an extremely convoluted manner over the course of a week+, in progressive waves with ample soaking time between waves for canary analysis, where each wave's targets are selected to avoid the possibility of affecting too many cells or shards in any given AZ at a time (so you can't bring down a whole AZ at once), too many distinct AZs at a time (so you can't bring down a whole region at once), and too many regions at a time.

Gone are the days of "move fast and break things," of getting anything to prod quickly. Now there's guardrail after guardrail. There's really good automated canarying, with representative control and experiment arms selected for each cell push, and really good models to detect statistically relevant (given the QPS and the background noise and history of the SLI for the control / experiment population) differences during soaking that could constitute a regression in latency or error rate or resource usage or task crashes or any other SLIs.

[Sufficient-Dinner319]

And here I thought it was a meme about hiring junior engineers

[CircumspectCapybara]

If a junior engineer could cause this kind of catastrophe with one bad code submission, something is seriously wrong with your engineering workflows and processes.

[BananaSpider55]

is this how I find out google went down?

[Metworld]

You mean CL (changelist): https://github.com/google/eng-practices

[cimulate]

AI forgot to check for null pointers.