From the Backlog to the Build Log
AI-Assisted .NET Development: August 21 - August 27, 2026
What I Worked On
One question drove the week. When someone lands on a HowdyChad, GlobalCove, or DevNitro page, can I determine the first touch point and follow their journey across the three properties? Answering it turned out to be a C# problem, and a full week of AI-assisted .NET development. I built a lite CRM, a booking flow, a lead capture path, cross-domain analytics, and the anti-bot hardening that has to sit in front of any of it. Intelligent Engineering shows up in the second half of that list. The AI writes the feature in an evening. You still owe the system its guardrails, its consent gating, and its tests.
A second thread ran under the platform. I moved user suspension out of an app and into GCT and the BlankSite blueprint, added an auth redirect handler for Blazor WASM clients, and switched GlobalCove to global usings to cut token usage on every file the agent reads.
DevNitro itself got attention on both ends of the week. I added a list_agents tool so the agent can discover what it can delegate to, put a hallucination guard around the Claude Code provider's tool calls, and made WorkspacePath runtime-only so it never lands in persisted state. Thursday closed with an MCP refactor to the version 2 standard and the first real test of the ACP adapter.
What the AI Did Well
The CRM came from one prompt I kicked off Friday night. Saturday morning I came down and read what DevNitro had built inside GlobalCove. It held up. That run went well enough that I turned it into a durable change and added a tool-injection refrain to the Claude Code provider prompt so the next run starts from the same footing.
The MCP work followed the same shape and made the case better. I started the prompt Wednesday night and spent about twenty minutes steering it. Thursday morning I spent forty minutes checking and testing the result. A major refactor to the MCP version 2 standard, done in an hour of my attention.
The journey work went in without a fight. I put it in the BlankSite blueprint with consent gating rather than bolting it onto one site, and gave a visitor a durable reference that survives a hop between domains.
The ACP adapter also got the test I owed it. I built the adapter during last week's Grok work and closed that log admitting I had not pointed Buzz at it yet. This week I did, and Buzz drove DevNitro over the wire.
What Needed Correction
The auth redirect cost me two passes. I added a handler in GCT so a Blazor WASM client that gets a 401 or 403 sends the user to the login page. That handler was too blunt. Anonymous pages started bouncing visitors to login, because the profile picture endpoint returns 401 when nobody is signed in. My first fix only redirected when the user had been signed in before. Then I went back and stopped calling that endpoint at all when there is no session. The AI built what I asked for, and I had asked for the wrong thing.
Smaller repairs filled the gaps. DevNitro was mangling the display of multi-edit tool results. web_fetch was passing through runs of blank lines and burning tokens. The contact modal dismissed on any stray click, so I tightened it. I also built the CRM capture endpoints before I hardened them, and spent Monday morning adding Turnstile and IP-based rate limiting to close that gap. Order should have been the other way around, same lesson as the security rules that prove themselves.
What Shipped
The GlobalCove site is live with the lite CRM, a multi-step booking modal, Cal.com scheduling with UTM parameters, Turnstile, rate limiting, and a scheduled job that reconciles unsubscribes back into the CRM. DevNitro pushes a record to that CRM when someone books from DevNitro.com.
On the platform side, GCT shipped user suspension, the corrected auth redirect handler, and global usings. BlankSite picked up the new packages, consent-gated journey tracking, and tests that enforce user privilege boundaries in the API. DevNitro deployed with list_agents, prompt steering, session loading, the hallucination guard from February's work on hallucinated tool calls, and MCP version 2.
The Numbers
| Category | Hours |
|---|---|
| Business | 21h 17m |
| Content | 10h 5m |
| Product / Features | 7h 43m |
| Testing | 4h 53m |
| Deploy / Infra | 2h 2m |
| Community | 1h 23m |
| Total | 47h 21m |
Business took the top slot for the second week running, up from 15 hours last week to 21. The label undersells where the hours went. Most of that block I spent writing C#, because the go-to-market work this week was a CRM, a booking flow, and an analytics layer. 52 commits across four repos back that up.
Where This Fits in Intelligent Engineering
I could have wired the journey tracking into the GlobalCove site and moved on. Instead I put it in the BlankSite blueprint with the consent gating attached, so every site generated from that blueprint inherits the behavior and the consent handling without anyone deciding to do it again. Inheriting your architecture looks like that. A coding agent hands one developer a fast answer for one site. Intelligent Engineering puts the answer in the blueprint, so the next twenty projects start with the version your legal team already approved. One of those you shipped. The other your team can support and scale.
AI-assisted .NET development bought me the CRM and the MCP refactor. I spent the rest of the week on the pipes that tell me whether any of it matters. Back at it next week.
Curious how this site was built?
Watch the 5-minute walkthrough on YouTube →
0 Comments
No comments yet. Be the first to share your thoughts!
Leave a comment