AI-Assisted Development: How to Supplement Output Metrics with Review Friction

When AI productivity is measured by lines of code, the bottleneck may shift to review only when the work arrival rate or workload per review rises and overall load approaches or exceeds review capacity. GitClear’s analysis of 150 million changed lines shows a concurrent rise in code churn from 2020 to 2023, though correlation is not causation. This article examines why measurement standards should shift toward review friction and system-boundary control.

AI 輔助開發:如何用審查摩擦補足產出量指標

以產出行數衡量 AI 生產力,只有當工作到達率或單次負荷上升,且整體負載逼近或超過審查容量時,瓶頸才可能轉移至審查階段。GitClear 針對 1.5 億行變更的數據顯示 2020–2023 年代碼流失率上升的同期變化訊號(需注意關聯不等於因果)。本文探討為何衡量標準應轉向審查摩擦與系統邊界控制。

Toy Models of Superposition: Feature Compression in Neural Networks

Open your IDE. You observe a single hidden-layer neuron. It responds to both “Python” and “error handling.” This is not a bug; it is feature-level compression. Anthropic’s Toy Models research reveals how feature sparsity drives “superposition,” explaining how models store more concepts under capacity constraints.

Chinchilla: Model/Data Ratios on a Budget

When compute is limited, should you buy a bigger model or feed it more data? Chinchilla gave a counterintuitive answer in 2022: at a fixed training budget, a 70B model trained on 1.4T tokens outperformed a 280B model trained on 300B tokens, using the same compute. That points to an approximate 1:20 parameter-to-token ratio in that setup. If you’re planning an LLM training run, this paper offers a practical way to think about model size, data volume, and where your next dollar creates more learning.