Back to blog

DHH States: AI Programming Tools Still Do Not Compare to Junior Developers

Hello HaWkers, David Heinemeier Hansson (DHH), creator of Ruby on Rails and CTO of 37signals (Basecamp/Hey), made controversial statements about the current state of AI programming tools. According to him, despite all the hype, these tools still cannot replace even junior developers.

Let's analyze DHH's vision, the context behind these statements, and what this means for developers in 2026.

What DHH Said

The Full Statement

In a series of recent posts and interviews, DHH shared his perspective.

Main quote:

"AI programming tools are useful for autocomplete and quick suggestions, but they're still far from replacing the ability of a junior developer to understand context, ask the right questions, and learn from the codebase. AI has no code sense."

DHH's main points:

  1. AI is excellent at repetitive and predictable tasks
  2. Lacks business context understanding
  3. Generated code frequently needs extensive review
  4. AI cannot replace the ability to learn and evolve
  5. The hype is far ahead of current reality

The 2026 Context

The Current State of AI Tools

To understand DHH's perspective, we need to look at the landscape.

Popular tools in 2026:

Tool Function Price Adoption
GitHub Copilot Autocomplete $19/mo 85% devs
Cursor IDE with AI $20/mo 40% devs
Claude Code Autonomous agent $20/mo 35% devs
ChatGPT Code Assistant $20/mo 60% devs
Windsurf IDE with AI $15/mo 15% devs

What AI does well:

  • Autocomplete boilerplate code
  • Generate basic unit tests
  • Explain existing code
  • Convert between languages
  • Suggest simple refactorings

What AI still struggles with:

  • Understanding complex architecture
  • Making design decisions
  • Debugging subtle problems
  • Understanding business requirements
  • Maintaining consistency in large projects

DHH's Arguments

Why Juniors Are Still Valuable

DHH argues that junior developers bring something AI cannot.

1. Ability to ask questions:

Junior Developer:
- "Why are we using this pattern here?"
- "Does the client really need this feature?"
- "Could this break the existing system?"

AI:
- Generates code without questioning requirements
- Assumes the prompt is complete
- Has no context beyond what's provided

2. Learning and growth:

Junior Developer in 1 year:
- Understands the business domain
- Knows the codebase peculiarities
- Built relationships with the team
- Can mentor new members

AI in 1 year:
- Same capabilities as at the start
- Does not accumulate project knowledge
- Has no relationship with the team
- Always depends on detailed prompts

3. Code sense:

DHH coined the term "code sense" - the ability to intuit when something is wrong.

Scenario: Subtle performance bug

Junior Developer (after months on the project):
"This code seems slow... I'll investigate"
- Notices patterns that deviate from normal
- Connects with previous problems
- Seeks validation from senior team

AI:
"Syntactically correct code"
- Has no performance baseline
- Doesn't know bug history
- Has no intuition

The Other Side

Counter-arguments to DHH

Not everyone agrees with DHH. Some counter-arguments:

1. AI is evolving fast:

Benchmark 2024 2025 2026
HumanEval 72% 85% 91%
SWE-bench 12% 45% 67%
MBPP 75% 88% 94%
Real-world fixes 15% 40% 55%

2. Developers with AI are more productive:

GitHub 2025 Study:
- Developers with Copilot: 55% faster on repetitive tasks
- 40% less time on documentation
- 30% less time writing tests

But also:
- No significant difference on complex tasks
- 15% increase in subtle bugs
- Excessive dependency in some cases

3. Cost-benefit:

Junior Developer (USA):
- Salary: $60,000-80,000/year
- Benefits: ~$20,000/year
- Training: 3-6 months
- Full productivity: ~1 year

AI Tools:
- Cost: $240-480/year per dev
- Available 24/7
- No onboarding needed
- Immediate (limited) productivity

The Market Reality

What Companies Are Doing

Despite diverging opinions, there are clear trends.

Current scenario:

  • Companies continue hiring juniors
  • AI is used as a tool, not replacement
  • Focus on "AI-augmented developers"
  • Junior role is changing, not disappearing

Changes in junior role:

Junior 2020:
- Write basic code
- Fix simple bugs
- Learn from seniors
- Do initial code reviews

Junior 2026:
- Orchestrate AI tools
- Validate and refine generated code
- Understand and explain AI decisions
- Focus on business logic
- Learn to prompt effectively

Implications for Your Career

What Developers Should Do

Based on this debate, some practical recommendations.

If you're junior:

  1. Learn fundamentals first

    • Algorithms, data structures, paradigms
    • Understand WHY code works
    • Don't depend on AI to think
  2. Use AI as a learning tool

    • Ask for explanations, not just code
    • Question generated code
    • Compare different approaches
  3. Develop skills AI doesn't have

    • Stakeholder communication
    • Business domain understanding
    • Critical thinking and questioning
    • Team collaboration

If you're senior/lead:

  1. Mentor juniors in effective AI use

    • Teach them to validate generated code
    • Show when AI helps vs hinders
    • Encourage critical thinking
  2. Don't replace juniors with AI

    • Talent pipeline matters
    • Perspective diversity matters
    • AI doesn't grow in the company
  3. Establish clear guidelines

    • When to use AI
    • How to review AI code
    • Responsibility for bugs

The Future According to DHH

Predictions for Coming Years

DHH shared his expectations.

Short term (2026-2027):

  • AI continues improving on specific tasks
  • Juniors continue being hired
  • Role evolves but doesn't disappear
  • Hype begins to normalize

Medium term (2028-2030):

  • AI may automate more routine tasks
  • Juniors will need different skills
  • Focus shifts to supervision and validation
  • Salaries may change, but jobs remain

Long term (2030+):

"Honestly, I don't know. But if AI really replaces programmers, it will replace all of us, not just juniors. And in that case, we'll have bigger problems to solve as a society." - DHH

Conclusion

DHH's perspective is an important counterpoint to the excessive hype about AI replacing developers. While AI tools are useful and will continue to evolve, the human ability to learn, question, and understand context is still irreplaceable.

Key points:

  1. DHH believes AI doesn't replace even juniors yet
  2. AI tools are useful but have clear limitations
  3. Junior developers bring unique value
  4. The junior role is evolving, not disappearing
  5. Fundamentals and human skills remain essential

Recommendations:

  • Use AI as a tool, not a crutch
  • Invest in fundamentals and critical thinking
  • Develop skills that AI doesn't have
  • Follow evolution but don't panic
  • Focus on solving problems, not writing code

If you want to understand more about career in the AI era, read: Developer Career in the AI Era: Survival Guide.

Let's go! 🦅

Comments (0)

This article has no comments yet 😢. Be the first! 🚀🦅

Add comments