arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~

它不再是我的代码

It Is Not My Code Anymore

Augusto Camargo

arXiv 2609.09022首次发表:更新:

发表机构

Institute of Mathematics, Statistics and Computer Science (IME); University of São Paulo(数学、统计与计算机科学研究所; 圣保罗大学)

机构由 AI 辅助整理,请以论文原文为准。

AI 中文总结

本文通过假设案例和文献分析,探讨AI辅助编程中代码生成者、所有权与责任归属问题,提出以服务结果为导向的验收标准及评估框架。

AI 中文摘要

AI辅助编程引发了关于谁生成代码、谁对其拥有所有权以及当代码失败时谁负责的独特问题。本研究笔记通过一个假设的注册失败案例和对相关文献的选择性阅读来审视这些区别。识别有缺陷表达式的生成者本身并不能确定审查者、发布决策者或服务运营者的职责。集体所有权同样将这些职责留待具体规定。随后,讨论考虑了质量工程如何评估生成的实现以及产生这些实现的过程。验收标准应由所需的服务结果来证明其合理性,组件检查为该结果提供证据。这一视角还允许与执行任务但不生成单独程序的系统进行比较。这种替代将改变作者身份的对象,同时保持服务义务不变。本笔记未报告新的实证结果;它提出了针对AI辅助软件生产的区别和评估问题。

英文摘要

AI-assisted programming raises distinct questions about who produces code, who feels ownership of it, and who is responsible when it fails. This research note examines these distinctions through a hypothetical enrollment failure and a selective reading of the literature. Identifying the producer of a defective expression does not, by itself, determine the duties of reviewers, release decision-makers, or service operators. Collective ownership likewise leaves those duties to be specified. The discussion then considers how quality engineering can evaluate both generated implementations and the processes that produce them. Acceptance criteria should be justified by the required service outcome, with component checks contributing evidence toward that outcome. This perspective also permits comparison with systems that perform a task without generating a separate program for it. Such substitution would change the object of authorship while leaving the service obligation intact. The note reports no new empirical results; it proposes distinctions and evaluation questions for AI-assisted software production.

Comments7 pages, 2 figures, 1 table. Research note

论文原文

arXiv 摘要页 · PDF 原文 · HTML 原文

↑