The camp 3 is called "professional programmers". I mean: - sometimes a practical problem benefits greatly from a well-designed high-level abstraction, - somet

The camp 3 is called "professional programmers". I mean: - sometimes a practical problem benefits greatly from a well-designed high-level abstraction, - sometimes a practical problem strictly requires low-level optimization. And yes, it is totally fine to have one's inclination in general, pursue them to any level in their free time, or in some (but not all) academic research. Yet, if a professional software engineer consistently favours one of these motivations over adding value to the product, usually there are frictions in the workplace. I guess you all know "let's rewrite it to Haskell" people, or ones using their favourite paradigm for everything, and against everyone. Or ones that squeeze 20% performance in a place of code that does not matter at all for the end user experience.