that's because these best practices aren't geared towards producing something good - it's geared towards making something easy to understand for someone else, and easy to maintain when requirements change.
It is also designed for the lowest common denominator programmers - so that many can work on the same code base, over a long period of time.
For games, none of these goals matter at all.
Here's the base Source Engine movement code for example: https://github.com/VSES/SourceEngine2007/blob/master/src_mai...
switch (index)
{
case 0: return sound0;
case 1: return sound1;
case 2: return sound2;
case 3: return sound3;
case 4: return sound4;
}You could argue that having `sound` as an array, and index into that array is better, but once again, what does "better" mean here?
this code works as is, you will not get an array index out of bounds error. If this is quick and easy to write, what else could you ask for?