# Week 10 — Tuesday, October 27 ### Tutorial due · Final render preparation · *Withdrawal deadline Friday* --- ## Focus Tutorial published. Attention shifts to finishing the demo piece to a presentable standard. --- ## Due today — before 9:00 AM **Project 2 — Tutorial (10 points)** - The published tutorial — **submit the live link** - Required elements: what it teaches and who it is for · the problem · step-by-step process · the *why* at each decision · failure modes · verification · references · AI disclosure if applicable **Weekly progress report.** --- ## Bring to class - The published tutorial, live - The demo piece as it stands - Your list of what remains before final delivery --- ## In class **Tutorial review.** We look at the published version — including how it presents. Formatting, thumbnail, title, description. A well-written tutorial with a bad title does not get read. **Demo piece polish planning.** What gets attention in the final week. Same discipline as Week 5: rank what is left, do the top of the list. **Technique visibility planning.** The final render requires a breakdown that makes the *technique* visible rather than only its result — a node graph walkthrough, debug view, turntable, or before/after. We plan that capture now. **Delivery and export instruction** for your track. **Reflection prep.** What the Week 11 write-up asks for. **Supervised production.** --- ## Before next week 1. **Finish and export the demo piece.** Final render due next Tuesday. 2. **Produce the technique visibility breakdown.** 3. **Assemble process documentation** from your captures. 4. **Write the reflection** — 500–750 words. What did teaching this technique reveal that using it did not? 5. **Prepare your presentation.** Loaded and ready before 9:00 next Tuesday. --- ## Note — withdrawal deadline **Friday, October 30** is the last day to withdraw from a Fall 16-week course with a W. If you are considering it, talk to me before Friday rather than after. In a course this small there is almost always a way to adjust scope, and by this point in the semester you have two of three projects substantially complete. --- ## Note — titles matter more than they should Your tutorial's title determines whether anyone finds it. Some patterns that work: - Name the exact technique and the exact software. *"Double-Exposure Compositing in After Effects"* beats *"My Title Sequence Process."* - State the problem if the technique is obscure but the problem is common. *"Fixing Shoulder Deformation with Corrective Blendshapes in Maya."* - Avoid cleverness. People search for the thing, not for your wordplay. Same for the description: state what it covers, what software version, and what prior knowledge is assumed, in the first two lines.