Quote:

I’ve seen game companies with hundreds of thousands of dollars lost per hour of unplanned server downtime.

Another Quote:

deterministic debugging is by far the best thing I have seen for production debugging.

Quote:

Then you can recover from any single server failure in a perfectly transparent manner

Another Quote:

after the program fails in production, we can get the input log and run it in the comfort of a developer’s machine, under a debugger, as many times as we want, and get exactly the same variables at exactly the same points as happened in production

Quote:

Doing sanitization at IDL level automates quite a bit of tedious-and-error-prone work, which is always a Good Thing™

Another Quote:

Hey, this whole thing can be made MUCH simpler, the only thing we need to acknowledge is that the best identifier for a string is the string itself!

Quote:

It is strongly recommended to have your build server to compile your game for at least two sufficiently-different platforms from the very beginning

Another Quote:

If allocation of 50 bytes causes an “out of memory” error, we’re probably already long dead because of unacceptable swapping. And even if we disabled swap file – chances that we will recover from this condition, are infinitesimally small