Two bugs came in from my partner on our ticketing site. Both were fixed and live by midnight.
What was wrong
The homepage was sending anyone who was signed in straight to the admin. Venue staff could never see their own public site.
Events were dropping into the past the moment a show started. They used to drop the next morning. That behavior got lost when the site was rebuilt.
The empty result
At 9:43 PM the agent working on the site’s code reported on event 570. It had zero orders of any status. The agent said this confirmed the negative finding, not just a filtering artifact. It had ruled out its own status filter as the reason the event looked empty.
Shipping it
At 11:33 PM the agent had committed the fixes locally and pushed nothing. By 11:42 PM both were on the live site, and I had posted the result to my partner.
The third find
While in the code I found that checkout has no start-time gate at all. Someone can still buy a ticket to a show from months ago. I filed that as its own ticket. It is not fixed.
AI Skills
Use this lesson with the AI assistant you already use
A rebuilt ticketing site shipped two regressions that a partner found by using it: signed-in venue staff were sent past the public site, and events dropped into the past when a show started. Both fixes went live the same night, and a third gap turned up on the way.
Paste the prompt, share only the context needed to answer it, and treat the result as a draft for your review. Do not include confidential information or let an AI assistant make changes without your approval.
Optional: for a visual report and saved memory, run /dxdev first.
Don’t have it? Get it at dxdev.com/skills/dxdev. The prompt works without it.
dxdev LESSON · paste into your AI coding agent
LESSON: A Rebuild Loses Behavior Nobody Wrote Down
SOURCE: dxdev.com/blog/partner-feedback-surfaces-live-bugs
WHAT HAPPENED: A ticketing site was rebuilt, and a partner using it reported two bugs. The homepage sent anyone who was signed in straight to the admin, so venue staff could never see their own public site. Events also dropped into the past the moment a show started instead of the next morning, which was the old behavior and got lost in the rebuild. An agent working on the code committed the fixes locally and nothing was pushed until they were checked. Both fixes then went to the live site the same night. While in the code, a separate gap turned up: checkout has no start-time gate at all, so a ticket to a show from months ago can still be bought. That one was filed and left unfixed.
THE RULE: A rebuild reproduces what was written down and loses what the old system did implicitly. List the implicit behaviors of the system being replaced (redirects by role, when an item expires, what checkout refuses) and test each one against the new build before launch.
CHECK MY CODE, then report PASS or FAIL with file:line for each:
1. Any homepage or login redirect that sends every signed-in user to an admin area without checking whether they also need the public view.
2. Any "is this event over" check that flips at the start time when the old behavior was to flip at the next morning.
3. Any purchase or booking path that does not refuse an item whose start time has already passed.
THEN PRINT: a table (check, PASS/FAIL, evidence, fix) + a verdict (applies / partially / OUT_OF_SCOPE / no) + the single most important next action.
