Skip to main content

One post tagged with "engineering"

View All Tags

AI Doesn't Get Annoyed

· 9 min read
Omry Yadan
Software engineer and open-source maintainer

Compilers exist because humans got tired of writing machine code. What shared concepts will remain implicit when AI can generate the implementation forever?

The next compiler

Linus Torvalds made a comparison that I found useful. He objected to describing AI-assisted code as "written by AI." Compilers already generate all the machine code, but we do not ordinarily say that the compiler wrote the program. In his analogy, AI is another tool that changes how the programmer creates software, not necessarily who created it. His larger point was that the fundamentals still matter even as the tools change.

Compilers did not eliminate creativity in programming. They eliminated most of the need to be creative in machine code. Creativity moved upward, into algorithms, data structures, languages, interfaces, and systems.

AI may do something similar. The analogy is operational, not mechanical: AI is not a deterministic translator like a compiler, but it similarly lowers the cost of turning an intention expressed at one level into an implementation at another. It can make one person capable of acting across a much larger surface area.

But there is an important difference.

A compiler generates low-level instructions only after the program has been expressed in a higher-level formal language. The knowledge has already moved upward into a durable representation. AI can often generate a lower-level artifact directly from an informal request, without requiring a stable language, model, or interface to exist first. It can remove the low-level work while leaving the knowledge scattered across prompts, generated files, tests, conventions, and human memory.