请问HN：如何向团队介绍Claude Code？
我负责一个小型软件工程师团队，团队成员包括一位有30年行业经验的资深工程师、一位刚入职的初级开发者，以及一些中级到高级的工程师。我们一直在使用像集成在IDE中的Copilot建议或ChatGPT这样的AI工具，并在我们的产品中使用OpenAI API来提供助手体验，但作为一个团队，我们还没有使用过编码代理。
最近，我通过一位朋友的介绍了解到了Claude Code。他辞去了工作，完全独立构建一个新产品，充分利用Claude的优势。这对我来说是一个觉醒的时刻：当好好利用这些工具时，生产力的提升是相当惊人的。我一直在密切关注这个领域，但在半年前尝试了早期的Cursor之后，我并没有考虑真正使用编码代理。最近几周，我在一个已经停滞多年的开源宠物项目上取得了巨大的进展。因此，我意识到我必须让我的团队学习使用Claude Code，最终提高开发速度——这是公司其他部门反复提到的一个抱怨。
然而，我在思考如何正确引导团队时感到困惑：我不想失去一个需求非常多样化团队的支持，也不想让资深工程师对工作完全改变感到沮丧，或者让初级工程师在一个他们无法理解或有效使用的黑箱中摸索。越是思考，我越意识到开发流程的根本变化：从设置Claude来预筛选GitHub问题并在开始之前制定计划，到处理那些长期存在但繁琐的任务，关于我们能做什么以及如何工作的规则完全改变了。
现在我认为我并不是唯一经历过类似故事的人，我想知道你是如何向你的工程师介绍编码代理的？你有没有阅读推荐或建议来帮助人们入门？对此我非常感激任何建议。
查看原文
I am responsible for a small team of software engineers, including an industry veteran of 30 years, a junior developer on their first job, plus a view mid-level to senior folks. We have been using AI tools like IDE-integrated Copilot suggestions or ChatGPT, and are working with the OpenAI API in our product for assistant experiences, but did not (as a team) use coding agents yet.<p>I recently got introduced to Claude Code by a friend who quit their job to build a new product entirely on their own, by leveraging Claude to maximum effect. So that was kind of an awakening moment for me: The possible gains of productivity when putting it to good use are pretty incredible. I had been following the space closely, but after my experiments with early Cursor half a year ago, I didn't consider really working with coding agents. The last weeks, I did make massive progress on an OSS pet project of mine that has been stalling for years. So at this point, I realised I'll have to onboard my team at work to Claude Code, and finally improve on development velocity—the one, recurring complaint from the rest of the company.<p>However, I am wondering how to do this properly: I don't want to loose buy-in from a team with very diverse needs, and risk leaving either seniors frustrated with their job changing completely nor juniors playing with a blackbox they have no chance of understanding, or working with effectively.
The more time I spend thinking about it, the more I realise how fundamental development processes change now: From setting up Claude to pre-screen GitHub issues and make a plan before we even start, to addressing all those long-standing but tedious tasks that have been laying around forever, rules for what we can do and how we work have changed entirely.<p>Now I think I am not the only one who experienced some variation of this story, and I want to know how you introduced your engineers to coding agents? Do you have reading recommendations or tips to get people started? I'm grateful for any advice here.