Incident Report for Today's Deploy
Thank you for sharing the info, for the honesty and transparency!
relax - it's just ones and zeros!
|
|
As a fellow software dev, I feel the pain.
Sorry you all had to go through that. Onwards me boys! S L O W E R
|
|
Thanks for being honest with the community, i respect that.
|
|
Thanks for your transparency and honesty. Keep up the great work!
|
|
Transparency should be a cornerstone of all companies. Kudos to GGG. What GGG can learn from this incident is that the signing-up and processing of Early Access accounts MUST go smoothly. There will probably be some issues and these must be resolved before 6 Dec so that everyone is able to log in and play straight away. Will one week be enough time to process Early Access sign-ups and fix any issues? Why not start signup two weeks before 6 Dec?
|
|
As someone who works with databases a lot I can totally emphasize with string truncation lol
| |
Thanks for the open and concise explanation.
Appreciated. |
|
Note to some people mocking the "exception free" thing:
Exception-free is not the same as bug-free. All code should be "bug-free", though obviously it never is. Exception-free code, however, isn't allowed to use crash recovery methods to keep the ball rolling, since that would add overhead. It's entirely reasonable for stuff like low level server code that needs to be run very frequently and needs to be very fast. If there's a bug, it SHOULD crash. It should not be bandaided over. Украина в моём сердце
|
|
As fellow software QA i can relate.
Thanks for the transparency. Wer nichts weiß, muss alles glauben.
|
|
thanks for sharing, good to see the old ggg is still alive, kicking and transparent when it comes to their own issues
age and treachery will triumph over youth and skill!
|