Such a good deep dive into the issue (Destiny)
Humorously I had this exact discussion with someone at work. And my point was that it’s not practical to test 1:1 against a production environment and that it arose because the use-case that caused it wasn’t in their test sample. Which this confirms. It is also a good reminder that it is a game made by people and people don’t trend to perfection and that is okay. Their response to all of this has been, imo, a good way to handle such an immediate recurrence.
Yep.
And it was still their first public data failure in 16 years of running games that consume and process persistent data.
The fact that both rollbacks were caused by the same bug and just sheer bad luck points that overall, they've been pretty good at what they do.
Complete thread:
- Bungie done did it again... -
Korny,
2020-02-11, 12:42
![[*]](themes/default/images/complete_thread.png "Open whole thread")
- Back up! - INSANEdrive, 2020-02-11, 16:46
- A fascinating debriefing/retrospective from the DOC -
Pyromancy,
2020-02-11, 21:19
- Such a good deep dive into the issue -
kidtsunami,
2020-02-12, 07:39
- Such a good deep dive into the issue -
Harmanimus,
2020-02-12, 08:44
- Such a good deep dive into the issue - FyreWulff, 2020-02-12, 18:09
- Such a good deep dive into the issue -
Harmanimus,
2020-02-12, 08:44
- +1
![[ [ No text ] ]](themes/default/images/no_text.png "Empty posting / no text")
-
Robot Chickens,
2020-02-12, 12:51
- TL;DR - Spaghetti - someotherguy, 2020-02-12, 13:44
- Solid Write-Up! - INSANEdrive, 2020-02-13, 14:12
- Such a good deep dive into the issue -
kidtsunami,
2020-02-12, 07:39
- Cached / stale servers / data.. - FyreWulff, 2020-02-12, 16:00