> Our company's full-time job is to shrink our customer's codebase size aggressively. Your team will not do that because it's a job security to them. No, they

> Our company's full-time job is to shrink our customer's codebase size aggressively. Your team will not do that because it's a job security to them. No, they did do that, that's where the layers of bloat originated from. Everything turns out to be not quite as generic as the authors thought and that helper function end up as it's own class with an inheritance tree, etc. That fancy mapper that uses reflection to eliminate hundreds of lines of boilerplate becomes a liability because information is now lost to future maintainers. I don't want less code, I want simple, greppable code that allows me to trace data across the codebase.