I was standing in the kitchen one rainy Tuesday morning, staring at a box of cereal for five minutes because I couldn't decide if I wanted breakfast or just another cup of coffee. It sounds pathetic, I know. But in Portland, where we get an average annual rainfall of 36 inches, the grey mornings can already feel heavy. Adding a mental deadlock over Cheerios vs. Granola was a clear sign that my internal processor was redlining. I wasn’t hungry; I was just out of 'choice juice.'
After three years of remote work, my focus had basically dissolved into a soup of back-to-back Zoom calls and solo coding sessions. I realized something was genuinely off when I missed two client deadlines in the same month late last year. For a guy who spent a decade in offices without a single late delivery, this was the equivalent of a total system failure. I wasn't just tired; I was suffering from a massive 'choice tax' that I didn't even know I was paying.
The Hidden Choice Tax of the Freelance Life
When you work in a traditional office, about 70% of your day is pre-configured. You know when you’re leaving, what the dress code is, and usually, where you're getting lunch. As a freelance developer, every single one of those variables becomes a manual configuration. Research from Cornell University suggests the average human makes roughly 35,000 decisions every day. When you’re remote, that number feels like it doubles because the guardrails are gone.
I started noticing that by the time I actually opened VS Code, I had already spent a significant portion of my cognitive energy on low-stakes nonsense. Should I work from the desk or the couch? Should I use the dark theme or the high-contrast one today? Should I answer that Slack message now or in ten minutes? It’s like trying to run a high-end graphics engine on a machine that’s already using 90% of its RAM on background processes. You’re going to get lag.
The worst part was the sensory overload. I remember one afternoon vividly: the hum of my laptop fan getting louder while I stared at a blank README file, paralyzed by which library to import for a simple state management task. I had five different tabs open with five different docs, and I couldn't pick one. It felt like my brain was a hard drive with a failing read/write head. Look, I’m not a doctor or some productivity guru—I’m just a guy who got desperate enough to start tracking his own brain metrics like they were server logs.
The Experiment: Hard-Coding the Routine
Late last November, I decided to treat my life like a legacy codebase that needed a massive refactor. I needed to eliminate the 'spaghetti code' of my daily routine. I started by removing every low-stakes choice I could find. I adopted a 'work uniform'—five identical black t-shirts and two pairs of the same jeans. I moved to a recurring meal plan where lunch was always a specific burrito bowl from the place down the street. No thinking, just execution.
I also set a rigid 'no-choice' morning routine. Alarm at the same time, coffee brewed the same way, and phone kept in the other room until at least mid-morning. I even stopped tweaking my IDE settings. In web dev, we deal with precision—like the 6-character hex code that defines a specific shade of blue. I realized I was spending 'hex-code energy' on things that didn't matter, leaving me with nothing but 'placeholder text' energy for my actual work.
About six weeks into this, I noticed a shift. The sharp, pulsing tension behind my left eye that only flared up when I had more than ten browser tabs open started to fade. I wasn't reaching for a third cup of coffee by 2:00 PM anymore. I was saving my 'decision budget' for the complex debugging sessions and architectural problem-solving that actually paid the bills. Honestly, it was a relief to realize I wasn't burning out; I was just over-provisioned on small choices.
The Contrarian Angle: Cognitive Resistance Training
But here’s where I’m going to go against the grain of every productivity blog you’ve ever read. Most people tell you to automate *everything* to save energy. I tried that, and for a while, it worked. But then I hit a plateau. I found that if I automated too much, my brain actually got 'flabby.' When a truly difficult architectural decision came up—like refactoring a massive database schema—I felt even more paralyzed because I hadn't exercised my decision-making muscle all day.
I started experimenting with what I call 'Cognitive Resistance Training.' Instead of automating every minor choice, I began intentionally increasing my daily micro-decisions in the morning to build the stamina required for the big stuff later. I’d pick a new, slightly challenging recipe for breakfast, or I’d force myself to choose between three different paths for my morning walk. It sounds counterintuitive, but it’s like warming up your muscles before a heavy lift. I have zero medical training, and you should definitely talk to your own doctor if you're feeling chronically exhausted, but for me, this was a game-changer.
By making these intentional, low-stakes choices early, I was 'priming' my brain to handle the high-stakes choices later. It’s the difference between a cold start and a warm one. I actually wrote about this when I was looking into whether NeuroPrime was actually worth the premium price tag for people like us who spend eight hours a day in a terminal. Sometimes you need the right fuel, but you also need the right warm-up.
Monitoring for Brain Fatigue Symptoms
By mid-February, I had a system. I knew exactly when I was hitting my limit. I learned how to spot brain fatigue symptoms before they impacted my client projects. If I found myself clicking through browser tabs without reading them, or if I spent more than sixty seconds staring at a Jira ticket without processing the requirements, I knew the budget was spent.
The turning point came on a Friday afternoon when I had to make a call on a critical API integration. Old me would have deferred it to Monday, adding to the Sunday Scaries. New me—the one who had been 'training' my decision-making and protecting my budget—spent ten minutes weighing the pros and cons, committed to a direction, and pushed the code. No eye tension. No second-guessing. Just a clean exit to the weekend.
It’s important to remember that freelance freedom isn't about the ability to choose everything every single day. That's a trap. True freedom is having the systems in place that protect your focus so you can choose the things that actually matter. I still drink way too much coffee, and my home office still doubles as a living room, but the missed deadlines are a thing of the past.
The Reality Check
We like to think of ourselves as logical machines, but we’re more like biological systems with finite bandwidth. If you're struggling with focus, it might not be a lack of discipline. It might just be that your environment is forcing you to make too many 'null' decisions. Check with a professional if things get worse, but in the meantime, try looking at your routine as a piece of code. Where are the memory leaks? Where can you refactor to save on CPU cycles?
I’ve found that rebuilding my coding flow was less about finding a magic app and more about realizing that my brain has a daily quota. When it's gone, it's gone. Don't waste it on the cereal box. Save it for the code that pays for the cereal. It takes time to find the balance between automating the mundane and keeping your mind sharp with intentional choices, but once you find that sweet spot, the 'choice tax' starts to feel a lot more manageable.
Accepting that you can't—and shouldn't—choose everything is the first step toward actually getting things done. Now, if you'll excuse me, I have a README to finish, and I've already decided exactly which library I'm going to use.