,
5 tweets,
2 min read
Read on Twitter
@copyconstruct I work for a competitor and have my own biases, but reading this I feel a sad sense that hubris in Google's engineering culture has come to this and continues to blind. The proposed fixes read as dangerously wrong to me. 1/n
@copyconstruct "we will harden Google's cluster management software such that it rejects such requests regardless of origin, providing an additional layer of defense in depth and eliminating other similar classes of failure." ... this feels like more layering, more complexity. 2/n
@copyconstruct Why does automation even have access to multiple regions? Why add more logic, which could have its own bugs and problems, instead of enforcing more robust separation; compartmentalization with their own local fail-safes. 3/n
@copyconstruct it reads like the deep reaction is "We just need to be a bit smarter, just add another case for this, we can defeat reality", rather than humility in the face of the unpredictable, and embracing simplicity. 4/n
@copyconstruct I am reminded of the marketing papers that say Spanner gets around the CAP theorem because the network will be close to perfect. cloud.google.com/blog/products/… … I am just going to use my outside voice when I roll my eyes from now on. 5/5
