Comment by Xirdus

Programming was never about communication. It was always about making the machine do the thing we want. Back in the day, a good game programmer knew which time intervals had writable video memory and which CPU cycles drew which scanlines, and spent more time rearranging the code to hit these timings than to write the actual algorithm. Later programmers (I hesitate to call them good) learned everything there is to learn about OS internals and wrote theoretically nonsensical and invalid code that still worked thanks to those internals, to save CPU cycles and especially memory use. And the next generation of programmers took the principles of late binding and abstraction to the logical extreme and created architectures that cannot be described in words anymore, only in diagrams - but are crazy good for code reuse, traceability and A/B testing.