3 ms·
If that account is a true reflection of events - it's really disappointing that engineers got fired (edit: or resulted in engineers leaving). A company needing
by mtkd 8y ago
If that account is a true reflection of events - it's really disappointing that engineers got fired (edit: or resulted in engineers leaving).
A company needing hours to identify/fix a minor code issue that affected 40M people is a senior management failure - not engineering.
When I read the initial %G post - I couldn't see how you could/would even test for it - unless you'd heard about such a scenario previously.
Rolling heads in engineering for understandable errors just creates a toxic environment for building anything remotely interesting going forward.
- jwilk 8y agoWere they actually fired? I assumed that they got tired of the shitshow and quit.
- Volt 8y ago"Blameless postmortems anyone?"
- masklinn 8y ago> When I read the initial %G post - I couldn't see how you could/would even test for it - unless you'd heard about such a scenario previously. Interestingly, because IIRC the Gregorian calendar has a 400 years "full" cycle (hence the "Doomsday Rule") depending on the "expense" of your processes you could just use exhaustive testing: there are less than 150k days in 400 gregorian years. Considering exhaustive testing is feasible across 32b ranges (https://randomascii.wordpress.com/2014/01/27/theres-only-four-billion-floatsso-test-them-all/ https://randomascii.wordpress.com/2014/01/27/theres-only-fou...), ~17 bits isn't much of an issue. You would still need to define properties which hold across the board, but then you could just check literally every date of the cycle. This get significantly less feasible if you need to check full calendaring (datetime x timezones).