Uploaded September 2026 | Updated November 2026, 20 hours ago
This episode starts calmly enough.
In the previous session, I spent about two hours building a major new Tsugi course-navigation feature with Cursor. At the end, I pushed everything into a pull request and handed it over to CodeRabbit for review.
So this session begins with me working through CodeRabbit’s comments.
Some of the feedback is exactly what I want from an AI code reviewer: accessibility improvements, keyboard behavior, cleanup suggestions, and a few places where the implementation needs another look.
I also decide that my Cursor conversation has gotten too large and sluggish. The design discussion from the previous session is no longer useful context, so I ask whether I should summarize the thread or simply start fresh.
The answer is effectively: start a new thread.
That turns out to be a good idea.
Then I make the session much more exciting than necessary.
While Cursor is rebuilding its context, I decide to merge a small related change and push it into production.
Bad idea.
I upgrade the production Django for Everybody site before the underlying Tsugi changes it depends on have been merged.
And production breaks.
Completely.
What follows is the part of software development nobody puts in the polished demo:
realizing the production site is down
swearing
figuring out what I merged
searching for the GitHub revert button
reverting the change
pulling the fix back into production
realizing exactly why it worked locally but failed in production
getting the site back online
The core mistake was simple: my local environment already had the new Tsugi branch checked out, so the higher-level DJ4E changes worked perfectly there. Production did not yet have those underlying Tsugi changes.
It is also a pretty good reminder of why smoke tests matter.
After the production excitement settles down, I go back to the CodeRabbit review, decide which issues to fix immediately, which to defer, and which need to become future accessibility work.
So this episode is a little bit of everything:
AI-assisted development
AI code review
Cursor context management
CodeRabbit
GitHub pull requests
production deployment
reverts
dependency ordering
smoke testing
and a completely self-inflicted outage
The good news is that production comes back, the navigation work is still intact, and CodeRabbit is still doing its job.
The lesson is pretty simple:
If one repository depends on changes in another repository, merge them in the right order.
And maybe don’t casually update production while you are simultaneously reviewing code in another window.
Cheers.
This episode starts calmly enough.
In the previous session, I spent about two hours building a major new Tsugi course-navigation feature with Cursor. At the end, I pushed everything into a pull request and handed it over to CodeRabbit for review.
So this session begins with me working through CodeRabbit’s comments.
Some of the feedback is exactly what I want from an AI code reviewer: accessibility improvements, keyboard behavior, cleanup suggestions, and a few places where the implementation needs another look.
I also decide that my Cursor conversation has gotten too large and sluggish. The design discussion from the previous session is no longer useful context, so I ask whether I should summarize the thread or simply start fresh.
The answer is effectively: start a new thread.
That turns out to be a good idea.
Then I make the session much more exciting than necessary.
While Cursor is rebuilding its context, I decide to merge a small related change and push it into production.
Bad idea.
I upgrade the production Django for Everybody site before the underlying Tsugi changes it depends on have been merged.
And production breaks.
Completely.
What follows is the part of software development nobody puts in the polished demo:
realizing the production site is down
swearing
figuring out what I merged
searching for the GitHub revert button
reverting the change
pulling the fix back into production
realizing exactly why it worked locally but failed in production
getting the site back online
The core mistake was simple: my local environment already had the new Tsugi branch checked out, so the higher-level DJ4E changes worked perfectly there. Production did not yet have those underlying Tsugi changes.
It is also a pretty good reminder of why smoke tests matter.
After the production excitement settles down, I go back to the CodeRabbit review, decide which issues to fix immediately, which to defer, and which need to become future accessibility work.
So this episode is a little bit of everything:
AI-assisted development
AI code review
Cursor context management
CodeRabbit
GitHub pull requests
production deployment
reverts
dependency ordering
smoke testing
and a completely self-inflicted outage
The good news is that production comes back, the navigation work is still intact, and CodeRabbit is still doing its job.
The lesson is pretty simple:
If one repository depends on changes in another repository, merge them in the right order.
And maybe don’t casually update production while you are simultaneously reviewing code in another window.
Cheers.










