Wednesday 

Room 3 

11:20 - 12:20 

(UTC+02

Talk (60 min)

What Actually Happens When You Give a Dev Team Claude Code for a Day

I keep building tools I didn't plan to build. A PR walkthrough generator that started as "can you just explain what this colleague changed?". Semantic search across thousands of Claude Code sessions that started as "I figured this out two months ago, where was it?". A design space explorer that started as "show me what this could look like."

AI-Assisted Development

After about 7,500 sessions I notice they're all variations on the same move — using cheap LLM tokens to claw back something AI made suddenly much harder: understanding what's in your code, your sessions, your design space. Addy Osmani calls it "comprehension debt"; Simon Willison, "cognitive debt".

I had a couple of days giving Claude Code to engineers who'd never used it. What they reached for first wasn't the chat — it was the tools. Once a tool exists, you don't need to know how to build it to use it. I'll walk through three of these tools, the prompt → skill → tool pipeline that produced them, and the patterns engineers picked up fastest when handed them — plus one uncomfortable finding from the research: AI walkthroughs measurably improve comprehension and inflate confidence about it. Designing for both is the actual craft.

Stian Håklev

Stian is a Product Engineer at Tana, where he builds tools for how engineering teams think, organize, and work with AI. With 7,500+ Claude Code sessions logged and a stack of homemade developer tools, he spends as much time using the AI tooling stack as building for it. He also runs hands-on AI workshops for engineering teams — most recently 321 and Vitec Megler — which double as direct field research into how developers actually adopt AI tools. His PhD in Learning Sciences (University of Toronto) and postdoc at EPFL keep showing up in unexpectedly practical ways.