问 HN：我们是否已经到了软件可以自我改进的阶段？
本文探讨软件是否已具备自我改进的能力。以库存管理系统Foo为例，设想一个机制，每隔24小时由编码代理分析日志、用户反馈、界面数据和数据库快照，结合业务目标文档，自动优化软件功能。核心在于通过持续的数据收集与分析，实现软件的自主迭代与提升。
1 分•作者: ManuelKiessling•大约 2 小时前
在这里发布这个想法，是为了听听你们是否认为这可行和/或有用，同时也想了解这是否已经是昨日新闻，大家早已在做了。
所以这里的核心内容是：想象一个面向用户的软件存在于世界上，执行它的功能。这个例子不需要太复杂，比如说一个叫做Foo的库存管理系统，每天被几百人使用。
现在想象你设置了一个类似“循环”的机制，运作方式如下：
每隔24小时，一个编码代理启动，提示如下：
“这是应用Foo的代码库。那边是Foo在过去24小时内产生的所有应用和系统日志。这边是过去24小时内发送到[email protected]的所有邮件。那边是Foo收集的所有用户界面数据：用户点击了哪里，滚动到了哪里等等。那边是Foo当前的数据库快照。这里是描述业务目标的文档……”
查看原文
Putting this out here to hear if you think this is feasible and/or useful, but also to find out if this is yesterday's news and everybody is already doing it.<p>So here is the gist of it: Imagine a user-facing software that is out there in the world, doing its thing. Doesn't have to be anything fancy for this example, let's say an inventory management system called Foo, used by several hundred people a day.<p>Now imagine you set up a kind of "loop" that works like this:<p>Every 24 hours, a Coding Agent launches, with the following prompt:<p>"Here is the codebase for application Foo. Over there are all application and system logs that Foo produced over the past 24 hours. Over here are all emails that went to [email protected] in the past 24 hours. Over here is all UI telemetry that Foo collected: where users clicked, where they scrolled to, etc. Over there is the current database snapshot of Foo. Here is the document that describes the business goals of Foo, and the basic limitations (legal, financial) in which it needs to operate.<p>This is your mission: analyze all these inputs, analyze the codebase — and then create Pull Requests with the three most pressing improvements that make Foo a better software for its users, based on your analysis."<p>Yes, there's a ton of details I'm glossing over, and yet: shouldn't something like this lead to some kind of fully automatic improvement of software Foo over time?