Quote:

I STRONGLY recommend to provide an option for your players to use 3rd-party “social logins

Another Quote:

you can be sure that as soon as your game is alive and kicking - you'll need to implement password recovery for your players.

Quote:

even if your RNG is statistically perfect, people will still complain🙁

Another Quote:

On modern x86 CPUs, single core can generate 150M+ random bytes/second this way (and this is a Damn Lot).

Quote:

full queues SHOULD NOT happen during normal operation

Another Quote:

With queues-implemented-over-mutexes like the ones we’ve written above, the most annoying thing performance-wise is that there is a chance that the OS’s scheduler can force the preemptive context switch right when the thread-being-preempted-is-owning-our-mutex.

Abstract:

After bashing all those Big Name guys for making those over-arching sets of guidelines, it is perfectly logical for me myself to do the same?

Quote:

DON’T use C-style cast, EVER. If you DO need a cast – DO spend time on figuring out which of C++ *_cast<>s you really mean (and maybe, you’ll find a way to avoid that cast at all)