Wednesday
Room 2
16:00 - 16:30
(UTC+02)
Talk (30 min)
For God's sake, keep the nerds!
Anyone can spin up an app, generate an API, and ship to production — without writing a line of code themselves. Top executives are declaring that technical expertise is becoming optional, that "anyone can be a technologist" without learning to code. Meanwhile, developers are reporting the opposite: FOMO, dread, and the sense that bad teams get worse with AI, not better. Both can't be right. This talk shows a better approach: shift the focus from chasing specific attacks to teaching solid defensive coding principles. We'll build security knowledge directly into the agent — using skills, hooks, and standards — so it looks up the right guidance, plans for it, and reviews its own work. You'll leave knowing how to make your agent produce secure code far more often, by default.
At Tet Digital, we ran a six-week Claude Code pilot across 6 teams and 30 developers, then rolled it out to 180. 90% reported higher productivity. But productivity isn't the whole picture: AI makes mistakes, so team practices for catching and correcting them matter more, not less; there's reduced learning, so skill development needs continued focus; the developer role is shifting toward orchestration and quality control; and like any tool, this one needs maturation, not just access.
In this talk, Stein Inge Morisbak (CTO) shares the concrete findings from the pilot, why Tet chose a deliberate three-step rollout with mandatory training and guardrails instead of an open tap, and why AI is best understood as an amplifier — one that makes deep technical understanding more valuable, not less. When anyone can ship, someone has to know what we're actually shipping.
Stein Inge Morisbak
Stein Inge Morisbak is CTO at Tet Digital, leading the technological modernization of Norwegian public transport. A pioneer in Agile, DevOps, and the cloud journey, he has been a central voice in the Norwegian tech community for nearly three decades — first as a developer and architect, then in senior leadership as CDO, CEO, and CTO. That trajectory from hands-on code to the executive table shapes why he believes technical depth — and the nerd — matter more, not less, now that AI is changing how we build software.