问HN：你会“微管理”你的代理吗？
我最近开始将人工智能编码助手融入我的日常工作流程中（特别是在使用Cursor Composer、Devin和Claude Code时），我注意到自己行为中出现了一种奇怪的模式。
我对待这些助手的方式就像对待最糟糕的微观管理者。
当我与一位人类初级开发者合作时，我会尽量提供“为什么”的解释和高层次的架构，然后给予他们解决问题的自主权。如果我在他们身后盯着，逐个指示每个变量名，在每个逻辑分支完成之前就进行评论，并不断打断说“不是，应该这样做”，他们（理所当然地）会在一周内辞职。
然而，与助手合作时，我发现微观管理实际上是最佳策略。
* 我将任务细分为原子单位。
* 我逐块审查代码，而不是按功能审查。
* 我实时不断纠正标准库的选择或变量命名约定。
我感觉自己在侵占助手的空间，而我本应信任它并让它自由发挥。这有时也打破了任务之间的分离。
让我更加不安的是，这种微观管理带来的心理负担和与我在管理方面所受训练之间的内心冲突。
所以我想问你：
你会对你的助手进行微观管理吗？
或者，最佳实践是什么？
查看原文
I’ve recently started integrating AI coding agents into my daily workflow (specifically when using Cursor Composer, Devin, Claude Code), and I’ve noticed a strange pattern in my behavior.<p>I treat the agent like the worst kind of micro-manager.<p>When I work with a human junior developer, I try to provide the "why" and the high-level architecture, then give them autonomy to solve the problem. If I stood over their shoulder dictating every variable name, commenting on every logic branch before it was finished, and constantly interrupting with "no, do it this way," they would (rightfully) quit within a week.<p>However, with the agent, I find that micro-management is actually the optimal strategy.<p>* I break tasks down into atomic units.
* I review code block-by-block rather than feature-by-feature.
* I constantly course-correct standard library choices or variable naming conventions in real-time.<p>And I felt that I am intruding the space of my agents while I should have just trust and let it build. It also sometimes break the seperation of tasks.<p>What makes me further unsettled is the kind of mental drain and internal conflict with what I have been trained in management.<p>So my question for you is<p>Do you micro-manage your agent?<p>or what's the best pratice?