The HowdyChad Build Log
Thoughts on software architecture, intelligent engineering, and building DevNitro.
$ tail -f build-log
Your codebase gets harder to change every year and nobody broke it. Here are the three things that pile up, and one list that shows you where to start.
My DevNitro API key expired mid-run. The agent kept burning tokens and saved nothing. The fix, plus concurrent autonomous runs and conversation forking, in one night.
Your team has used AI for a year, and every change still waits on your best engineer. Here's how to split review into judgment and rules you write down once.
A NuGet vulnerability audit stopped a DevNitro deploy on a package I never referenced. The agent traced it in minutes. Plus SignalR fixes and a lead magnet.
Most AI coding tools have one flat context. Scoping them like appsettings.json gets you halfway and then breaks, because the rule that makes config work destroys a standard.
AI-assisted .NET authorization: GCT AccessCheck guards closed real IDOR holes in DevNitro, then a blueprint upgrade run exposed a version bump that never fired.
AI-assisted .NET development built a lite CRM overnight and refactored MCP in an hour. Then a blunt 401 redirect sent anonymous visitors to the login page.
Grok joined DevNitro's provider lineup in three days this week. Native tool isolation, an ACP adapter, and a production weather app built from a blueprint.
DevNitro hardened visual browser cleanup, tool calls, tests, analytics, and blueprint checks during a week of AI-assisted .NET development.
DevNitro turned .NET security rules into checks this week, with auth canaries, Blazor CSS linting, payment safeguards, and stronger tests.