AI 正在改变开发者工作,GitHub 给出三项应强化的技能
AI is changing developer work. Here are three skills to strengthen.
GitHub 提出开发者应强化三项技能:学会指挥 AI 智能体而非只是使用它,不轻信 AI 的第一个答案,以及用 AI 节省的时间去解决更大的问题。文中提到 GitHub Copilot 内置的 Rubber Duck agent 会用第二个模型来审查计划、代码和测试。
正文
当前显示原文,中文全文译文尚未就绪。
AI is changing how developers work and apply their skills. Writing code is still essential, but developers increasingly need to know how to direct AI, evaluate its output, communicate tradeoffs, and make sound technical decisions.
The good news? You can start preparing today. Here’s where to focus:
Tip #1: Learn to direct AI, not just use it.
AI is changing what execution looks like. Increasingly, great execution means defining the problem clearly, providing the right context, evaluating AI-generated code, and deciding what’s ready to ship. As AI agents take on more of the implementation, these skills become even more valuable.
For example, imagine you’re asked to add a new authentication flow.
A traditional workflow might look like this:
As AI tools become more capable and more deeply integrated into day-to-day workflows, those same skills can help you coordinate multiple AI agents. Your workflow might look more like this:
Notice what changed. You’re still responsible for the outcome, but you’re spending less time implementing every piece yourself. Instead, you’re defining the work, reviewing outputs, and making the technical decisions that bring everything together.
Takeaway: Learn to direct AI agents.
Start your first agent session >
Tip #2: Don’t trust AI’s first answer
AI can generate impressive solutions in seconds, but the first answer isn’t always the best. Your experience writing clean, maintainable code can help you evaluate AI’s output.
Ask a second AI model to critique the first model’s work, then use your own judgment to evaluate both responses.
Here’s a prompt that shows what that might look like in practice:
Different AI models have different strengths and blind spots. That’s why GitHub Copilot’s built-in Rubber Duck agent uses a second model to critique plans, code, and tests before you move forward. A second perspective often catches issues the first model misses.
Takeaway: Trust AI enough to use it but not enough to skip review.
Tip #3: Use AI to solve bigger problems
When AI saves implementation time, developers can use that time to tackle broader problems: understanding customer needs, evaluating tradeoffs, designing better systems, and making technical decisions that AI can’t make for them.
For example:
As AI takes on more implementation work, the skills that distinguish great engineers become even more important: exercising sound judgment, balancing tradeoffs, and solving the right problems.
Takeaway: Let AI handle more of the implementation so you can spend more time building the judgment that helps teams make better decisions.
The bottom line
As developer workflows evolve, learning to work effectively with AI—and strengthening your own technical judgment—can help you adapt.