The last twenty years of building in the Microsoft ecosystem have been fantastic for me. I've gone from classic ASP, SOAP, to .NET Core and through countless enterprise migrations. Nothing in those twenty years prepared me for the last six months. The way I write software at work changed dramatically, and I don't think it's changing back. I see a lot of devs at work sitting on the sidelines skeptically. I'm not sure that's the right move.
I've been through enough technology shifts to know how these things usually go. Microservices, containers, serverless architectures. Most of the time some things changed, and the rest of us kept writing code the same way we always did. So when AI assistance showed up in my feed every day, I wasn't ready to rethink my workflow.
Then I started seeing it at work. Not like a demo on LinkedIn -- but actual agentic development against real enterprise problems. Code being written, reviewed, and pushed through an agentic workflow. This wasn't spicy autocomplete or copilots. It was a fundamental shift in how we're building software.
I started using these tools at home. It took me a week and then I was using it on everything. I'm building, learning, and I intend to land on the right side of this.
I'm scoping out a real estate property management website in .NET 10, Cosmos DB, full backend web application as well. I'm building a daily meditations phone app in React Native. Both projects are going full agentic from day one - I'll be using AI tools as an active collaborator in architecture, implementation, and iteration. All-in agentic.
This newsletter is the build log. What works, what doesn't, what I'm learning, what I might do differently.
If you're interested in software development, especially if you like .NET, and you're wondering what agentic coding looks like on real projects -- stick around. I'm just a senior .NET dev building things and writing about it.