2 ms·
I would guess, with some evidence from experience, that all FAANG companies have sufficiently bureaucratic process, checks, and balances, to largely mitigate th
by ryandrake 6y ago
I would guess, with some evidence from experience, that all FAANG companies have sufficiently bureaucratic process, checks, and balances, to largely mitigate the risk of a disaster caused by a lone wolf screwing something up. Multiple cross-functional sign-offs whenever you deploy something to production, mandatory code reviews, gatekeeping access to push changes for junior folks, etc. This has got to be a mostly solved problem for companies of that size.
I'm not denying they are primarily focused on preventing false positives, but not for the reason you mentioned.
- pavas 6y agoYeah there are definitely other reasons but this is one of the biggest in my opinion. There's always a tradeoff between security/bureaucracy and speed in delivery so as to remain competitive. This does matter even at large scale. I would agree that if one were purposefully trying to cause as much damage as possible, that impact would be contained by these processes. But one can still make mistakes or be a drain on the team's energy and focus which increases the chance of mistakes team-wide. At scale, even minor mistakes are costly, not just in terms of direct impact but in terms of the opportunity-cost of developer effort that could be better spent elsewhere. Of course, my direct knowledge has sample size of n=1 here so it likely does not apply uniformly across all large companies. I would love to hear contrasting opinions on this topic. I've spent a lot of time thinking about what would help developer teams increase their productivity w/ regards to adding value.