Module 1 · Build a Website Business · Day 7 of 10

Fix things when they break

Something breaking isn't a crisis — it's the most normal part of building anything real. Today you practice the fix loop on purpose.

Video — recording pending, script below stands in for now

Video script (for recording): "Everyone who builds things breaks things. Today you learn the exact loop for fixing it fast, so the next real bug doesn't rattle you."

Where you are

Day 01

Install Claude Code, ship your first live page

Day 02

Turn a plain-English idea into a working page

Day 03

Edit what it built — ask for changes without breaking things

Day 04

Understand what got created: files, folders, why they matter

Day 05

Connect to GitHub so your work is never lost

Day 06

Get a site live: your first real deploy

Day 07

Fix things when they break — read errors without panicking

Day 08

Add a second page and link it up: your landing page

Day 09

Automate updates: push once, redeploy every time

Day 10

Ship the deliverable: portfolio + business landing page, live

The debugging loop

Something will break eventually — today you practice it on purpose, on a low-stakes project, so the first real break doesn't panic you. The loop is always the same: reproduce it, read the exact error, hand that exact text to Claude Code.

Vague bug report (slow)

"It doesn't work."

Useful bug report (fast)

"The Services section disappeared after I edited the CSS — here's the exact error from the browser console: [paste it]."

Today's project — break it, then fix it

  1. Ask for a deliberate small bug

    Introduce one small, realistic bug into this project on purpose — something like a typo in a class name that breaks the styling — then tell me what you changed.
  2. Find it yourself first

    Open the live site. Something should look visibly wrong. Try to spot what, before asking for help.

  3. Report it properly

    Something looks broken: [describe exactly what you see]. Find the cause and fix it.
  4. Confirm the fix

    Reload the live site (after redeploying, or locally) and check it's back to normal.