I Let AI Refactor 10 Years of Code — Now I Have to Trust It @ChuckSeverance
I Let AI Refactor 10 Years of Code — Now I Have to Trust It  @ChuckSeverance
Uploaded September 2026 | Updated November 2026, 1 hour ago
This one got big.

I’ve been thinking for months about how to change Tsugi’s Lessons architecture so that its internal representation moves toward the IMS Common Cartridge data model — while still preserving all the extra information and functionality that has accumulated in Lessons over roughly ten years.

I started by talking the architecture through with ChatGPT. Then I handed the resulting design to Cursor and started implementing it.

And it worked.

Sort of astonishingly well.

We normalize the old Lessons JSON into a new Lessons V2 representation, preserve compatibility with existing courses, create a new authoring path for V2 courses, work through discussions, web links, files, resource link IDs, MIME types, and other pieces of the model — and gradually discover that we are building a much larger system than I expected to build in one sitting.

That creates a different problem.

There is now a lot of new code.

Some of it touches code paths used by real production courses. Tens of thousands of people use some of this infrastructure. So the question stops being:

“Can AI build this?”

and becomes:

“How do I build enough confidence in AI-generated code to actually put it into production?”

That means branches, rollback points, compatibility testing, unit tests, regression testing, and a lot of staring at the code wondering whether I actually believe it.

This is a long and sometimes slow video. It isn’t the usual “AI makes an amazing feature in 20 minutes” demo. It’s much closer to what AI-assisted software engineering looks like when the change is large, architectural, and actually matters.

And by the end, I think I’m maybe one-third of the way there.

Cheers.
I Let AI Refactor 10 Years of Code — Now I Have to Trust ItAI Coding: Cursor + CodeRabbit Review Each Other’s WorkAI Coding with Dr. Chuck: Working on Sakai Submit Dates SAK-52505Building an LTI 1.3 Tool Editor in TsugiAI with Dr. Chuck: AI Let Me Attempt a Software Project I Would Never Try Alone (2 hours)How Should Quizzes, Grades, and LTI Fit Together in an LMS?Post-War Computing and CommunicationMemorial Day MoodDjango for Everybody Week 12: Owned Rows and Marketplace AuthorizationPythonShell (shell.py4e.com) in 2 Minutes: Python, No Login, No CloudA History of C, UNIX, and Computation (a.k.a The importance of 1978) (Classic)Shelby gets a pup cup at Moomers Ice Cream in Traverse City MI. #dogcation #icecream #spoiledpup
Chuck Severance |

I Let AI Refactor 10 Years of Code — Now I Have to Trust It

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER