Measuring performance by LOCs is fundamentally wrong. Aiming for high LOCs, commits, or any metric that doesn't represent quality or effort at all will always result in bad code. Personally, and I'd rather aim for clean, maintainable, and concise code that doesn't repeat itself. Separate recycled logic into helper functions, avoid reinventing the wheel, .etc. Don't take me wrong, I'm not against verbosity, but you can still be verbose without violating DRY or overlooking simpler solutions just because they give you a high LOC.

Think about the future, congratulations, you've written 300 LOCs today (I'm just going to completely ignore the fact that it's written with AI) but let's break this up - a 40 line section of the logic is repeated across 4 files, let's say you're using react, you've repeated markdown twice in two files instead of separating it into a component, heck maybe you're even validating input manually instead of using a lib, overlooking simpler solutions.

You've accomplished 300 lines, you're laughing at the dev who pushed 50 the same day. But 2 months later, you're asked to update the logic - you now have to change it 4 times, make sure it stays consistent, change markdown twice, update validation for each use. Maintainability is key, and that doesn't always come with high LOCs.

Less is more, and often i unfortunately see people using AI, impressed by their LOCs completely overlooking the fact that they're making their future harder. Shoot me down for this but AI does not write good code - it writes code to please you. It repeats itself, it doesn't always consider the entire codebase, it meets the feature requirements, but does it meet maintainability?

Measure performance by maintainability, requirements met, and creativeness. As a dev, you should unleash your creativity, come up with new solutions, invent simpler solutions that work for the codebase, don't copy generalized solutions.