Ask HN：我每天都在使用编码代理，但真正的工程师是如何使用它们的？
1 分•作者: getlawgdon•3 个月前
我拥有广泛但不够深入的技术背景（长期担任管理顾问），并且在自己的项目中广泛使用代理（VS Code 中的各种服务和模型）。我知道自己正在遇到瓶颈。我的工作流程很初级，不专业，需要大量的摸索和努力来生成代码、处理上下文漂移、手动修复等。
我想了解资深工程师是如何对待这些工具的。他们的流程、系统、保障措施、必做事项等。
如果您靠写代码为生，并将代理融入了您的工作流程，那么您的系统是什么样的？
任何/所有输入都欢迎：资源、网址、大纲、警告、发现、建议。
以下内容并非必需，但有一些想法？
- 您如何构建一个全新的项目？脚手架、git init/ignore？仓库？初始提交策略？如何将不想包含在上下文窗口中的内容排除在外？
- 您如何“分层”您的工作，使其更多地关注上下文和结构的完整性，而更少地关注提示？
- 您会切换模型吗（频繁地？偶尔地？）？为什么？
- 除了基本的代理/环境，您还有哪些其他工具？
- 我有哪些“专业习惯”没有，但应该养成？
- 对于在高度领域特定的工作中如何提高代理在该领域的实用性，有什么建议吗？
查看原文
I have a broad but shallow technical background (longtime management consultant) and use agents (a variety of services and models in VS Code) extensively for my own projects. I know I'm hitting a ceiling. My workflow is naive and nonpro, a lot of tinkering and bashing my way through code generation, context drift, manual fixes, etc.<p>I want to learn how senior engineers treat these tools. Processes, systems, guardrails, must-dos, etc.<p>If you write code for a living and have integrated agents into your workflow, what does your system look like?<p>Any/all input is welcomed: resources, URLs, outlines, warnings, discoveries, recommendations.<p>None of these are specifically needed, but ideas?<p>-How do you structure a brand new project? Scaffolding, git init/ignore? Repos? Initial commit strategies? How do you keep stuff out of the context window that you don't want in it?<p>-How do you "layer" your work so it's much more about the context and integrity of the structure and much less about prompts?<p>-Do you switch models (often? ever)? Why?<p>-What other tooling do you have alongside basic agents/environments?<p>-What are "pro habits" that I don't have and should?<p>-Any suggestions for how to work in a very domain-specific endeavor to try to increase the utility of the agents for a silo like this?