4 ms·
The current state of Twitter seems to indicate there's a significant problem with the code, which implies the people who would have either spotted that before i
by onion2k 3y ago
The current state of Twitter seems to indicate there's a significant problem with the code, which implies the people who would have either spotted that before it was deployed or fixed it quickly afterwards, are unable to do so. Given the number of layoffs and resignations Occam's Razor would suggest the reason is because those people aren't available to do that work.
We don't kmow it's true but it is a likely explanation.
- tomatocracy 3y agoBut these are "significant problems with the code" which evidently can't be fixed by simply reverting relevant changes. In that case, it seems more likely to me that these are due to long-standing issues which would have caught up to the company sooner or later.
- onion2k 3y agowhich evidently can't be fixed by simply reverting relevant changes Rumors suggest that part of the change is moving from GCP to something else. Something like can't be reverted without signing a new contract with Google (and paying the bill..).
- tomatocracy 3y agoAh - I hadn't heard that and it does make some sense. But I'm not sure that the alternative version of events (where the engineers who were fired or left were still around) would look much better in that case - perhaps delay/better planning might have helped (though of course we don't know how much planning was done) but it's also entirely credible that this was essentially inevitable with such a move.