Uploaded July 2026 | Updated September 2026, 2 weeks ago
I spent 1.5 billion AI tokens and roughly 24 hours of compute trying to expand a real .NET application. The result was nearly 170,000 lines of bloated, unmaintainable code that ultimately had to be thrown away.
In this video, I break down where the project went wrong, why a more powerful model would not have solved the underlying problem, and how developers should actually use AI on large software projects.
AI is an incredible pair programmer, debugger, and productivity tool. But without proper architecture, checkpoints, Git, and someone who understands the code, it can generate technical debt faster than any human developer.
What do you think? Is AI coding getting better, or are we just producing slop faster?
**Chapters**
00:00 1.5 Billion Tokens
03:17 170,000 Lines
06:37 Technical Debt
09:45 Resetting Everything
13:06 The Right Approach
16:06 Final Verdict
►► Digital Downloads ➜ cttstore.com
►► Patreon ➜ patreon.com/christitustech
►► Twitch ➜ twitch.tv/christitustech
►► Website and Guides ➜ christitus.com
I spent 1.5 billion AI tokens and roughly 24 hours of compute trying to expand a real .NET application. The result was nearly 170,000 lines of bloated, unmaintainable code that ultimately had to be thrown away.
In this video, I break down where the project went wrong, why a more powerful model would not have solved the underlying problem, and how developers should actually use AI on large software projects.
AI is an incredible pair programmer, debugger, and productivity tool. But without proper architecture, checkpoints, Git, and someone who understands the code, it can generate technical debt faster than any human developer.
What do you think? Is AI coding getting better, or are we just producing slop faster?
**Chapters**
00:00 1.5 Billion Tokens
03:17 170,000 Lines
06:37 Technical Debt
09:45 Resetting Everything
13:06 The Right Approach
16:06 Final Verdict
►► Digital Downloads ➜ cttstore.com
►► Patreon ➜ patreon.com/christitustech
►► Twitch ➜ twitch.tv/christitustech
►► Website and Guides ➜ christitus.com
