发现维护由编码代理创建的软件很有挑战性吗？
我们确实制定了适当的产品需求文档（PRD）、系统设计和实施计划，并将其提供给代理。<p>我是一名机器学习工程师（MLE）和软件工程师（SWE），所以并不是说我不能阅读代码或不知道任何合适的实践。不同之处在于，<p>由于我们不像之前的编码代理那样每天花6-8小时与代码库打交道，我们缺乏在出现错误时帮助我们缩小根本原因的深入知识和直觉，也不知道如何最好地扩展当前的代码库以支持新功能。<p>由于编码代理的生产力，代码库的规模和应用程序的复杂性相对于开发人员的数量也有所增加。现在每个开发人员都需要在更大的范围和更多的微服务上保持上下文和理解。随着时间的推移，这使得对应用程序和代码库的扩展进行审查在认知上变得越来越困难。<p>还有其他人也面临这个问题吗？这只是我们工程流程的问题吗？你们有什么有效的方法？
查看原文
We do have in place proper PRDs and system designs and implementation plans that we feed to the agent.<p>I'm an MLE and SWE, so it's not like I can't read code or don't know any proper practices. What is different though are that<p>Since we are not spending 6-8 hours a day working with the code base unlike pre-coding agents, we lack the indepth knowledge and intuition that helps us narrow down root cause when bugs arise, or know how to best extend the current code base to support a new feature<p>Because of the productivity from coding agents, the size of the code base and sophistication of the app relative to number of developers has also increased. Each developer now needs to maintain context and understanding over a greater surface area and number of micro services. Over time this makes reviewing extension to the app and code base increasingly more difficult cognitively.<p>Anyone else dealing with this too? Is it just a problem with our engineering processes? What works for you?