My cursor is parked in a search bar I don't remember opening, floating over one of maybe forty tabs, and I've genuinely lost the thread on which one has the API documentation I was reading two minutes ago. This is the kind of moment that used to happen to me weekly as a remote worker, and it's exactly why I rebuilt my entire approach to cognitive load and browser workflow instead of just buying another app. Developer productivity, for me, turned out to have almost nothing to do with typing speed and everything to do with how much mental scaffolding I was rebuilding every time I switched tabs.
Missing two client deadlines in the same month is what finally forced the issue: something that had never happened across a decade in an office. Remote work had been quietly eroding my focus for years, and the missed deadlines weren't garden-variety laziness so much as something closer to a system failure; there's a real, specific difference between brain fog and just not trying hard enough, and sorting out which one I was actually dealing with took longer than I'd like to admit. The fix, once I found it, was almost stupidly simple: stop organizing tabs by project, and start organizing them by the kind of thinking each task actually requires.
Project Windows Made Everything Worse
The first fix I tried was the obvious one: organize by project. One window for the e-commerce client, one for the fintech build, one for my own site. It maps neatly onto how you'd structure folders on a server, so it felt right. Weeks in, it was clearly making things worse, not better.
Every time I alt-tabbed into the "Project A" window, my brain had to figure out which mode it was supposed to be in, reading, writing, replying, reviewing, because the live site, the docs, the Jira board, and three Stack Overflow tabs were all crammed into the same space. That mental context switch is its own tax on your bandwidth, and twenty-six-plus tabs sitting open at once is basically a passive trap for paying that tax over and over before you've written a single line of code. Somewhere in the middle of a gray Portland winter, it clicked: my brain didn't actually care which project it was working on. It cared what kind of thinking the moment required.
Building a Browser Workflow Around Three Kinds of Thinking
So I scrapped windows-as-project-buckets and rebuilt around browser profiles instead: one profile per cognitive state, not per client. Most browsers support multiple profiles now, and treating each one as a separate room turned out to matter more than any single tool I'd tried. Where you physically carve out a deep-work zone in your home matters too, especially in a small rental, but that's its own separate problem from the software side, which is where I actually found traction.
Writing Code With Nothing Else Open
Profile one is execution only. Local dev environment, staging site, the one API endpoint I'm currently hitting; nothing else. No email tab, no Slack, no "quick" how-to article open in the background. If I'm in this profile, I'm writing code, full stop. One-in-one-out is the rule: if I need to check a new doc page, I don't open it here, I switch rooms.
Almost nothing pulls me out of this profile anymore. One exception: if a deployment breaks on a Friday night, Rosamund Achterberg — my old college roommate, now a UX designer here in Portland — is still the first person I call, not because she can fix my stack trace but because complaining to someone who gets it is apparently part of my process too.
Keeping Research Away From the Keyboard
Profile two is learning mode: the Stack Overflow tabs, the MDN pages, the GitHub issues I'm digging through to understand something before I touch the code. Separating this from execution stopped me from the copy-paste-and-hope loop, where you grab a snippet without actually understanding what it does. I go to research to learn, then I go back to execution to build. Two different jobs, two different rooms.
Why Admin Work Needed Its Own Room
The third profile is Slack, Jira, Notion, email: everything that makes me feel more like a manager than a maker. Zoom fatigue is a whole separate fight that deserves its own post, but a good chunk of it traces back to admin and meeting tabs bleeding into deep-work time instead of staying contained. I only open this profile during scheduled blocks, usually after lunch or at the end of the day.
One Tuesday, a client asked if I'd seen their note from days earlier, and my stomach dropped; the message had been sitting open in a sea of identical-looking tabs the whole time, and I'd genuinely just stopped seeing it. It had become wallpaper. When everything lives in one window, nothing gets flagged as important. Moving admin tasks into their own profile means I actually process them instead of watching them rot in the background.
Sensory Friction and the Rest of the Puzzle
Tab organization is maybe half the fix. The physical toll of staring at a screen all day chips away at focus just as fast as a messy browser does, and I've written separately about how to reduce eye strain and brain fatigue with better desk lighting, which covers a chunk of what finally got my eyes to stop feeling gritty by mid-afternoon.
Supplements were the other half of my testing, and I tried to be honest about what actually did anything versus what was an expensive placebo. A strict keto stretch for about ninety days is the one that stings most to admit: it cleared the fog fast, but it fell apart the moment a real crunch month hit and I needed carbs and decision-making energy at the same time.
Timing when you take a supplement relative to your first deep-work block matters almost as much as which one you pick, and I never dug into the actual ingredient mechanisms behind why a couple of them seemed to help; I just tracked outcomes. For what it's worth, how to improve your memory for work using Neuro-Thrive is one of the few things from that stretch of testing I'm still doing, mostly because it never stopped pulling its weight. None of it replaces a broken workflow, though. If I'd bothered to set a real baseline before swapping things in and out, I probably would've wasted less of that time.
What Changed by Week Eight
Something happened around week eight that stuck with me: I caught myself recalling something a client had said offhand on a kickoff call, word for word, three weeks after the fact. That's not something I could have pulled off the year before. Normally a throwaway line like that would've been gone by the next morning.
Clover, one of the regulars in the focus-tracking Discord channel I moderate, DMed me a screenshot of her calendar around the same week, solid blocks of deep work where scattered, half-finished sessions used to be. Whatever actually triggers a flow state seems to vary person to person, which is a rabbit hole of its own, but the profile split was the one variable we'd both changed at the same time.
Even now, if I duck out to New Seasons Market on SE Division St between blocks, I leave the Admin profile closed the whole time, with no Slack notifications trailing me through the produce aisle and no half-read Jira ticket pulling at the back of my mind.
One Thing I'd Tell My Past Self
None of this makes you a biohacked, superhuman focus machine. It just stops the leaks in the attention you already have. We've all got a limited amount of mental bandwidth in a given day, and most of us are burning a chunk of it just hunting for the right tab in a sea of identical favicons.
Honestly, if there's one thing worth carrying out of this whole mess, it's that the fix wasn't a better tool; it was fewer decisions per minute about where to look. Structure the environment so your brain doesn't have to guess what mode it's in, and the mode takes care of itself.
I still drink more coffee than I should, and my phone still lives in the kitchen most of the day while I work from the living room. Nobody's perfect. But my browser stopped fighting me, my laptop fans finally quieted down, and I'm hitting deadlines again, for whatever that's worth from a guy who is very much not a doctor.