AI moves programming's core from syntax to clarity, expanding the developer's role instead of ending it.
He argues the new programming language is clarity. Syntax is no longer the bottleneck; clarity is. Can you describe what you want, provide examples, set constraints, explain what good looks like, and test whether the result matches the intent? Communication becomes a technical skill, and diagrams, examples and shared understanding matter.
Yes, absolutely. Many things are taught because they shape how we think, not because everyone turns pro: essays, calculus, choir singing. Coding can be part of general education, like math, language and music, because it builds a certain kind of thinking. But how it is taught must change, since natural language becomes a programming interface.
AI makes mistakes. It will make fewer over time but never zero, and the last few percentages between almost correct and actually correct are expensive and valuable. People who truly understand code are needed not to write everything, but to know what is wrong: to debug, to verify, and to close that gap.
The problem is not that AI writes better code, but that it takes away the part many developers fell in love with. People who chose the career because they love building things with code now ask what is left for them. He says this resistance is not fear of technology; it is grief.
He feels neither fear nor grief; he has more fun developing software than in many years and feels powerful. Not because AI does the work, but because the distance between idea and reality has drastically shortened. It brings back the self-efficacy he felt as a teenager, the feeling that his ideas can change reality.
Programming languages were always abstractions that freed him from registers, memory addresses and machine code. AI is just another abstraction layer, a powerful one but still a tool. It does not replace what he does; it changes the level at which he does it, expands his role, and removes friction rather than creativity.
He does not think so. We still play chess although machines beat us, and still run, cycle and sail though engines are faster. Efficiency was never the point; experience was. Coding will stay because it trains precision, logic and patience, and one day handmade software might even be valued for being intentional.
Programming is the first frontier, the canary in the coal mine. Designers, writers, translators, lawyers, accountants, architects and doctors go through denial, fear, grief and redefinition. His answer: don't fight the tool, find the layer above it, like a designer as a visual thinker or a writer as a storyteller.
In 1987, as a teenager, he got a Commodore C128. He spent hours typing code from computer magazines line by line, and it mostly failed over a single typo. When it worked, like his first nested loop drawing patterns, it felt like magic, and he showed it to everyone, even typing it into store display computers.
He did not stop teaching, but stopped thinking of himself as someone who teaches syntax. He teaches agency, clarity, and the craft of turning ideas into reality across abstraction layers. He still loves coding, but no longer defines his professional identity by it: he is not just a coder, he is a developer.
“isn't AI making all these things meaningless?”
“The problem is that AI takes away the part that many of us fell in love with.”
“This resistance isn't fear of technology, it's grief.”
“Not the result, the process.”
“It doesn't shrink my role. It, in fact, expands it.”
“That's where people who truly understand code become incredibly valuable.”
“What to teach when AI writes the code | Rainer Stropek | TEDxLinz.” https://www.youtube.com/watch?v=yhGzXULZkEw. Transcript summary by WhipScribe, https://whipscribe.com/transcript-pages/what-to-teach-when-ai-writes-the-code-rainer-stropek-tedxlin.html.