Uploaded October 2026 | Updated November 2026, 4 days ago
This talk was recorded at NDC Oslo in Oslo, Norway. #ndcoslo #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you:
ndcconferences.com
ndcoslo.com
Subscribe to our YouTube channel and learn every day:
/ @NDC
Follow our Social Media!
facebook.com/ndcconferences
twitter.com/NDC_Conferences
instagram.com/ndc_conferences
#ai #softskills #code
AI can write code faster than you. Congratulations to the robots. But if speed of code production is the thing holding your team back, I've got some uncomfortable news: you have much bigger problems and nobody is willing to talk about them.
I've spent over 25 years building software and the bottleneck was almost never the typing. It was the three-week argument about what to build. The requirements that changed after you shipped. The stakeholder who couldn't articulate what they actually needed. The architectural decision nobody wanted to own.
Kent Beck said something that stuck with me: 90% of his skills dropped to zero value, but the remaining 10% got a 1000x multiplier. He's right. And the engineers doing well right now (actually well, not performing wellness for LinkedIn) are the ones who figured out which 10% is theirs. They stopped identifying primarily as "people who write code" and started identifying as people who solve problems. Code just happens to be one of the tools.
If your AI strategy is "write code faster," you're optimising the wrong thing.
Let's talk about what to optimise instead.
This talk was recorded at NDC Oslo in Oslo, Norway. #ndcoslo #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you:
ndcconferences.com
ndcoslo.com
Subscribe to our YouTube channel and learn every day:
/ @NDC
Follow our Social Media!
facebook.com/ndcconferences
twitter.com/NDC_Conferences
instagram.com/ndc_conferences
#ai #softskills #code
AI can write code faster than you. Congratulations to the robots. But if speed of code production is the thing holding your team back, I've got some uncomfortable news: you have much bigger problems and nobody is willing to talk about them.
I've spent over 25 years building software and the bottleneck was almost never the typing. It was the three-week argument about what to build. The requirements that changed after you shipped. The stakeholder who couldn't articulate what they actually needed. The architectural decision nobody wanted to own.
Kent Beck said something that stuck with me: 90% of his skills dropped to zero value, but the remaining 10% got a 1000x multiplier. He's right. And the engineers doing well right now (actually well, not performing wellness for LinkedIn) are the ones who figured out which 10% is theirs. They stopped identifying primarily as "people who write code" and started identifying as people who solve problems. Code just happens to be one of the tools.
If your AI strategy is "write code faster," you're optimising the wrong thing.
Let's talk about what to optimise instead.










