All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Why measuring AI-assisted coding by lines of code is a flawed metric

By

David Curlewis

1d ago· 8 min readenOpinion

Summary

The article argues against using vanity metrics like lines of code, PR counts, and commit frequency to measure developer productivity, especially in the context of AI-assisted coding. It draws a parallel between the industry's past lessons (learning that LOC is a poor metric for human developers) and the current trend of applying similar flawed metrics to AI-generated code. The author advocates for outcome-based measurements—what actually ships, what it does for customers, revenue, and reliability—rather than volume-based vanity metrics.

Key quotes

· 3 pulled
Lines of code, PR counts… we spent a couple of decades learning these are stereotypically bad ways to measure a developer.
One of them writes 40% more lines of code than the other. Is that developer better? More impactful for the business?
You'd want to know what actually shipped. What it did for customers, for revenue, for reliability.
Snippet from the RSS feed
A case against measuring AI-assisted engineering by code volume and other vanity metrics instead of outcomes.

You might also wanna read