Coding with AI: Small Fixes, Big Architecture — Tsugi Cleanup Day @ChuckSeverance
Coding with AI: Small Fixes, Big Architecture — Tsugi Cleanup Day  @ChuckSeverance
Uploaded October 2026 | Updated November 2026, 3 days ago
Not every coding session needs to be a moonshot.
After several sessions of major architectural work in Tsugi, I decided to spend an evening knocking small things off the to-do list — the easy fixes that make the system cleaner, more consistent, and a little nicer every time.

Of course, “small fixes” have a way of turning into architecture discussions.

We start with the Files controller, adding recursive file counts to folders so you can immediately see whether a folder contains anything below it.

Then I finally get rid of some lingering Lumen framework naming.

Tsugi stopped depending on Lumen a long time ago, but some class names were still hanging around. Rather than calling the replacement something boring like HTTP or WebApp, we rename it Lumos.

Because Harry Potter.

Next we move into grading and LTI Assignment and Grade Services. Tsugi already had support for gradingProgress and activityProgress, and I had somehow forgotten just how much of it I had already built.
We update quiz grading so that a completely auto-graded quiz can be marked completed and fully graded, while a quiz containing an ungraded essay can be completed but pending manual grading.

That turns into a nice reminder of why standards are useful: every Tsugi gradebook column is already modeled around LTI AGS concepts, which gives us a strong foundation for future assignment and grading workflows.

Then we jump over to the Python for Everybody supporter system.
Supporters get a green heart for a year, and I wanted existing supporters to be able to contribute again and extend that expiration date another year. Cursor makes the change, we push it into production, test it live, and then tone down the UI so the “extend” option is subtle rather than begging for money.

And finally, after promising not to write any more code, I start thinking about the future of the Tsugi threaded discussion tool.
The current discussion system was written in PHP with little rendering methods that were basically my imitation of Web Components. Now that AI makes this kind of migration much easier, I start thinking seriously about replacing those server-rendered pieces with Lit-based Web Components — similar to the architecture used in Sakai.

No implementation yet. Just architecture, possibilities, and something to sleep on.

So this episode is a collection of small improvements:

Recursive file counts
Lumen becomes Lumos
Better LTI AGS grading states
Quiz support for pending manual grading
Supporter renewals

And a first look at a future Lit-based discussion architecture
Sometimes the best coding session is just making the to-do list shorter.

Tsugi: tsugi.org
Python for Everybody: py4e.com
Django for Everybody: dj4e.com
Coding with AI: Small Fixes, Big Architecture — Tsugi Cleanup DayAI Master Programmer with Dr. Chuck: Sakai LTI Auto Release SAK-49972AI Coding (No Audio): LTI Allow Tools to use LTI Bearer Tokens to Access WebAPI - SAK-52581Title: Week 6 – Django Forms, Generic Views, and Database InteractionDJ4E Marketplace - Initial Setup / Install (Classic - MySQL)DJ 04.01 Linux Shell Commands for Django Developers (18:27)When AI Moves Your Cheese 😤 | Cursor AI Meltdown & Recovery (Live Coding with Dr. Chuck)AI Coding: Tsugi Discussions Management - Also Wheelchair FloorballShelby gets a Pup Cup to Dairy Lodge in Traverse City #dairylodgetc #aussie #dogcation #spoiledpupI 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-52505
Chuck Severance |

Coding with AI: Small Fixes, Big Architecture — Tsugi Cleanup Day

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER