What NOT to AI: Hand-Crafting Your Apps Core Foundation
AI coding agents can generate a working application in an afternoon. That is exactly why you need to be careful about what you let them decide.
In my .NET Conf 2026 session, What NOT to AI: Hand-Crafting Your App’s Core Foundation, I cover the parts of an application I never hand over to the AI.
Watch the video: https://www.youtube.com/watch?v=Hu0pDa0jwkM
The Workflow
Get the foundation right by hand, then let the agents build on top of it. The AI writes much better code when it has a solid blueprint to work from.
From typist to architect
“Vibe coding” is fine for a prototype. For software you have to maintain, the Agentic Coding Workflow asks something different of you: stop being the person who types the code and become the architect who sets the rules. The agent builds whatever you describe. If the foundation is vague, it will happily invent one, and you will be living with that invention for years.
- Database design. Tables, keys, and relationships are the contract everything else depends on. I design the schema myself.
- Authentication. JWT or cookies is an architectural decision with security consequences. I make that choice up front and don’t let it emerge from generated code.
- The Data Context. The DbContext is the map the agent reads to understand your data, so its structure has to be deliberate.
