
AI ยท 3 min read
๐ The Dawn of the Renaissance Developer
๐ The Dawn of the Renaissance Developer
It’s that time of the year. AWS Community gets ready for the event of the year: re:Invent. And Werner publishes his tech predictions [1]. Like every year, a densely packed piece with loads of gems in it. This year Werner came up with 5 major themes, if I didn’t miscount. I covered the first one in my initial post [2].
The second one is about:
๐จ “The Dawn of the Renaissance Developer”
That’s a vivid discussion at the moment between colleagues and customers alike. Is vibe coding the future? AI Agents taking over the work from human developers?
Werner argues that generative AI will not make developers obsolete but will elevate them into “renaissance developers,” akin to historical polymaths like Leonardo da Vinci who blended art, science, and engineering. Past technological shifts, he argues โ compiled high-level languages displacing most (though not all) hand-written assembly, or cloud managed services and automation tooling absorbing operations work โ lowered entry barriers, expanded opportunities, and amplified the need for human creativity, curiosity, and systems thinking rather than eliminating expertise.
Developers, he argues, must now act as modern polymaths, integrating domain knowledge, business constraints, and nuanced human priorities that today’s AI does not capture on its own, while owning code quality, safety, and communication for both humans and machines.
๐ฐ๏ธ ๐ ๐ ๐๐ผ๐๐ฟ๐ป๐ฒ๐ ๐ง๐ต๐ฟ๐ผ๐๐ด๐ต ๐ง๐ฒ๐ฐ๐ต ๐๐๐ผ๐น๐๐๐ถ๐ผ๐ป
Some of you who know me better know that I’ve been around for quite a while already.
I still programmed in assembler in the very early days, earned some money with relatively low-level C-programming for embedded mobile devices, before higher-level programming languages became the tool of choice. At each step on the ladder of abstraction, questions arose: ๐๐ผ ๐ ๐๐๐ถ๐น๐น ๐ป๐ฒ๐ฒ๐ฑ ๐บ๐ ๐ฝ๐ฟ๐ถ๐ผ๐ฟ ๐ธ๐ป๐ผ๐๐น๐ฒ๐ฑ๐ด๐ฒ? ๐ช๐ถ๐๐ต ๐ฎ๐น๐น ๐๐ต๐ฒ๐๐ฒ ๐ป๐ฒ๐ ๐ฎ๐ฏ๐๐๐ฟ๐ฎ๐ฐ๐๐ถ๐ผ๐ป๐, ๐ถ๐ ๐๐ต๐ฒ๐ฟ๐ฒ ๐ฒ๐ป๐ผ๐๐ด๐ต ๐๐ผ๐ฟ๐ธ ๐น๐ฒ๐ณ๐ ๐ณ๐ผ๐ฟ ๐บ๐ฒ? ๐ช๐ถ๐น๐น ๐๐ต๐ฎ๐ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐๐ผ๐ฟ๐ธ? - ๐ฆ๐ฎ๐บ๐ฒ ๐ฎ๐ ๐๐ผ๐ฑ๐ฎ๐ ๐๐ถ๐๐ต ๐๐ต๐ฒ ๐ฝ๐ฟ๐ผ๐ด๐ฟ๐ฒ๐๐ ๐ผ๐ณ ๐๐ ๐๐ฒ๐ฐ๐ต๐ป๐ผ๐น๐ผ๐ด๐.
During my career, I’ve worked in teams and companies of different sizes. Right when I left startups - and just had finished university - for an enterprise company, there was a big wave of off-shoring work (and then later near-shoring). I had brilliant times with teams in China, India, Romania, and Poland. Every time a project or task was handed over, questions came up: ๐๐ผ ๐ ๐๐๐ถ๐น๐น ๐ป๐ฒ๐ฒ๐ฑ ๐บ๐ ๐ฝ๐ฟ๐ถ๐ผ๐ฟ ๐ธ๐ป๐ผ๐๐น๐ฒ๐ฑ๐ด๐ฒ? ๐ช๐ถ๐๐ต ๐ฎ๐น๐น ๐๐ต๐ผ๐๐ฒ ๐๐ฒ๐ฎ๐บ๐ ๐ฎ๐ฟ๐ผ๐๐ป๐ฑ ๐ฑ๐ผ๐ถ๐ป๐ด ๐ฎ๐บ๐ฎ๐๐ถ๐ป๐ด ๐๐ผ๐ฟ๐ธ, ๐ถ๐ ๐๐ต๐ฒ๐ฟ๐ฒ ๐ฒ๐ป๐ผ๐๐ด๐ต ๐๐ผ๐ฟ๐ธ ๐น๐ฒ๐ณ๐ ๐ณ๐ผ๐ฟ ๐บ๐ฒ? ๐ช๐ถ๐น๐น ๐๐ต๐ฎ๐ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐๐ผ๐ฟ๐ธ? - ๐ฆ๐ฎ๐บ๐ฒ ๐ฎ๐ ๐๐ผ๐ฑ๐ฎ๐ ๐๐ถ๐๐ต ๐๐ต๐ฒ ๐ฝ๐ฟ๐ผ๐ด๐ฟ๐ฒ๐๐ ๐ผ๐ณ ๐๐ ๐๐ฒ๐ฐ๐ต๐ป๐ผ๐น๐ผ๐ด๐.
๐ก ๐๐ถ๐๐๐ผ๐ฟ๐ ๐ฅ๐ฒ๐ฝ๐ฒ๐ฎ๐๐ ๐๐๐๐ฒ๐น๐ณ
I can bring up even more major points of disruption. Always the same questions came up. And in my experience the answers have always been ๐ฌ๐๐ฆ!!! Yes, the prior knowledge still mattered. Yes, there was enough work left. Yes, it actually worked.
My bet is that it’s no different with the current technology of Agentic AI. Amazing technology. I’m currently doing a longer-term experiment with Agentic Coding in a pet project. Here too, the answers so far are yes โ early impressions from one pet project, not a controlled study. Some voices from my network characterize the new way of building as “๐๐ฒ๐ฒ๐น๐ ๐บ๐ผ๐ฟ๐ฒ ๐น๐ถ๐ธ๐ฒ ๐ฏ๐ฒ๐ถ๐ป๐ด ๐ฎ๐ป ๐ฎ๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐ ๐๐ต๐ฎ๐ป ๐ฎ ๐ฐ๐ผ๐ฑ๐ฒ๐ฟ” and “๐๐ผ๐บ๐ฒ๐๐ถ๐บ๐ฒ๐ ๐ถ๐ ๐ณ๐ฒ๐ฒ๐น๐ ๐น๐ถ๐ธ๐ฒ ๐๐ผ๐ฟ๐ธ๐ถ๐ป๐ด ๐ฎ๐น๐ผ๐ป๐ด๐๐ถ๐ฑ๐ฒ ๐ด๐ฒ๐ป๐ถ๐๐๐ฒ๐ - ๐๐ผ๐บ๐ฒ๐๐ถ๐บ๐ฒ๐ ๐ถ๐ ๐ถ๐ ๐ฝ๐๐ฟ๐ฒ ๐ธ๐ถ๐ป๐ฑ๐ฒ๐ฟ๐ด๐ฎ๐ฟ๐๐ฒ๐ป” - I agree with both views.
I’ll share more about my experiments in the near future.
Werner talks about the renaissance developer in his brilliant keynote at re:Invent [3]. Highly recommended to watch!
๐ช๐ต๐ฎ๐ ๐ถ๐ ๐๐ผ๐๐ฟ ๐๐ถ๐ฒ๐?
๐ Last updated: August 13, 2026 โ Technical corrections from a quality audit