Tomorrow's you is a new hire on yesterday's branch
Sleep clears working memory. Morning you knows the project exists but not which test failed, which flag was on, or which file held the bug. Reloading that state from git history and Slack search can cost forty-five minutes before a single new line ships.
Restart tax is not laziness. It is physics. The fix is not "try harder in the morning." The fix is parking state where cold start can read it in ninety seconds.
Example: Monday after Friday
Example: Friday you fixed auth for staging but left one integration test red. Monday you open the laptop, read email, skim Slack, open three tabs from bookmarks, run the full suite because you forgot the filter, and at 10:30 remember the failing test name.
Friday's last hour of depth evaporated in Monday archaeology.
Parked state would be: branch name, ./vendor/bin/phpunit --filter=OAuthRefreshTest, file app/Auth/TokenRefresh.php line 88, hypothesis "clock skew on expiry edge."
Monday starts with the filter command, not memory.
The four-line restart card
Write these before you close the laptop:
- Outcome: what "done" means for this thread.
- Next action: the smallest concrete step (run X, open Y, try Z).
- State: branch, failing test, URL, or screenshot pointer.
- Landmine: the open question or risk you must not forget.
Example:
Outcome: payments webhook ignores duplicate events. Next: run test --filter DuplicateWebhook and inspect idempotency key path. State: branch fix/webhook-dedupe; test red on second delivery. Landmine: staging uses different header casing than prod.
Minimum park bar
Before standup, dinner, or context switch longer than two hours:
- Commit or stash with message that states intent, not "wip"
- Paste failing test output or error snippet in ticket comment
- One next physical action: file, line, or command
- Note environment quirks: account id, feature flag, port, seed command
That bar matches leave work someone else can continue because future you is someone else.
One first action, not a rebuilt plan
Leave context for tomorrow without overplanning warns against rewriting the whole backlog at night. Same for code: one line beats an essay.
Good: "Add null guard before refresh call in TokenRefresh.php:88."
Bad: "Continue auth work."
Where the note lives
Ticket comment or pull request description beats private scratch unless the scratch is guaranteed open tomorrow. Useful work notes without building a parallel system.
Link the ticket from the commit message so git blame finds context.
Red tests are valid park state
Do not hide failing tests to "look clean." A red test with output pasted is a beacon. A green suite with uncommitted hack is a trap.
If you must stash red work, stash message includes test command and expected failure text.
Branch hygiene
One active feature branch per thread. Park others with last command in ticket, not mental stack. Deep work for developers caps parallel hypotheses for a reason.
Pull main before park if merge is imminent; note "rebase needed" if not done so morning you does not assume freshness.
Morning sequence that respects the park
- Open ticket linked from yesterday's commit
- Checkout branch named in ticket
- Run exact test command from ticket
- Open file at line from ticket
- Do not open Slack until step four completes or emergency interrupts
Morning routine starting remote work can wrap this sequence without adding ceremony.
When interruption strikes mid-block
Same park bar applies: meeting in twenty minutes still gets stash, output paste, next line. Two minutes now saves forty later.
IDE and tool state
Optional: note which run configuration was active. Optional: screenshot of debugger breakpoint if complex. Do not rely on IDE session restore across sleep and updates; it fails often enough to hurt.
Explicit not-tomorrow
One line ruling out tempting sidetracks: "Not tomorrow: refactor UserRepository." Prevents Sunday brain from assigning Monday a different task without noticing.
Weekends and long gaps
Longer gap needs richer park: link to pull request, summarize conversation with reviewer, list open questions. Still one first action, but add "decision pending from Alex on token TTL."
Team handoffs
If you might be out, park bar rises: reproduction steps, stakeholder name, deadline. Your vacation should not force teammate duplicate exploration.
Shutdown pairs with restart
Shutdown routine ending remote workday is the container; park note is the payload. Closing laptop without park is betting memory against biology.
Bad versus good stops
| Bad stop | Good stop |
|---|---|
| "Almost done on auth" | Next failing assertion named |
| Clean desktop, dirty mental model | Clear next command |
| Commit with empty message | Commit or stash with restart card in ticket |
| Push past fatigue "to finish" | Stop at clean compile even if incomplete |
When restart still feels slow
If park notes exist and mornings still drag, look at environment: slow test suite, unclear ticket, or meetings at 09:00 that forbid cold start. Fix system before self-blame.
Also check whether you park ten threads; morning picks wrong one. One primary thread per day from why remote workers need clear next action.
Restarting coding tomorrow is a handoff problem. Write one command, one file, one hypothesis where morning eyes land first. Pay ninety seconds at shutdown to buy an hour before lunch. ## Pairing handoff
When rotating pair, both write the restart card while context is shared. Driver reads it aloud before switching. Pairing without written state still loses half the model overnight.
Stash versus commit
Commit when tests are green enough to share. Stash when messy but reproducible with pasted failure. Never leave dirty tree without note explaining which files matter. ## Make the habit visible
Put the next review on calendar before you close this week. One recurring block beats remembering when tired. If the habit slips, shrink the review to fifteen minutes rather than skipping entirely - continuity matters more than perfection.
Example: what changed this month
Example: Billable ratio fell because sales calls doubled. Maintenance choice is raise quote for new work and batch sales to two afternoons, not pretend the old ratio still holds. Write that sentence in your rate note so January you is not guessing. ## Make the habit visible
Put the next review on calendar before you close this week. One recurring block beats remembering when tired. If the habit slips, shrink the review to fifteen minutes rather than skipping entirely - continuity matters more than perfection.
Example: what changed this month
Example: Billable ratio fell because sales calls doubled. Maintenance choice is raise quote for new work and batch sales to two afternoons, not pretend the old ratio still holds. Write that sentence in your rate note so January you is not guessing. ## Make the habit visible
Put the next review on calendar before you close this week. One recurring block beats remembering when tired. If the habit slips, shrink the review to fifteen minutes rather than skipping entirely - continuity matters more than perfection.
Example: what changed this month
Example: Billable ratio fell because sales calls doubled. Maintenance choice is raise quote for new work and batch sales to two afternoons, not pretend the old ratio still holds. Write that sentence in your rate note so January you is not guessing.