Agree 100%. At my company we have some OKRs that involve reducing code size by a certain percentage. We do some rough measurement before of what we can reduce.

Agree 100%. At my company we have some OKRs that involve reducing code size by a certain percentage. We do some rough measurement before of what we can reduce. So far we've been doing good. Most of our bloat is due to duplication (literal copy and paste) of UI components and patterns. And also to hasty architectural decisions, especially around error handling. Other than that, there is a general attitude of removing unpopular features that cause more trouble than they're worth, or at least moving them to totally separate services.