Mg6yDfjp5U

Definitely. The front line support agents handle only the most basic requests. Anything even remotely complicated, such as this, would be internally kicked around until they found someone familiar with the project to give input. Which most likely is someone who worked on the original implementation.

I recently left Google having worked on a number of projects with various YouTube teams. I think I can explain why it's being handled this way by YouTube.

This is a fairly nuanced/involved issue, so the task of classifying the bug likely made it's way to one of the engineers responsible for the implementation of this feature.

That engineer has already launched this project, and filed it away under their GRAD (performance) artifacts for when promo/annual review talks roll around. There's no motivation for this engineer to waste time fixing this bug because it won't benefit their promo packet, and they are already being put under pressure to launch other projects which _will_ benefit their promo packet.

So they do what they can to sweep it under the rug because that's what the promo/annual review framework (GRAD) incentivizes and rewards.

Where are you getting that $150M spent on RSU grants per year from? Unless I'm missing it, I don't see that in the report and it seems way too low.

Let's say the average engineer gets $100k/year in RSUs. (I would guess the actual number is higher.) That would only cover 1500 engineers.

I just downloaded it, and can't get past the landing/sign-in page: "Google sign in error.null"

Unfortunately, signing in with Google is the only option.

Do you know of any resources describing this as a developer responsibility/best practice? I agree with you, but I'm looking for some independent resource that I can show to Business to convey to them the importance of this.

(Most resources I'm finding are only describing the importance of remembering to change the default password, rather than designing a system without a default password to begin with.)