James Shore on measuring unintended consequences of AI programming: change costs and modeling approaches
Automated summary · Based on collected summaries; not individually verified
Prepared by HotAI
What happened
In the third part of his series, James Shore explains how to measure and model the unintended consequences of AI programming. The core metric is change cost, with value-added ratio being his most trusted indicator. The article presents models for maintainability and code churn, along with observation methods for lock-in and burnout. It warns that the value-added ratio is easily manipulated and should be used only to evaluate methodologies, not to assess individuals.
Reading notes
The event summary comes from collected excerpts. Background passages quote existing HotAI articles to explain terms and do not establish new facts about this event. Check the original sources for product results, conditions and subsequent updates.
Original source
Sources and collection timeline
| Source | Report title | Original publication time | Collected by HotAI |
|---|---|---|---|
| oreilly.com | James Shore on measuring unintended consequences of AI programming: change costs and modeling approaches | 2026-11-11 20:11 | 2026-11-11 20:37 |