The most detailed free FDE + DevOps library: 140+ lessons, 70+ labs and 80 long-form articles, in English and Turkish. Start learning →

TürkçeSearch

Build with AI: From Zero to Your First App · Module 6: Working reliably with AI coding tools · Lab

Snapshot and Rollback Drill

25 min hands-on · Core

Browser only. Practice the snapshot habit on a deliberately risky edit with a scratch copy; no account anywhere.

Three ways to do this lab. A: the browser steps below, the main path, free with no account. B: try the same task with your own AI tool if you have one (its terms and quotas apply). C: work from the provided material and the worked solution below, which teaches the same skill. No path claims you used a live AI tool when you did not.

Objectives

  • Take a dated snapshot with a reason line before a risky edit
  • Attempt the risky edit and judge it by its criterion
  • Restore the snapshot and retry smaller

  1. Step 1

    Snapshot

    Copy your project folder (or the course sample files) to a dated name with a reason: e.g. folder-2026-10-05-before-gallery. Write the reason line in your notes.

    snapshot-log.mdmarkdown
    SNAPSHOT LOG (template)
---
Date: ____
Reason: before ____
Location: ____
Restore time: ____
Lesson: ____

  2. Step 2

    Risk and judge

    Attempt something you do not fully understand (a layout technique, a storage change). Judge it strictly: criterion missed twice or any regression means failed.

  3. Step 3

    Restore and retry smaller

    Restore the snapshot copy as the working project, note one lesson line, retry at half size. Record restore time; it must be under five minutes.

How to confirm it worked

  • Snapshot with date plus reason exists before the risky edit
  • Risky edit judged strictly with the verdict written
  • Restore completed under five minutes with lesson line
  • Retry at half size recorded

Workspace

0/2 checks passing · Coverage only, not a quality score.

Draft kept in this browser.

Hints, in three stages

Stage 1: a nudge

Pick a genuinely risky edit. Safe edits teach nothing about rollback.

Stage 2: a direction

The verdict must be written before restoring. 'Failed: cleared values on submit' beats vague regret.

Stage 3: almost the answer

Half-size retry is the point. Rollback without a smaller retry is just undo; with it, it is learning.

Worked solution (open after an honest attempt)

Worked solution. Snapshot folder-2026-10-05-before-gallery taken. Risky edit: gallery with grid technique, breaks menu at 360px twice. Verdict written: failed, layout regression. Restore in two minutes. Retry: single image first, verified, then the row. Lesson: additions last and small.