The AI Learning Hub Journal

Changing Your Mind About Data

The first change after real records exist is the dangerous onea second groomer joins — every booking now needs ‘with whom’, and 200 were made before the question existedthe form gains a choice —easy, done in minutesbehind the form: 200 bookings madeunder the old rules — none says with whomall with the original groomer? probably —but ‘probably’ is not something afiling system can holdTHE DANGER PATH — STRAIGHT AT THE REAL THINGask the AI to add ‘with whom’ — it obliges, cheerfullythe form changes in minutes and looks perfectthe 200 old bookings: stranded under the new rules,rewritten with a guess — or simply gonethe page still loads, still takes new bookingsa regular arrives for an appointmentthe system no longer remembersthe AI is not careless with code — it is careless withhistory, because nobody said the history matteredTHE SAFE PATH — COPY, CHANGE, LOOK, THEN TOUCH1copy firsta copy makes every mistake survivable2change the copythe version customers depend on stays untouched3look at old records through the new shapethe standing Saturday, the two-dog morning — open them4only then touch the real thingonce the copy behaves and the history reads correctlyslower than letting the AI loose on live records —it is meant to beA COPY NOBODY HAS RESTORED IS A HOPE, NOT A BACKUPdoes the platformkeep copies at all?how far back dothe copies go?have I actuallyrestored one?putting one back: minutes,or a lost afternoon?all four answered: a backup · only the first: a feelingthe drill, done calmly before it is needed: take a copy, practise putting it back somewhere safe,and write the steps down while they are fresh — the worst day is not the day to learn themplenty of businesses found out, on the worst possible day, that their copies were empty or impossible to put backTHE PAGE CAN LOOK PERFECT WHILE THE HISTORY BEHIND IT IS GONEthe extra hour is the whole difference between ‘we changed how bookings work’ and ‘we lost the bookings’
Change the copy, check the history through the new shape, and only then touch the version people depend on.

The Day You Need One More Question

Real products change their minds, and the day it happens looks innocent. Suppose the business grows and a second groomer joins. Every booking now needs one more piece of information: with whom. The form is easy — the AI adds a choice to the page in minutes. The trap is behind the form. You have 200 existing bookings, made under the old rules, and none of them says with whom. Are they all with the original groomer? Probably — but 'probably' is not something a filing system can hold. You cannot just change the form. You must also decide, deliberately, what becomes of every record made before the change. That decision is the real work, and no screen will ever show it to you. Changing the shape of live data while people depend on it is the most grown-up thing this course asks of you.

  • A second groomer means every booking needs 'with whom' — and 200 records don't have it
  • Changing the form is minutes; deciding what old records now mean is the work
  • 'Probably with the original groomer' is not something a filing system can hold
  • Every change to what is recorded must answer for records made under the old rules

Where Vibecoded Apps Actually Die

This is where vibecoded products die — not during the build, when everything is reversible, but at the first change after real data exists. Ask an AI to add 'with whom' and it will do it, cheerfully, in a way that looks perfect on screen. What it will not reliably do is care about your 200 existing bookings. It may quietly strand them, unreachable under the new rules. It may rewrite them with a guess. In the worst case it rebuilds the filing system fresh, and the old records are simply gone — while the page still loads, still looks right, still takes new bookings. You find out when a regular arrives for an appointment the system no longer remembers. The AI is not being careless with code; it is being careless with history, because you never told it the history mattered. Telling it is your job now.

  • The dangerous moment is not the build — it is the first change after real data exists
  • AI will change the form happily and strand or destroy old records quietly
  • The page can look perfect while the history behind it is gone
  • The AI is careless with history unless you tell it the history matters

A Copy Nobody Has Restored Is a Hope

Backups are what make the previous slide survivable, so it is worth being honest about what a backup is. A copy nobody has ever restored is a hope, not a backup. Plenty of businesses have discovered, on the worst possible day, that their copies were empty, incomplete, or impossible to put back. The fix is a drill, done calmly, before you need it: take a copy, practise putting it back somewhere safe, and write down the steps while they are fresh. Then ask four questions of whatever platform holds your data. Does it keep copies at all? How far back do they go? Have I actually restored one? And how long does putting one back take — minutes, or a lost afternoon? If you can answer all four, you have a backup. If you can only answer the first, you have a feeling.

  • A copy nobody has restored is a hope, not a backup
  • Practise putting a copy back before you need to, and write the steps down
  • Ask the platform: does it keep copies, how far back, how long does a restore take
  • If you have never restored one, you do not yet know what you have

The Rule: Copy, Change, Look, Then Touch

All of this collapses into one rule, short enough to keep. Before any change to what is recorded: copy first, change the copy, look at the old records through the new shape, and only then touch the real thing. Copy first, because a copy makes every mistake survivable. Change the copy, so the version customers depend on stays untouched while you experiment. Look at the old records through the new shape — actually open them: does the regular's standing Saturday booking still make sense, does the customer with two dogs still have both? Only when the copy behaves, and history reads correctly, does the real thing get the change. This is slower than letting the AI loose on live data. It is meant to be. The extra hour is the entire difference between 'we changed how bookings work' and 'we lost the bookings'.

  • Copy first — a copy makes every mistake survivable
  • Change the copy while the real thing keeps serving customers
  • Open old records through the new shape and check they still make sense
  • Only then touch the real thing — the extra hour is the whole difference

Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.