Ask HN：你使用 Agentic Coding 的体验如何？
3 分•作者: grandimam•7 个月前
我最近深入地尝试了基于 Agent 的编码方式，这让我重新思考了构建软件的方法。
我注意到一个关键的区别在于前期成本。使用基于 Agent 的编码，我感觉前期成本更高：在模型开始生成代码之前，我必须先思考架构、约束和成功标准。我必须将我通常在脑海中保留的思维模型外化出来，以便 AI 可以使用它。
在“精确编码”中，前期成本很低，但这仅仅是因为我将大部分复杂性都放在了脑海里。所有的设计决策、边缘情况和上下文假设都存在于我的头脑中，伴随着我的代码编写。测试更像是一个最终的验证步骤。
我意识到的是，基于 Agent 的编码将我的认知负荷从即时执行转移到更预先规划的执行（我更像一个研究人员而不是一个黑客）。我的角色不再是“精确地”实现每一段逻辑，而是更清晰地定义问题空间，以便 Agent 能够可靠地组装解决方案。
另一个观察是，由于编写代码的成本很低，因为 Agent 被委托编写代码，我需要转变角色和上下文，并承担起 QA 的角色来评估 Agent 的输出。
很想听听你的想法？
查看原文
I have been experimenting more deeply with agentic coding, and it’s made me rethink how I approach building software.<p>One key difference I have noticed is the upfront cost. With agentic coding, I felt a higher upfront cost: I have to think architecture, constraints, and success criteria before the model even starts generating code. I have to externalize the mental model I normally keep in my head so the AI can operate with it.<p>In “precision coding,” that upfront cost is minimal but only because I carry most of the complexity mentally. All the design decisions, edge cases, and contextual assumptions live in my head as I write. Tests become more of a final validation step.<p>What I have realized is that agentic coding shifts my cognitive load from on-demand execution to more pre-planned execution (I am behaving more like a researcher than a hacker). My role is less about 'precisely' implementing every piece of logic and more about defining the problem space clearly enough that the agent can assemble the solution reliably.<p>Another observation has been that since the cost of writing code is minimal as agents are delegated to write them, there is a need for me to shift and context and also take up the QA role to evaluate the agents output.<p>Would love to hear your thoughts?