Gwen Davis
Gwen Davis is a senior content strategist at GitHub, where she writes about developer experience, AI-powered workflows, and career growth in tech.
AI is changing what it takes to stand out—and move forward—as a developer. 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:
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:
Task: Add authentication
→ Create branch
→ Write code
→ Run tests
→ Open pull request
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:
Workspace: Add authentication
Agent 1 ✓ Authentication ready for review
Agent 2 ✓ Documentation draft ready
Agent 3 ✓ Test suite ready
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 >
AI can generate impressive solutions in seconds, but the first answer isn’t always the best. The years you’ve spent in school learning to write clean, maintainable code are exactly what will 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:
"Write a SQL query that returns each customer's most recent order."
↓
AI Model #1
✓ Generates the query
↓
AI Model #2 (Critique)
⚠ Doesn't handle duplicate timestamps
⚠ Missing index recommendation
⚠ May perform poorly on large tables
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.
Perhaps AI’s biggest benefit is that it gives you more time to think. The developers who grow the fastest will use that time to solve bigger problems: understanding customer needs, evaluating tradeoffs, designing better systems, and making technical decisions that AI can’t make for them.
For example:
Issue #4821
Title: Add dark mode
AI
✓ Build implementation
✓ Generate tests
✓ Update documentation
Developer checklist
☐ Validate customer problem
☐ Review architectural tradeoffs
☐ Check accessibility
☐ Define success metrics
☐ Approve solution
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 skills that launch careers are evolving. If you learn to work effectively with AI while strengthening the judgment AI can’t replace, you’ll be well positioned to thrive as a developer.
Describe the interface you need in plain English, then let the agent build a live surface you can both use and update—so you spend less time adapting to tools and more time getting work done.
What is a developer to do when they need something more tangible than a chat box? Enter canvases.
In this blog post, I explain how to use the new fuzzing taskflow based on the GitHub Security Lab Taskflow Agent AI framework.