Show the evidence.
Link to studies, protocols, code or first-party documentation; expose sampling limits and conflicting results.
AI-assisted programming is changing the way software gets made. We track the evidence, test the claims and keep the forecasts accountable.
Emerging software tools are presented through benchmarks, demos, survey responses and confident predictions. None of these sources answers every question. Our job is to identify what each can—and cannot—support.
Read the evidence protocol ↗New modes of authoring, assembling and maintaining software.
Explore research ↗02 / DOSSIERProgramming through prompts, generated code and iterative feedback.
Explore research ↗03 / DOSSIERNew divisions of labor between developers, reviewers and models.
Explore research ↗04 / DOSSIEREditors, command-line agents and integrated coding workspaces.
Explore research ↗05 / DOSSIERVisual, conversational, spatial and multimodal development interfaces.
Explore research ↗06 / DOSSIERBenchmarks, correctness, security and the limits of passing tests.
Explore research ↗07 / DOSSIERWhat should developers learn when code can be generated?.
Explore research ↗08 / DOSSIERProductivity, costs, maintenance and organizational change.
Explore research ↗09 / DOSSIERScenarios, indicators and claims that can be tested over time.
Explore research ↗10 / DOSSIERReplicable trials, methodological notes and critical perspectives.
Explore research ↗No matching research sections. Try a broader term.
One controlled trial measured slower completion. Newer investigations raise different questions. We examine why task selection, self-reports, and benchmark validity complicate the headline.
Read the evidence review ↗Numbers are from particular studies, not universal estimates. Read METR's update ↗
Link to studies, protocols, code or first-party documentation; expose sampling limits and conflicting results.
Separate observations, hypotheses and measurable forecasts. Record assumptions before outcomes are known.
Invite counterevidence, acknowledge corrections, and maintain a consequential public revision history.
Evidence first. Futures second.
ENTER THE OBSERVATORY ↗