Skip to content

docs: keep the tasks-app scope note honest across the course #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
recklessop merged 1 commit into from
Jul 2, 2026
Merged

docs: keep the tasks-app scope note honest across the course #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions modules/01-the-copy-paste-problem/lab/starter/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,7 @@ A deliberately tiny command-line task tracker. It exists to be *changed by an AI
enough to read in a minute but real enough to have more than one file, which is exactly where the
copy-paste workflow starts to hurt.

This is the running example for **Module 1** (where you feel the copy-paste problem) and **Module 2**
(where you put it under version control).

@recklessop recklessop Jul 2, 2026

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit — the delete captures the intent, but the new one-liner collapses M2's role into just "safety net." That works for someone reading top-down, but folks who land here from a search for "undo the AI" might miss that this is the repo M2 has them practice git restore on. Two options: (1) keep the delete and reword the new sentence to name the practice explicitly ("safety net you practice with git restore"), or (2) split the sentence and keep an explicit "Module 2" callout. I'd lean (1) — same tightness, doesn't lose the anchor.

This is the running example throughout the course: pain in Module 1, safety net in Module 2, docs in Module 3, agent-driven edits in Module 4, and it keeps showing up all the way to the capstone.

## Files

Expand Down
Loading