请问HN：在微服务中如何进行代码协作而不破坏一切？
上周，我们让一个AI代理在一个服务中重命名了一个字段。结果导致另外三个服务在生产环境中出现了故障。由于这些依赖关系并不在代码中，而是在某个人的脑海里，审查时没有人发现这个问题。
我所在的公司正在推动我们在开发人员更少的情况下交付更多的产品，我们都在使用Claude Code。这在单个服务内的开发速度上确实很惊人。但是在微服务的环境中，这就像把电锯交给一个看不见墙壁的人。AI的速度远远超过了团队追踪依赖关系的能力。
你们是如何应对这个问题的？还是大家在部署之间只是祈祷？
查看原文
We had an AI agent rename a field in one service last week. Three other services broke in production. Nobody caught it in review because the dependencies aren't in the code, they're in someone's head.<p>My company is pushing us to ship more with fewer devs, we all use Claude Code. And it's amazing for velocity within a single service. But microservices? It's like giving a chainsaw to someone who can't see the walls. AI moves way faster than your team's ability to trace what depends on what.<p>How are you dealing with this? Or is everyone just praying between deploys?