

- The fastest code is the code you don’t run.
Not really. The code can be slow, even if I do not run it. Also, sometimes additional code can do optimization (like caching), which is more code = faster. Or additional libraries, complexity and code paths can in example add multicore execution, which could speed up. So, I do not buy the less code is faster logic.














On a slightly different example, the suckless project has a huge emphasizes on lightweight code, which they call “suckless”. I don’t think in this case faster is the goal, but having less code and be simple as possible (not even configuration files allowed, you just recompile program) and almost no documentation in the code either. But the idea is the same, of having “lightweight” code.