How to Stop Tutorial Hopping This Month. A Build Next Stack field guide for learners shipping small projects.
Name the tutorial you are finishing
Tutorial hopping starts when no single course owns the month. Write one line at the top of your notes: Primary tutorial: [exact title + platform] until [date]. Everything else is reference, not parallel progress.
Post the line where you will see it—repo README, sticky on monitor, phone lock screen for three days. Naming creates a finish line hopping avoids. If you cannot name one primary, you are browsing, not learning.
Finishing does not mean every bonus chapter. Finishing means the instructor’s core outcome exists in your repo as runnable code you can explain.
Jon named Primary: Full-stack todo course on Platform X until July 28 and closed nine other tabs into graveyard.md. The visible finish date hurt when chapter six dragged—it also kept him from starting a shiny Rust side quest mid-week.
One output artifact per course
Define the artifact before chapter two:
- Web course: deployed URL or screen recording of core feature working
- Language course: one script in your project that imports a pattern from the course
- Tool course: config file committed with comments tying each section to course timestamp
No artifact, no complete—regardless of progress bar percentage. Progress bars measure video watched, not skill transferred.
Artifact size should fit one evening to demo aloud. Huge artifacts become second projects that justify hopping away.
Jon defined artifact as todo app with deploy URL and login—not production SaaS. Narrow artifact made finishing possible while working full-time.
The bookmark graveyard rule
When a new tutorial tempts you, add it to graveyard.md with date and one-line reason—looks better for React Query v5—then return to primary. Do not start graveyard items until primary artifact ships.
Review graveyard on the finish date. Most entries will look stale or redundant; delete without guilt. Graveyard captures curiosity without letting it fork the month.
If graveyard exceeds ten items before primary finishes, your primary was too large or too boring. Shrink primary scope instead of promoting graveyard items.
Share primary line with an accountability partner who will ask once mid-month: artifact yet? One question prevents silent scope drift.
Pair tutorials with a repo branch
Create branch tutorial/[short-name]. All course code lives there until merged or abandoned. Main stays deployable. Branch isolation prevents half-finished lesson code from breaking demos you show friends.
Commit after each chapter with message ch3: forms validation exercise. Commits become a map when you return after a busy week. Clean squashes can wait until artifact ships.
When the course ends, either merge useful patterns into main or delete the branch with a short note in learning review explaining what transferred.
Jon tags commits that match course sections so he can cherry-pick patterns without merging tutorial cruft—demo auth pages stay on branch, validation helper merges to main.
Mid-course checkpoint at hour three
At roughly three hours of primary tutorial time, pause for a fifteen-minute checkpoint:
- Can you demo one feature without scrubbing backward in video?
- Is the artifact closer or did you redefine the artifact to something bigger?
- Are you still on the same primary named on day one?
If demo fails, redo one chapter with typing-only notes—no playback speed above 1x. If artifact grew, cut scope today. If primary changed, you hopped—pick one and write a new finish date honestly.
What to do when the tutorial is outdated
Outdated tutorials happen mid-month. Do not hop immediately. Ask: Does the concept still match my artifact? If yes, finish with official docs filling version gaps—note mismatches in errors.md as you go. If the stack diverged entirely—course uses Create React App, you need Vite—finish one module for pattern language, then switch primary once with a written reason, not a silent tab switch.
Document version deltas in the repo README so future-you knows which commands were translated. Translation work is learning; pretending the course matches production is not.
When you switch primaries, write a one-paragraph postmortem in learning review: what artifact shipped from the old course, what transferred, what was sunk cost. Honest postmortems prevent shame-spiral hopping.
When finishing feels worse than hopping
Chapter seven boredom is not a signal to swap courses—it is a signal to tighten artifact scope or pair video with typing-only notes. Jon’s hour-three checkpoint caught him rewatching the same clip; he paused playback and typed the next feature from memory instead.
If the instructor’s pace is too slow, increase playback modestly but ban pausing to implement until the section ends—then implement without scrubbing back. If you scrub back twice, the section is too dense; split artifact into a smaller demo.
Social feeds will always show a course that looks newer. Graveyard.md exists so novelty has a parking space without hijacking the month. Finishing one artifact builds credibility with yourself that starting six never will.
Measure the month by artifact demo, not certificates. A screen recording explaining your deploy beats a PDF completion badge you cannot reproduce.
Jon recorded a three-minute Loom of his todo artifact at finish line—no script, just clicks. That video became portfolio proof and forced him to fix one embarrassing bug before sharing.
Pick one tutorial and close the rest from tabs
Choose the tutorial closest to an artifact you need this month. Write primary line and finish date. Close other course tabs into graveyard.md. Run the hour-three checkpoint even if you are already past hour three—late checkpoint beats no checkpoint.
Builders who finish one small artifact learn more than browsers who start six. This month, be a finisher once.
Write the artifact sentence before pressing play on chapter one tomorrow. If you cannot name the demo, pick a smaller course scope before you invest hour one.
Record a short demo within forty-eight hours of finishing—even rough—to lock learning before hopping to the next shiny stack.
When graveyard.md shrinks because items feel obsolete, celebrate—you finished fast enough that novelty did not outpace skill.