Recording intelligenceAI-generated brief · check the source for context

What to teach when AI writes the code | Rainer Stropek | TEDxLinz

18:19 recording · AUTO · 1 speaker

Watch the original

Executive Summary AI
  • Leonardo Silva opens with an evening at his desk preparing coding exercises for the students he mentors in his spare time, when the thought struck him that AI might be making all of it meaningless.
  • He traces the feeling back to 1987, when as a teenager he got a Commodore C128, typed programs from computer magazines line by line, and even demonstrated his nested-loop pattern program on display machines at the Hartlauer in the old Pluskauf.
  • He argues the resistance among experienced developers is not fear of technology but grief, like a carpenter watching a robot do the same work faster and without breaks: what is lost is not the result but the process.
  • Working with AI every day, he instead feels powerful because the distance between idea and reality has shortened, which made him realise he was in love with developing rather than coding, and that AI is just another abstraction layer like the programming languages that freed him from registers and machine code.
  • He concludes that programming is only the first frontier, with designers, writers, lawyers, accountants and doctors facing the same identity question, and that the thesis to remember is that the new programming language is clarity, so he now teaches agency and clarity rather than syntax.

Brief overview

AI moves programming's core from syntax to clarity, expanding the developer's role instead of ending it.

  1. The resistance to AI is grief, not fearDevelopers are not afraid of the tool; they are mourning the process they fell in love with, like a carpenter replaced by a robot.
  2. AI is another abstraction layer, not a replacementJust as languages freed him from registers, memory addresses and machine code, AI changes the level at which he works instead of shrinking his role.
  3. Clarity is the new bottleneck in every professionSyntax is no longer the constraint: describing intent, giving examples, setting constraints and testing the result is now a universal requirement, from lawyers to designers to managers.

Questions this recording answers

10 questions, each answered where it is said
If AI writes code, what does the speaker say the new programming language is?

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.

Does it still make sense to learn coding without AI?

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.

Why will people who truly understand code still be valuable?

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.

Why do experienced developers resist AI coding tools, according to the speaker?

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.

How does the speaker feel working with AI every day?

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.

How does the speaker see AI in relation to programming languages?

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.

Will coding disappear if machines can do it better?

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.

How should other professions respond as AI gets better at their work?

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.

What was the speaker's first computer and how did he learn to program?

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.

What does the speaker teach his students now?

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.

Key Quote

“isn't AI making all these things meaningless?”

— Leonardo Silva, What to teach when AI writes the code | Rainer Stropek | TEDxLinz, at 1:00▶ watch at 1:00
Key Quote

“The problem is that AI takes away the part that many of us fell in love with.”

— Leonardo Silva, What to teach when AI writes the code | Rainer Stropek | TEDxLinz, at 5:36▶ watch at 5:36
Key Quote

“This resistance isn't fear of technology, it's grief.”

— Leonardo Silva, What to teach when AI writes the code | Rainer Stropek | TEDxLinz, at 6:05▶ watch at 6:05
Key Quote

“Not the result, the process.”

— Leonardo Silva, What to teach when AI writes the code | Rainer Stropek | TEDxLinz, at 6:38▶ watch at 6:38
Key Quote

“It doesn't shrink my role. It, in fact, expands it.”

— Leonardo Silva, What to teach when AI writes the code | Rainer Stropek | TEDxLinz, at 9:36▶ watch at 9:36
Key Quote

“That's where people who truly understand code become incredibly valuable.”

— Leonardo Silva, What to teach when AI writes the code | Rainer Stropek | TEDxLinz, at 11:35▶ watch at 11:35

Cite this

“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.

Report this page
What is wrong with this page?