问HN：你们是如何处理Vibe编码和维护的？
嗨，HN，
现在人工智能能够生成代码，我在思考使用人工智能或进行“氛围编码”的每个人是如何考虑维护问题的。
软件不可避免地会因为弃用、更新、安全建议等原因而出现故障，而现在软件、应用程序、网页应用和SaaS的生成变得相对简单。
软件的技术债务迅速增加（添加API、数据库、分析、功能、更多库、更多文件、更多代码路径等），因此软件出现故障的可能性也随之增加，尤其是在“氛围编码”流行的情况下。
大家对此是怎么考虑的？
你们只是让ChatGPT、Claude和其他大型语言模型“修复代码”，然后祈祷一切顺利吗？还是在添加单元测试和集成测试或者其他措施？
谢谢！
查看原文
Hi HN,<p>Now that AI is able to generate code, I was thinking about how everyone who is using AI or is vibe coding is thinking about maintenance.<p>Software inevitably breaks with deprecations, updates, security advisories, etc, now and that with software, apps, web apps and SaaS's being easy to generate.<p>The technical debt of the software increases quickly, (adding APIs, databases, analytics, features, more libraries, more files, more code paths, etc) so the likelihood of the software breaking also increases, especially with vibe coding being popular.<p>How is everyone thinking about this?<p>Are you just prompting ChatGPT, Claude and other LLMs to just "fix the code?" and crossing your fingers? or you adding unit and integration tests or something else?<p>Thanks!