3 ms·

A postmortem has been requested; whether we'll see it... who knows. https://github.com/facebook/facebook-ios-sdk/issues/1385#issuecomment-656768967 https://git

• tmpz22 6y ago
  If there’s no postmortem I think it’s pretty safe to assume the mistake(s) were embarrassingly simple such as a disturbingly poor CI process for a multi billion dollar company. There is no shame for a bad config push... it happens... but there’s a huge amount of shame in having an ego so big you cannot admit it.
  • jkingsman 6y ago
    When I worked at FB, I once brought down provisioning of bare metal fleet-wide for five hours because I forgot a semicolon in the .bashrc of the boot ramdisk... the linter didn't catch it because it only went off of file extensions, and ".bashrc" didn't end in ".sh". Even huge behemoths aren't immune from CI and linter issues. Agreed on your second point as well.
  • jiggawatts 6y ago
    They invented the "move fast and break things" attitude. That's fine for a social network, but by forcing the SDK to be directly integrated into third party apps, they're forcing their attitude onto developers that have a "move slowly and don't break things" attitude. I'm shocked that they have this rule, that developers play along, and that there's apparently nothing that can be done about this. If there was some easy way to find out which iPhone apps that I'm using have the FaceBook SDK installed, I would mercilessly uninstall all of them. But as a consumer, I'm completely blind to the privacy-violating malware that is being forced upon me by faceless corporations. Yay.