Design for low-motivation days
Motivation shows up for the first week. Consistency is what you do on the dull Wednesday. Make the session so small that skipping feels sillier than starting: open the editor, finish one exercise, commit or save the file. Identity helps — “I run code on weekdays” — but identity needs evidence. Keep a simple log: date, what you ran, pass/fail.
Remove friction the night before: bookmark the lesson, leave the editor open, put the next lab slug in a note. Add friction to distractions: phone in another room for twenty minutes. You are not trying to feel inspired. You are trying to keep the chain of proof that you are someone who practices.
Make progress visible
- A folder of finished programs beats a vague sense of ‘studying’.
- Labs with green checks are cleaner feedback than vibes.
- A weekly review: three things that work, one stuck point, next focus.
When you stall, shrink the goal; do not abandon the schedule. Pair with daily practice and a tiny project so the calendar has a destination, not only lessons.
Never miss twice. Missing once is life. Missing twice is a new habit of stopping.