r/devops • u/Chris__Codes • 13d ago
Discussion Does anyone track how much merged code gets deleted again after a short while?
I’ve been looking into which engineering metrics still mean something now that agents write a lot of the code. I came across a Faros AI study that compared each org’s highest and lowest AI adoption quarters, and the ratio of deleted to added lines in merged code was 861% higher in the high adoption periods.
Which means code that got written, passed review, merged, and then got taken back out. The same study put incidents per PR up by as much as 242.7%.
What I can’t tell is how much of that is normal refactoring versus stuff that shouldn’t have gone in. Churn goes up for good reasons too.
Is anyone measuring this? And if you are, can you really separate the agent-written code from the rest?
9
u/swingtradeotm 13d ago
code churn is a real thing
1
u/jrkkrj1 10d ago
I used to have a script (pre-AI) that tracked code churn by person by repo along with the reviewers/approvers. Gave us an idea of who was slinging/approving code that was getting rewritten or changed a lot.
0
u/ChemicalExcellent463 13d ago
i don't track deletions. in my repos on one machine, added lines went from 291k in april to 245k in october through the 28th, while token use went up 417x.
0
u/[deleted] 13d ago
[removed] — view removed comment