Don't Be John Henry

AI comes in second, losing to an exhausted developer.
August 14, 2025

In July 2025, Polish programmer Przemysław Dębiak spent 10 hours coding against OpenAI's AI model at the AtCoder World Tour Finals. He won by 9.5%. His condition afterward? "Completely exhausted" and "barely alive."

We've heard this story before.

The Legend That Warns Us

John Henry was a steel-driving man in the 1870s. When a steam-powered drill threatened to replace human workers, he challenged the machine to a contest. Armed with two 20-pound hammers, he worked for hours under the mountain.

He won. Then he died, hammer in hand, heart given out from the superhuman effort required to beat the machine.

The AI Wasn't Running at Full Capacity

The AI wasn't even running at full capacity. OpenAI's model was deliberately compute-restricted to make the competition "fair" for humans. Even handicapped, it demolished the other top 10 programmers in the contest—Dębiak was the only human who managed to stay ahead.

Think about that. A deliberately slowed-down AI still outperformed 9 out of 10 of the world's best competitive programmers. The one human who "won" had to operate on extreme sleep deprivation and push himself to complete exhaustion.

The Uncomfortable Truth

If you were competing against an unrestricted AI system today, you would lose. Decisively.

What Are You Really Fighting For?

John Henry's story resonates because it captures our desperate desire to prove our worth against machines. But here's the question that should keep you awake: Are you John Henry?

Are you the developer burning yourself out trying to prove you can still code faster than machines? Working 80-hour weeks while refusing to touch AI tools because you need to prove your human worth?

The future is already here. It's just wearing training wheels.

When those come off, what then?

The railroad industry didn't stop when John Henry died. It accelerated. The workers who disappeared were those who kept trying to out-muscle the machines.

Don't be John Henry.

Sources:

Exhausted man defeats AI model in world coding championship - Ars Technica

User Interviews: Discovering Genuine Needs Instead of Rebuilding the Same Old Tools

When building an entirely new digital experience, it’s tempting to focus on replicating the best features of existing tools.
Best Practices
Jul 10

Enhancing Developer Ergonomics: A Full-Stack Inclined, Local-First Approach

Reducing friction and streamlining workflows are critical in today's fast-paced development environment.
Teams
Jul 8

The Power of a Flexible Team: Why Variability in Staffing Matters

A flexible team structure allows businesses to scale up or down based on project needs, ensuring efficiency, cost-effectiveness, and faster delivery. By embracing variability in staffing, companies can optimize expertise at every phase, accelerate development, and maintain agility in an ever-changing market.
Teams
Mar 2

Accessibility: What It Means to Be WCAG Compliant and Why It Matters in 2024

In 2024, accessibility is no longer optional, it's essential.
Best Practices
Mar 2

The Power of Fractional Leadership

Top technical leaders thrive when they're laser-focused on delivering extreme value.
Teams
Oct 2

Why You Need a Fractional CTO

A fractional CTO gives growing businesses access to top-tier experience and strategic guidance.
Teams
Oct 3

To Promote Or Not Promote

Promoting a strong developer or director to CTO in hopes they'll grow into the role can backfire if they lack strategic perspective.
Teams
Oct 1

AI in Software Development in 2025

Artificial Intelligence (AI) has profoundly changed the landscape of software development.
Best Practices
Feb 20

Choosing the Right Near-Shore Team

Near-shore software development has emerged as a smart and strategic choice for tech startups and small businesses.
Outsourcing
Mar 2