4 ms·
I find it just as humorous, every time this question is asked, that people throw out the "it's just a X, Y, Z" without ever thinking too hard about the roles ne
by halfmatthalfcat 3y ago
I find it just as humorous, every time this question is asked, that people throw out the "it's just a X, Y, Z" without ever thinking too hard about the roles needed, beyond engineering, to fulfill X, Y and Z at scale. X, Y and Z can usually also be broken down into many, many subparts all with their own supporting cast.
- danpalmer 3y agoYeah I get that, but I think there are two sides to this. One is that it is possible to guess ballpark figures without knowing the intricacies, and I think anyone with experience in a big tech company of this ilk can probably make a reasonable estimation (to within 50%?). The other is that it's easy on the inside of these situations to justify each individual role, and miss the fact that the system is too complex and a simplification may be able to drop significant numbers. I'm not suggesting it is too complex, I fully realise there's a different sort of scale involved when you operate a large globally available service like this, but duplication still happens, engineers still make things more complex than they should be, etc.