My website says jokingly says: "I edit text files for a living at Microsoft." Turns out, I don't even do _that_ anymore.

I used to define myself by the code I wrote. C#, XAML, knowing obscure platform APIs by heart, that was what made me a "real" engineer. Then AI started writing most of my code, and I had a bit of an identity crisis. If I'm not the one typing the code… what exactly am I doing all day?

I'll be honest: I was skeptical at first. But somewhere along the way, things actually changed. Last month I realized I hadn't opened my IDE in three days, and I'd shipped more than usual. That still feels weird to say out loud.

Now, I work for the company that builds a lot of these tools. I know that. You should know I know that. This isn't a pitch. This is what my actual workday looks like; the parts where AI genuinely helps, and the parts where it confidently generates nonsense and I have to catch it before it hits main.

In this keynote, I'll walk you through real examples from my daily work on .NET: how I triage issues, review PRs, explore unfamiliar APIs, and yes — how AI gets it wrong and what that costs when you're not paying attention. Live demos included, mistakes and all.

You'll walk away with a clear picture of what actually changes when you let AI into your workflow, what doesn't, and why "software engineering" was never really about typing code. The code was always just the delivery mechanism.