A note about this build log entry: I published this after the week it covers. DevNitro reconstructed a draft from work-related entries in my journal, Git commit history, and time tracking. I reviewed, edited, and approved the final post. The story reflects what I knew and built at the time.
From the Backlog to the Build Log
Week of December 19 - December 25, 2025
What I Worked On
A Christmas week, so the hours were lighter and the story is smaller. Most of the product time went three places: making the agent runner resilient, pushing the payment and checkout UI into GCT, and losing a full day to a Blazor debugging problem that had a one-line fix.
On the agent side, I made the Terminal.Gui console UI actually call the LLM, moved agents into isolated processes, and hardened conversation resume: restoring the model's context when you pick a session back up, detecting runaway loops, recovering from crashes, and stopping the agent from declaring victory before the work is done.
On billing, I refactored the payment code out of the client app and into GCT so subscriptions and checkout live in the shared core. That brought in user settings, a payment UI with address autocomplete, guest checkout, and billing address handling.
What the AI Did Well
Centralizing the Dapper setup behind a single AddGlobalCoveDapper call was a clean refactor the AI handled well, and it makes every generated site wire up data access the same way. The payment UI, including address autocomplete and guest checkout, came together faster than I expected for a Blazor form with that many states.
What Needed Correction
Two of these hurt.
First, the rate limiter I added during the security pass was counting a successful login as a failed attempt, so it locked me out of my own admin. I refined it to record failed attempts only on real failures and to ignore 2FA and successful logins. A security control that punishes the legitimate user is its own kind of bug.
Second, the one that cost a full day. The Visual Studio debugger kept crashing when it loaded the Blazor site. I updated VS. I repaired VS. I compared the projects that worked against the ones that did not and found no difference. Eight hours in, the fix was clearing the bin and obj folders. That was it. It also fixed a styling problem I had been chasing separately. I made a short video that week about how often the simple path is the one you skip.
I also got DevNitro to create a new site through the create-site tool for the first time, a Todo app, though the CLI died partway and did not finish the work. Half a win.
What Shipped
The agent runner survives crashes and resumes conversations with context intact. Payment and subscription UI, including guest checkout and address autocomplete, lives in GCT. Dapper setup is centralized behind AddGlobalCoveDapper. The rate limiter no longer locks out valid users. And the create-site path ran end to end for the first time, even if it did not finish.
The Numbers
| Category | Hours |
|---|---|
| Product / Features | 30h 52m |
| Content | 3h 20m |
| Community | 1h 3m |
| Total | 35h 16m |
A lighter week by design. The product time split across subscriptions, the debugger hunt, the console UI, and migrations, with almost no content over the holiday.
The headline work was payments and agent resilience. Some weeks the work moves the platform forward. Some weeks it just reminds me that the boring fix, clear bin and obj, is usually the right one.
Curious how this site was built?
Watch the 5-minute walkthrough at devnitro.com →
0 Comments
No comments yet. Be the first to share your thoughts!
Leave a comment