Set a Quit Rule for a Learning Project
Added 2026-11-06
Deciding when to stop first keeps sunk cost from steering.
I am investing in a learning project: [project, time spent, goal, progress]. Set the quit rule: 1) break the goal into verifiable stages with a time cap for each; 2) define success, partial success, and failure per stage; 3) give three signals for stopping — the goal no longer matters, the ratio keeps worsening, the method is clearly wrong; 4) design a pause option and when it applies; 5) say how to keep what was built — notes, artifacts, relationships; 6) name the reasons that do not justify stopping: a temporary setback, others progressing faster.
Site original
Chinese original
Replace these placeholders 1
Swap the bracketed parts for your own details before sending.
[project, time spent, goal, progress]
How to use
Write the quit rule before you start; written after, it bends toward continuing.
Try tweaking it
- Ask for one diagnostic question first to locate where you are stuck.
- Replace "explain it" with "give three progressive exercises; correct me after I answer".
What you should get
- A diagnosis of exactly where you are stuck
- A small set of self-checkable exercises
Common mistakes
- Asking it to explain from scratch, and still not knowing where you went wrong.
- Memorising the explanation as the answer, then failing on any variant.
How to check the output
- It names exactly where you are stuck instead of re-explaining everything.
- Exercises are graded and self-checkable.
Where it works
- Good for: diagnosing where you are stuck, then giving the smallest exercise instead of a lecture.
- Watch out: ask it to flag uncertainty rather than memorising a confident but wrong explanation.