展开讨论

经验与复盘编辑摘编

AI 写 PR,小步修改仍然重要

Supermancho 提供了另一种 AI 开发体验:继续做小改动、自我审查,通过团队评审统一约定。他们也用 AI 清理重复实现。生成代码之后的协作流程,同样值得关注。

原文节选

“I don't understand this slop debt either. I make lots of small changes, as I did before, alongside self-reviews. This time, the AI puts”

阅读完整原文
源讨论Slop Debt
讨论

这条内容在回应什么?

父级讨论 · 原文节选

PR

I don't know. We've managed to avoid most of this, I think. We have tech debt, but it feels more like regular tech debt than sloppy engineering practices. What's worked for us: - Very strict linting, type checking, and so on. - An opinionated flow of data and clear layers in the codebase. - Good code review workflows with multiple AI code reviewers, along with a pretty opinionated SDLC. - Agents that look for duplication and opportunities to simplify. - Strong opinions about our core data model. I really think that the companies that are struggling with slop probably struggled with slop before. It just moved slow enough that things could be f…

完整原文

社区评论 0

还没有社区评论,来聊聊你的看法。

原讨论中的回复 0

仅展示本次导入中包含的直接回复,原文节选。

本次样本未包含直接回复,可以前往 Hacker News 继续阅读。

在 Hacker News 阅读

尊重不同观点,分享具体经验。

登录后即可发帖、评论、转发和引用。