Unverified50% confidenceFactExact time
Code churn is the rate at which recently merged code is rewritten or reverted within two weeks of being committed.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe report's authors compared code written directly by humans with agent-written code in the same month and the same directories, concluding that there was no difference in the proportion of code lines later deleted or rolled back.65% similarUnverifiedFor repositories newly added to Code Review, the default trigger is to review after every push, and the cost multiplies with the number of pushes.63% similarUnverifiedInternal research at Google shows that the average update delay for documentation corresponding to code changes exceeds two weeks.63% similarUnverifiedThe refresh function in this article directly modifies the fields of the Report object (in-place update); in many production systems, the safer approach is to return a new report object, keeping the old version as an immutable snapshot, thereby supporting rollback, comparison, and concurrent reads.61% similarUnverifiedWhen updating a document, a delete-then-insert strategy at the document level is more reliable than chunk-by-chunk comparison updates, because under fixed-length chunking, modifying the beginning of a document causes all subsequent chunk boundaries to shift.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1069209API
curl https://kongchang.com/api/v1/knowledge/claims/1069209MCP
get_claim(id=1069209)