请问HN：我每天都在使用编码助手，但真正的工程师是如何使用它们的？
我有一个广泛但浅显的技术背景（长期担任管理顾问），并在自己的项目中广泛使用代理（在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?