profile

.NET Web Academy

4 steps to modernize a legacy .NET app with AI

Published about 9 hours ago • 1 min read

Hey friend,

A developer I know built his whole career on one bet: that young developers would never want to touch old code. So the legacy systems quietly running real companies would always need someone, and he would be that someone.

For twenty years it paid.

Then AI arrived and went straight for the part he thought was safe.

Because the hardest part of modernizing an old system was never the typing. It was the understanding. Reconstructing thirty projects and three contractors' worth of decisions in your head before you dare change a line. That used to take weeks, and it is exactly what these tools are best at dissolving.

But his niche did not disappear. It compressed.

In my new video I break down what actually happened to that kind of work, and then the four steps he uses now on real client systems:

The understanding pass, before you write a single line. The constraints file that stops the AI inventing packages that do not exist. Why you migrate one vertical slice instead of one layer. And the review rule that will save you an entire wasted day.

Watch the video here

The barrier that used to protect legacy work is gone. What replaced it is worth more.

Take care,

Patrick

P.S. If your team is sitting on an aging .NET app and you want them to learn this properly, I run private workshops for exactly that: https://dotnetwebacademy.com/workshops

.NET Web Academy

by Patrick God

Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.

Read more from .NET Web Academy

Hey friend, The other day I found a bug in StackBuddy, an app I built. Normally I'd open it, file a ticket for myself, and move on. Instead I turned to my AI and just said, "log a dev ticket for that." And it did. A real ticket in my own bug tracker. Title, description, priority, the whole thing. I never opened the actual app. The thing that makes that possible is called MCP, Model Context Protocol. Ignore the name for a second. Out of the box, an AI can only talk. It writes and explains, but...

21 days ago • 1 min read

Hey friend, I don't really write code by hand anymore. I describe what I want, and the AI builds it. For a while, that scared me. If I am not writing the code, does everything I spent years learning still matter? Does my stack matter at all? If you are a developer right now, I would bet you have felt some version of that too. Here is where I landed. It flipped the whole thing for me. The other day I was debugging a slow app, talking it through with the AI. Would WebAssembly help here? Is it...

28 days ago • 1 min read
video preview

Hey friend, Lately I told an AI I’d see it in 7 hours, and went to bed. It was done in 2. Across two different projects. There’s this thing people call the night shift. You give an AI agent a pile of work, start it in a loop, and go to sleep while it keeps working on your real codebase. I tried it a month ago and could not make it work, the model just fell apart. But with the newest models, it works now. And the surprising part wasn’t that it ran all night. It’s that it ran out of work before...

about 1 month ago • 1 min read