Jake Gold

Jake Gold

Building AI infra @ clor.com in SF Bay Area. Helped launch and scale Vibecode and Bluesky. Prev: Nuro, Docker, Google, founder. Addicted to history, computers, and open systems. Unconditional love for all conscious life.

Linus Torvalds was the first 1000x programmer

I’ve worked closely with hundreds of programmers over decades. There were always some people who were shockingly more productive compared to everyone else. Not in terms of typing code faster, although they often did write code faster. Mostly they just made better decisions, so their work compounded. They could move from project to project making huge improvements while also reducing tech debt.

Some people like to argue and even take offense at the idea of the “10x programmer” but I’ve seen it too many times to even care to debate it. Lots of 10x and 100x programmers exist, and at least one 1000x programmer.

Linus is the evidence of what’s possible

Linus Torvalds is the clearest example of a 1000x programmer.

The Linux kernel supports 21 CPU architectures and an enormous amount of hardware. It runs on billions of devices (Android, servers, TVs, cars, routers, etc).

The world does in some real sense run on Linux and one programmer has been in the technical details managing the entire codebase himself for decades.1

Linus is an extremely good programmer

Linus isn’t a manager who happens to run a big project. He’s an extremely good programmer who designed a system to scale up his ability to write large and complex software.

He wrote the first kernel by himself. When the kernel lost BitKeeper in 2005 he wrote Git in about two weeks. Given sufficient time, he could certainly write every single line of code in the Linux kernel himself.

That’s how good he is.

Linus parallelizes himself

Linus splits the kernel into subsystems, assigns a maintainer to each one, and works on all of them in parallel. Maintainers take patches, review them, and send him pull requests. He reads them, says yes or no, and merges.

His way of working was always impressive. He doesn’t have meetings. He chats over email, exchanges patches, gives design feedback, and says yes or no. This is how he describes his job:

I read email, I write email, I do no coding at all any more.

Remember, the reason this works is because Linus is an extremely good programmer. Because he could write any of it himself, he can review any of the code, and he can tell when a maintainer is wrong.

Linus was coding agentically before it was cool

If like many of us in 2026 you’ve been running coding agents in parallel, it’s not hard to see the analogy to how Linus has always worked. He sits at his computer chatting with subsystem maintainers, each one a high context session isolated to one modular piece of the codebase. He helps plan the work, gives feedback on patches, and merges what’s good.

Linus has been running “chat-based coding agents” over email since 1991.

Linus showed us the way

What made Linus the first 1000x programmer wasn’t just that he’s a really good programmer. There are lots of really good programmers in the world.

It was that founding something as important as Linux gave him the control and the resources to design the most effective way of working for himself.

No engineering manager at Big Tech would ever have approved of the way Linus works. No CTO at a small startup could’ve afforded it.

So now that any good programmer can work like Linus, expect a lot more 1000x programmers.

Hacker News


  1. None of this takes away from the thousands of kernel maintainers and contributors. The MAINTAINERS file alone lists roughly 2,000 people, and Linux is what it is because of their hard work. ↩︎