I'm glad I'm not the only with this view. I've even refrained from stating such statements in the past on HN. While I wouldn't go to your extent just yet, I'm

I'm glad I'm not the only with this view. I've even refrained from stating such statements in the past on HN. While I wouldn't go to your extent just yet, I'm on the sample size of 2 large projects. Projects where ex-Googler's were in technical/team lead positions, and those two were the flakiest, bikesheddy and glacially moving of all projects I've worked on. I'm sure they're familiar with good sturdy systems from Google and wanted to replicate it within other organization they got hired into, but without high upfront investment to build a Google-like infrastructure (with assumingly Google internal-like tooling) the projects turned out into a mess of multiple very fragile scattered components. Both in terms of actual project code, and infrastructure systems.