Jamie Okafor

Editor of Focus Work Remote

About

Freelance web developer, Portland, Oregon. Went fully remote in March 2020.

For the first eighteen months it was mostly fine. Then the deep work blocks started compressing. Six-hour coding sessions became four-hour ones, then three-hour ones, then two with the phone charging in the kitchen forty feet away and every notification turned off, still losing the thread by early afternoon.

Two missed client deadlines in January 2023, same month. The second was a React project for a client I'd worked with for two years. I told them it was a family emergency. It wasn't. I just couldn't sustain the focus depth the final sprint required and ran out of days. That was the thing that ended the rationalization: three years of remote work, ten years of office work with no missed deadlines, and two in the same month.

Starting that February, I treated the problem the way I'd treat a persistent production issue: isolate variables, document a baseline, test one thing at a time under conditions that actually stress the system. Supplements, routines, small environmental changes. Rosamund, a UX designer I've been friends with since college, had been running Pomodoro blocks for years and kept suggesting I was just not respecting the technique. She still texts at 9 PM asking if a button label is accessible enough. She was partially right about Pomodoro, but not right enough to account for what was actually happening.

Yuki, who lives directly upstairs, has never touched caffeine and is irritatingly alert by 6:45 AM. We do silent virtual co-working sessions twice a week. The accountability structure helps; the gap between their baseline and mine at that hour was too consistent to blame on sleep alone. That observation went into the tracking notes too.

Six weeks into one supplement I had expected to work, there was nothing detectable. Kept logging. Still nothing by week six. Discontinued. That one is in the archive, because the expensive failures are more instructive than the expected wins.

A developer's framework applied to a non-development problem. For anything brain or CNS-related, your doctor has context about your health history that I don't. Check with them before adding anything new to your routine.

Posts by Jamie Okafor

Disclosure

Some links here are affiliate links. Buy through one, I earn a small commission at no extra cost to you. The commission doesn't determine what gets covered or how. The products that didn't work are documented here alongside the ones that did, because omitting the failures would make the rest of the data meaningless.