AI Workshops for Enterprise .NET Teams
Your .NET team ships with AI. I show them how.
I built the AI and Copilot workshops for Microsoft's VS Code team, and before that I was the ASP.NET MVC Community Lead. Now I run workshops for enterprise .NET shops: two days inside your solution, learning how to modernize legacy code, review what the agents produce, and move a whole team from the 2015 way of working to the 2026 one. No hype. No slides about "the future." Just work that ships.
Built for enterprise .NET shops with real constraints: a decade of Framework code, a compliance team, and an agent that just opened a 4,000-file pull request. Here's exactly what the workshop covers and exactly what it costs.
Two days of hands-on work with Claude Code inside the .NET code your team actually ships. Legacy modernization, agent-scale pull requests, review practices that hold up in a regulated shop, and the human part nobody plans for: getting a team of twenty to change how they work.
Your team walks out with:
Not sure where to start? Spend a half day with me on your actual solution and find out before you commit to anything bigger.
What you get:
The price on this page is the price on the proposal. No "it depends," no discovery-call markup. Fixed, public, boring.
The focus is .NET, because that's where the hardest version of this problem lives: old code, big teams, and an audit trail. The practices travel to whatever else you ship.
Framework 4.x, WebForms, WCF, and the project nobody wants to open. We use agents to map the dependency graph, carve out a slice that can actually move, and get it onto modern .NET with tests that prove behavior didn't change. Strangler patterns, not big-bang rewrites.
Claude Code inside a real solution: multi-project builds, internal NuGet feeds, dotnet test, and the conventions your team argues about. Writing CLAUDE.md so it encodes your architecture instead of generic advice, plus subagents, plan mode, and when to just write it yourself.
Agents produce more diff than humans can read, and enterprise teams hit this in week two. How to scope work so the PR arrives reviewable, how to split what already landed too big, and how to decide fast when a giant one shows up anyway.
What review is for once a machine wrote the first draft. Reading for intent and blast radius instead of style, using agents as a first-pass reviewer without letting them approve their own work, and keeping a trail that satisfies whoever audits you.
The part that actually decides whether this works. Your senior people are skeptical for good reasons and your juniors are pasting output they don't understand. We work through both, plus what to measure, what to mandate, and what to leave alone.
Where code and context are allowed to go, what stays on your network, how to handle secrets and customer data in prompts, and what to write down so security signs off once instead of every sprint. Real policy, not a slide.
Tell me about your team and what you ship. I answer everything myself, usually within a day.
One 30-minute call: dates, on-site or remote, which solution we work in, and which of the six areas matter most to your team.
Two days, hands-on, in your code. Every engineer leaves with working agentic workflows and the judgment to use them on code that matters.
Your team's seats in The AI Pro keep the questions flowing and the momentum going after I'm gone. No cliff, no "good luck out there."
I spent three years on the VS Code team at Microsoft, where I built the AI and Copilot workshops and curriculum that taught the team behind the tools your engineers already use. Three more years helping enterprise teams get serious about PostgreSQL. My first run at Microsoft was as the ASP.NET MVC Community Lead, which means I've been arguing about .NET architecture with enterprise teams since before half your solution was written. Along the way I founded Tekpub, a developer screencast company that Pluralsight thought was worth acquiring.
I wrote The Imposter's Handbook because I'm largely self-taught and felt the weight of not knowing things I felt I should. Thirty thousand other developers apparently felt the same way.
Now I do one thing: I help engineering teams build AI as a capability, not evaluate it as a product. There's a real difference, and I've seen both sides of it. The workshop focuses on .NET because that's where the hard version lives, but nothing about the practices is locked to it.
30,000+ copies sold. Written for curious developers who want to understand the fundamentals without the academic gatekeeping.
A CS primer for self-taught developers. Algorithms, data structures, computation theory, databases, design patterns, and more. The book that started it all.
Learn more →
A data science mystery featuring PostgreSQL, Cassini, and Enceladus. Learn serious SQL skills through a narrative that keeps you turning pages.
Learn more →
Essential skills and practices for self-taught professional developers. DevOps, security, containers, and the practical stuff that rounds you out.
Learn more →Fifteen years of posts on PostgreSQL, Elixir, Node.js, career, writing, and whatever I happened to find interesting that week.
Co-hosted with Scott Hanselman. Stories about the human side of software, from getting fired to competitive drive to why we aren't on Mars yet.
If you're a VP of Engineering or CTO sitting on a decade of .NET and trying to figure out what your team should actually do with AI (not the hype, the reality) let's talk. Whether it's a workshop, an assessment, or you're just not sure yet, email me. I read and answer everything myself.