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 September 26 - October 2, 2025
What I Worked On
Most of this week went to legal paperwork and entity structure. DevNitro Inc became a formal entity late on September 30. I actually wanted it created on October 1 (1001), but it went through faster than I expected. The week turned into getting the structure around the company right. I drafted a SAFE and worked out the terms for an early investor page. I also started an IP agreement between GlobalCove and DevNitro so the entity boundary would be clean before any money moved.
Two small .NET problems needed fixing too. A package upgrade in my local AI environment in docker pulled in Postgres 18 and broke things that depended on 17. A git branch versioning issue in the GCT NuGet packaging pipeline blocked a deploy I needed to ship.
This week built the container the company runs in, not a feature inside it.
What the AI Did Well
When I went to set up an EIN for DevNitro, I asked the AI to walk through the steps with me. It flagged the order-of-operations details that are easy to get wrong when you are moving fast, and talking through them kept me from creating problems I would have had to unwind later.
I also used AI to sanity-check the terms on an early investor page for internal consistency. Talking through how the pieces fit together sped up a decision I had been circling for weeks. It's not about using AI to make decisions for me, it's about using it to try and make sure I don't miss anything when I make them myself.
What Needed Correction
I broke the Postgres environment myself. A routine package upgrade in my local AI stack moved Postgres from 17 to 18 without me checking what depended on the older version. Realizing the issue and then pinning everything back to 17 took about an hour. The fix going forward is to pin the database version explicitly instead of letting it move with the rest of the stack.
The GCT NuGet versioning issue took longer. Git branches had drifted out of sync with the package versions they were supposed to produce, and the deploy pipeline choked on the mismatch. Tracing the branch history back to a clean package took close to two hours.
What Shipped
The NuGet versioning fix went out, along with the deploy it had blocked. I also stood up the DVN database for DevNitro, the platform's own database rather than one borrowed from another project.
The larger outcome from this week doesn't show up in a changelog: DevNitro, Inc. moved from a plan into an entity in motion.
The Numbers
| Category | Hours |
|---|---|
| Product / Features | 9h 18m |
| Content | 8h 49m |
| Business | 1h 29m |
| Deploy / Infra | 1h 13m |
| Community | 1h 7m |
| Total | 21h 56m |
Five hours of research against roughly two hours of code fixes describes this week accurately: closer to legal work than engineering work. That balance shifts back toward engineering next week.
Next week returns to the code. The entity groundwork won't make for more interesting log entries, but DevNitro can't take on investors or hire anyone without it.
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