[haburka]

I do wish they updated this to 2026 google! I don’t think it would be nearly as interesting though since they do get rid of most red tape but since everything is enterprise scale, it’s never easy.

[hiddencost]

Huh?

The bureaucracy is way worse. BCID requirements. MDBs that take 4+ hours to roll out. The Byzantine array of different MDB group types, often with two party control. GDPR company compliance. Tagging proto fields with provenance. Documents are private by default now. Most support happens in chat groups, and is if you're not at deepmind your help requests are getting ignored. Spending a month filing GUTS tickets to get your intern access to basic tools. XManager idle pruning. GCP automated boq setup/teardown tools usually fail and you have to fall back to getting support from a contractor 12 time zones away.

[dmoy]

I wish that the remake focused on the new bureaucracy stuff (or even new technical stuff), instead of being a near 1-for-1 rehash of the old one. E.g. it's not like anyone is being recommended to serve out of a bigtable for the last decade or whatever. But it's also not like the replacement(s) are problem-free when it comes to quota, etc.

[jeffbee]

The bureaucracy is why people trust Google with their data. I wouldn't use a Google if I thought they didn't have BCID and proto field provenance and the rest of it.

[summerlight]

Don't forget to mention automatic enrollment of your production group into access-on-demand. Any minor access on the production now requires the group manager's approval. I had a fun time with some production fire where only director level folks can approve the access. Even funnier thing is that this "refactor" was done without any prior notice.

[kridsdale3]

This guy Googles.

[awalsh128]

This is only an issue when you need to migrate services. I can't get into details but much of this isn't a problem anymore.