I'm a student, working at my first job in the industry. We don't use a rubber duck here but I've been noticing companies using the "Rubber Duck Challenge" as incentive to remove as many LOC as possible. Is this practical?
Surely you'd want to remove only when necessary, I understand trying to refactor a legacy codebase to something more manageable, but usually (unless it's terribly written) removing lines by condensing things down only leads to harder legibility.
Can anyone who's used this method or has (more) experience in the industry throw their 2¢ in?
So, I think better design is the goal, and fewer LOC is a natural side effect. I personally find that essential for evolving a large project. Some managers are ok with ever-increasing tech debt, which I associate with increasing job dissatisfaction.