You take a week off. You come back, open the repo, and for about twenty minutes you are a complete beginner in a codebase you wrote yourself. The function names look vaguely familiar. You're sure past-you had a plan. You just can't remember what it was, or which of the seventeen markdown files on your desktop is the one that's actually current.
If you build solo, especially with AI assistants doing a lot of the typing, this feeling is sharper than it used to be. The code moves fast. Your memory of why it moves does not.
Here's what I've learned: the thing you lost over the week isn't skill. It's context. And context is recoverable if you treat it like a first-class artifact instead of something that lives only in your head.
The trap: trusting your own notes
I keep a checkpoint document. After every session I write down where things stand, what's next, and the open threads. Coming back, that doc is the single most valuable file in the project. It is also a liar.
Not on purpose. It just goes stale. I came back this week, opened the checkpoint, and it told me a specific cleanup job had ~215 items left in one place and ~154 in two others. Concrete numbers. Easy to plan around.
So I almost planned around them. Then I ran the actual check against the code instead of the note. The real numbers were lower. Work had continued after the note was written, and the note never caught up. If I'd trusted it, I'd have scoped a sprint against figures that were days out of date, and wondered later why nothing added up.
The lesson isn't "stop taking notes." Notes are how you rebuild context in minutes instead of hours. The lesson is: a note is a hypothesis, not a fact. Coming back from a break is exactly when you're most tempted to skip verification, because the note feels like memory. It isn't. It's a snapshot of a moving thing.
A re-onboarding ritual
After a few of these returns, I stopped winging it and made the first 30 minutes a fixed routine:
- Read the checkpoint. Get the story back: what shipped, what's next, what's blocked.
-
Diff your branch against the source of truth.
git log HEAD..origin/main. Your local state is almost always behind where you think it is. This one command erases half the confusion. - Verify the top one or two claims against the code or production — not the note. Pick the things your next decisions depend on and check them at the source. This is where the stale-note traps get caught.
- Ship the smallest real slice you can. Don't start with the scary architectural item. Find one bounded, self-contained piece, finish it end to end, and merge it. You're not doing it for the feature. You're doing it to get your hands back on the wheel.
That last step is the underrated one. The newbie feeling doesn't go away by reading more. It goes away by shipping something small and watching it work. Momentum is a context-recovery tool.
For the AI-assisted builder specifically
If an assistant is writing a lot of your code, your leverage is no longer typing speed. It's the quality of the context you can hand back to yourself — and to the model — when you sit down again. The builders who stay fast across breaks aren't the ones with the best memory. They're the ones with the best re-onboarding ritual and a checkpoint doc they're disciplined enough to distrust.
So write the checkpoint. Then, every time you return, verify the part that matters against the code before you build on it. The twenty minutes of feeling like a stranger is unavoidable. Spending the next twenty acting on a stale note is not.
Take the week off. Just don't trust the version of the project that existed before you left.
