The Programmer Who Sleeps While AI Codes: Eric Schmidt’s Warning to the Industry

Eric Schmidt, the former CEO of Google, has a confession that surprises even him. He is grieving. Not for a lost colleague or a failed product, but for the end of a craft he mastered as a teenager. “I started as a programmer when I was basically 13 or 14, and that is essentially over,” he told a recent audience. His identity as a computer scientist, he says, vanished within his own lifetime. The Economic Times reported his remarks.

Schmidt’s words carry unusual weight. He has advised the Pentagon on artificial intelligence and backed multiple AI coding startups. When he tells programmers to stop writing code the old way, the industry listens. “If you’re writing code in any traditional way: stop. It’s over,” he declared.

His evidence is concrete. At one of his startups, an engineer writes a specification and a test function each evening at 7 p.m. Then he runs the system and goes to dinner with his wife. AI agents work through the night. By 4 a.m., they finish. The engineer reviews the results over breakfast. “This stuff would’ve taken me six months and 10 programmers at Google,” Schmidt recalled. “This poor guy’s sleeping.” The Times of India detailed the account.

That story captures the shift. The best programmers no longer write most of the code. They define success, set evaluation criteria, and manage fleets of AI agents. The machines handle implementation and debugging. Humans orchestrate.

Schmidt notes the transformation accelerated sharply around October 2025. Six months later, the gap between old practices and new ones had widened dramatically. Managers who still see engineers typing line by line should ask a direct question: “Why are you still writing code the way you did six months ago?”

Some developers remain skeptical. AI still hallucinates, struggles with novel architectures, and requires human oversight. Yet models already write 10 to 20 percent of code at leading labs. That share grows monthly. Schmidt’s advice for working engineers is blunt: stop writing code the traditional way. Learn to manage agents. Master the art of specification and evaluation. Those who adapt will widen their impact tenfold. Those who cling to the old identity may find their skills commoditized faster than expected.