📚 Open Source Wrote the Textbooks AI Learned From

Fri, 28 Aug 2026 11:00:00 -0500

We owe the open source community more than we usually credit for how good AI has gotten at writing software.

Here’s a theory that matters more as we move from asking LLMs to generate snippets to asking agents to build real systems:

An LLM didn’t independently discover what good software architecture looks like. It learned patterns from an enormous body of code written, reviewed, refactored, tested, documented, and maintained by developers over decades. Which means the quality of those examples matters.

Better Code In, Better Code Out

Research backs this up. One study found that removing low-quality code from training data cut quality problems in the model’s output significantly, without hurting functional correctness. Better code in, better code out.

That makes me wonder whether mature enterprise ecosystems have an underappreciated advantage in the agentic era.

Java’s Quiet Advantage

Take Java. Decades of professionally maintained open source projects have reinforced patterns around interfaces, dependency injection, domain boundaries, testing, error handling, package structure, API design, and backwards compatibility. The language then adds another layer of constraint through static typing and compilation.

Those constraints matter to AI too. Type-constrained decoding has been shown to cut compilation errors by more than half. Giving coding agents compiler feedback has produced similarly dramatic jumps in how often they generate valid code.

Not Java Versus Python

This isn’t “Java good, Python bad.” Python is one of the richest languages in current training data and performs extremely well on code-generation benchmarks.

My hypothesis is narrower: the more a language and its ecosystem encode decades of professional engineering constraints, conventions, and high-quality examples, the more structure an LLM has to imitate — and the more we can mechanically verify what it produces.

That starts to matter a lot more once the goal stops being “generate a function that passes a test” and becomes “build software another team can safely operate, modify, and maintain for the next twenty years.”

They Wrote the Textbooks

Which means every developer who spent years maintaining Apache projects, Spring libraries, compilers, frameworks, and testing tools contributed something bigger than they probably realized. They didn’t just build software for us. They helped write the textbooks our machines learned from.

So next time you’re working in a scripting language that never had to earn its keep in the enterprise — never got dragged through code review, backwards-compatibility guarantees, and a decade of production incidents — and you’re wondering why your agent keeps producing code nobody can maintain, that might be your answer. Try one of the languages the open source community spent decades hardening for exactly that job.

And thank your contributors while you’re at it.

Open-Source on David Parry

📚 Open Source Wrote the Textbooks AI Learned From

Better Code In, Better Code Out

Java’s Quiet Advantage

Not Java Versus Python

They Wrote the Textbooks