April 8, 2026
Why professionals max out at 2-3 projects (and how to get back faster)
Experienced developers know the unwritten rule: 4+ concurrent projects and something slips. The culprit isn't time, it's the mental model you lose every time you switch.
You’ve been here before. You finish a sprint on one codebase, close the laptop, and spend the next two days on something completely different. Then you come back. You open the repo, scan the last few commits, skim your own comments, and spend the next hour or two just trying to remember what you were even trying to do. By lunch you’re functional. By late afternoon you’re actually productive. You’ve burned most of a day just getting back to where you were.
This isn’t a focus problem. It isn’t about discipline or working smarter. It’s just how expensive it is to reconstruct a mental model from scratch.
There’s a reason most experienced developers cap themselves at two or three active projects at a time. It’s not a rule anyone teaches you. It’s something you learn after the fourth project causes the third one to quietly fall apart. The implicit budget isn’t hours in the week. It’s the number of mental models you can hold in rotation without losing them between sessions.
When you’re in a codebase daily, the model stays warm. You remember why you structured things a certain way, what that weird edge case was, where you left off and what comes next. When you step away for a week, that warmth disappears. The code doesn’t change. Your understanding of it does.
At two or three projects, the gaps between sessions are short enough that you can usually piece it back together in an hour. At four or more, the gaps stretch, the models get colder, and ramp-up time compounds. You stop making forward progress and start spending your time re-learning things you already knew.
What helps is having something waiting for you when you return. Not a general README, not a ticket in Jira, but a specific snapshot of where you were: the files you had open, the decision you were working through, the next step you’d already thought through but hadn’t executed yet. That’s the difference between an hour of archaeology and picking up mid-sentence.
That’s what KeepGoing’s re-entry briefing does. When you come back to a project, it shows you exactly what you were working on, which files changed last, and what you’d set as the next step. The five-minute read replaces the half-day ramp-up.
If you’re managing two or three projects right now and feeling the friction every time you switch, it’s worth installing the VS Code extension and letting it capture a checkpoint before you close out for the day. Coming back cold is a solvable problem. You just need something to hold the context while you’re gone.