I've been writing software since 1993. Since 2025 I write it with an agent at my side, on production codebases, with all the baggage they carry. What I learn, I tell live, to development teams and the people who lead them.
Everyone tunes their prompts, switches models, reaches for bigger context windows, and Claude keeps floundering in the code. Why? Maybe the answer sits somewhere else entirely. In this talk I share what I saw in the field, and what I had to unlearn.
Software development and AI were both born in the 1950s, and for seventy years they barely touched. Then they did. Raymond is the name I gave my agent: in this talk I introduce him while he works, live, on a codebase he has never seen. If you're a skeptic, even better: I wrote this one with you in mind.
Three talks on how the craft of building software is changing, made for development teams and so far delivered in private settings (here's a trace).
Raymond writes code fast. The signature, though, is yours. That detail changes everything, and most people find out late. In this talk we explore what remains of your craft when the part that felt like its heart stops being yours alone.
In-houseCopilot, Cursor, Claude Code. At some point I stopped asking which one to use and started asking where I stood in relation to Raymond. That question changed how I work. In this talk we explore it together, demos in hand.
In-houseI've watched Raymond pick up a ticket, open eight files, get lost in the middle and ask me what I wanted. I've watched the same ticket, same Raymond, with the code organized differently: problem solved, tests written, no questions. The difference was all in the code. In this webinar we explore what changes.
If you want the series for your community or your team, write to me.
I started at a technical high school, writing software for small businesses before I even graduated. Since 1993 it has been my trade. The nineties as a developer in Turin, then the real-time Olympic results systems of London 2012 and Sochi 2014, four years as a CTO in IoT, HPC at AWS. Today I'm an engineering manager for a German company, working remotely, still from Turin.
Since 2025 I spend my days putting agents to work on real code. What interests me, by trade and by temperament, is understanding why it sometimes works beautifully and sometimes doesn't, and what needs to change when it doesn't. The answer usually lives in the code, occasionally in the people, rarely in the prompt.
A talk for your community, a question after seeing one, or the reason you think I'm wrong: I read everything.
Send me an email