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 October 10 - October 16, 2025
What I Worked On
This week was cleanup and foundation work in GCT and BlankSite. I spent two days pulling compiler warnings out of both projects, going from over 500 down to 76. Along the way I found that InsertData.sql had gotten corrupted in a recent change, fixed it, and got all 13 GCT tests running again.
BlankSite got real attention too. I stopped ignoring the wwwroot files, fixed the styling, and added actual theming: light or dark, horizontal or vertical, with auto-detection and a manual switch. Test pages went in to prove the theming worked before I moved on.
By the second half of the week the focus shifted to something bigger: getting GCT to support SQLite in addition to SQL Server and Postgres. I added a migration project directly to GCT so client projects could use it, and started running the same test suite against all three providers.
What the AI Did Well
The warnings cleanup was mechanical but large, and the AI worked through most of it without me watching every change. Going from 500+ warnings to 76 in two focused sessions would have taken me most of a week by hand.
The BlankSite theming came together fast too. Auto-detection with a manual override for light, dark, horizontal, and vertical touches a lot of small cases, and it landed clean with test pages to back it up.
DevNitro also stood up two throwaway test sites this week, Entrepreneur Checkup and I Fix AI Code, along with HowdyChad.com itself, to prove the prototype flow held up outside of GCT's own test suite.
What Needed Correction
The SQLite work is not done. SQL Server tests pass with the provider changes in place, but SQLite is not pulling in all the seed data correctly yet. I have to track down that provider-specific behavior myself, so it carries into next week.
A WSL and Docker Desktop scare in the middle of the week also cost time. A flagged file in a temp folder stopped Discord and left WSL flaky until I killed every WSL process and restarted clean.
What Shipped
GCT is down to 76 warnings with all 13 tests passing again, and the corrupted seed data file is fixed. BlankSite has working theming with test pages to prove it. The GCT migration project is in place for client projects, and SQL Server now runs clean against the new provider abstraction.
SQLite support is still in progress. The architecture is there; the seed data path is the remaining gap.
The Numbers
| Category | Hours |
|---|---|
| Product / Features | 31h 30m |
| Content | 7h 8m |
| Community | 1h 8m |
| Business | 0h 38m |
| Total | 40h 24m |
Most of the week went straight into the prototype and GCT itself, with a smaller slice building HowdyChad.com as a real test of the platform.
SQLite is the piece that carries into next week. Getting a GCT project to run identically against SQL Server, Postgres, and SQLite is unglamorous, provider-by-provider work, and it is what makes the platform usable by any client project regardless of database choice.
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