Shifts in programming practice should be traced through working systems and measured results—not product announcements.
New modes of authoring, assembling and maintaining software. Our purpose is to establish the evidence and questions needed for rigorous coverage, not to imply that a proposed future is inevitable.
Natural-language interfaces promise a different starting point for development, but a description of intent is not equivalent to a verified program. The questions are how intent is specified, how failure is surfaced, and who remains responsible for the result.
We distinguish interface changes from changes in underlying computing models. A chat-based editor is not automatically a replacement for structured languages, tests, compilers or code review.
Repeatable controlled evaluations; public version histories; integration into established software lifecycles; documented reversibility and maintainability.
Compare tools on matched tasks with recorded failure rates, setup time and reviewer effort.
These are starting references for future reporting, not proof that every open question above is resolved.
Edition 1.0 · 9 October 2026. Initial scope and source register created. This brief is a research framework, not a completed investigation; material future corrections should be described rather than silently overwritten.
How corrections are documented ↗