> As with all engineering, there are always trade-offs to every decision
This is the cliche that needs to be put to rest.
Yes, often there are tradeoffs. But just as often one thing is better than another thing, and there is no tradeoff.
A worldview in which everything has pros and cons and is ultimately subjective is fertile ground for entrenched habits, because it means never having to admit you're plain wrong, that there is a better way, or that other approaches are simply that much better than yours.
I believe code design is ultimately subjective. Unlike other metrics like performance which can be easily and definitively measured, you can't easily measure 'good' code. The definition of 'good' changes based on the context of the code base and function the code is trying to achieve. In this case, choices like having giant functions and files is definitely subjective.
This is the cliche that needs to be put to rest.
Yes, often there are tradeoffs. But just as often one thing is better than another thing, and there is no tradeoff.
A worldview in which everything has pros and cons and is ultimately subjective is fertile ground for entrenched habits, because it means never having to admit you're plain wrong, that there is a better way, or that other approaches are simply that much better than yours.