Thinking about today, you're going to keep a small fraction of your 10x employees, the ones who implement a feature a week and don't need to look back on code t

Thinking about today, you're going to keep a small fraction of your 10x employees, the ones who implement a feature a week and don't need to look back on code that just works; also you're going to keep juniors who have no idea what they're doing and write pages of inefficient code where a senior would make a library call. You're going to lose the 10x refactor wizards who delete more than they write, the firefighters who don't really change linecounts, and your 1x developers who think before they type. Might as well just give everybody a typing test. Thinking about tomorrow: this establishes a hilarious incentive. A nonzero fraction of people who know that this was the criteria will change their behavior to suit. More lines of code, you say? Coming right up! I've met some people who work / worked in shops where the number of commits per day was the ruling metric. The smart ones wrote scripts to carve their commits into plausible but small chunks.