# Week 8 — Tuesday, October 13 ### Consultation · Demo build and process capture --- ## Focus The demo piece works, and you have the process material to explain it. Both halves matter equally this week. --- ## Due today — before 9:00 AM **Demo piece in progress** — functional, with captured process material. **Weekly progress report.** --- ## Bring to class - The demo piece as it stands - Your captured process material — screenshots, recordings, notes - The tutorial outline, updated with anything you learned while building --- ## In class **Demo critique.** Does it show the technique clearly? Is anything in it distracting from what you are trying to teach? Usually the note is to simplify. **Process material review.** We look at what you captured. Gaps get identified now, while you can still go back and re-capture — the alternative is discovering the gap in Week 10 with the file long since finalized. **Outline revision.** Building the demo almost always changes the outline. Steps turn out to be in the wrong order, or one step turns out to be three. Update it. **Technique instruction** as needed. **Supervised production.** --- ## Before next week 1. **Finish the demo piece to a working standard.** Polish comes later; function comes now. 2. **Draft the tutorial rough cut.** Full pass, start to finish, rough. Same principle as a first draft — complete beats polished. 3. **Write the failure-modes section.** What went wrong for you, what it looked like, how you fixed it. Do this while it is fresh. --- ## Note — the section nobody writes Almost every tutorial online covers the happy path: do this, then this, then this, and it works. Almost none cover what happens when it does not work. Which is the situation the reader is actually in, because people generally seek out tutorials *after* something has gone wrong. Your failure-modes section is the most valuable part of your tutorial and the part that will get it linked and shared. You have spent weeks generating material for it. Write down every dead end, every wrong setting, every "why is it doing that" moment — and what the fix turned out to be. That is the section that makes your tutorial worth finding.