Last November, specifically on 2025-11-15, I hit a wall. I was halfway through a messy code review for a client here in Austin, staring at my vertical side monitor, when the text started to vibrate. Not a physical vibration—my corneas were just throwing a 404 error. This was the peak of my 3 PM headache routine, a daily performance degradation I’d been dealing with since I went fully remote three years ago.
Quick heads-up: I use affiliate links on this site. If you decide to buy something through them, I earn a commission at no extra cost to you. I only recommend stuff I’ve actually tested and logged in my spreadsheet. I have zero medical training—I’m just a guy who stares at code until the semicolons start swimming, so definitely talk to your own eye doctor before trying anything new.
The Debugging Process: Why I Started Logging My Eyes
As a developer, when a system is failing, you don't just guess what's wrong—you check the logs. But for two years, I treated my eyes like a legacy system I didn't want to touch. I bought the blue light glasses, adjusted my refresh rates, and hoped for the best. When that didn't work, I realized I needed a data-driven approach. I needed an Eye Fatigue Spreadsheet.
I started tracking everything: hours of screen time (usually 10+), my eye fatigue score (1-10), what I ate, and what supplements I was testing. I’ve spent the last 14 months in a supplement rabbit hole, testing seven different products to see if anything could actually move the needle. If you’ve read my 30-Day Eye Supplement Experiment: Debugging My Vision After 14 Months of Spreadsheet Tracking, you know I don't take these things on faith. I want to see the trend line in my Excel docs.
My setup is pretty standard for a freelance dev: three 4k monitors. One primary, two vertical. It’s great for productivity, but it’s like running a high-load server with a failing cooling fan. By mid-afternoon, my "fan" (my eyes) was screaming. According to organizations like the Mayo Clinic, digital eye strain is a direct result of this kind of intense focus, but knowing the name of the problem didn't fix the headaches.
The 14-Month Log: What My Data Revealed
For the first few months of my tracking, the data was depressing. My fatigue scores were consistently 8/10 by 4 PM. I tried the standard lutein and zeaxanthin pills you find at the grocery store. They were cheap, but my spreadsheet showed zero correlation between taking them and feeling better. It was like adding more RAM to a machine with a CPU bottleneck—it looked good on paper, but the system still lagged.
I even went through a phase where I returned four different supplements because they either made me jittery or did absolutely nothing. I wrote about that disaster in my post on the 3 PM Wall and the gut-eye connection. The turning point happened around 2026-01-05. That’s when I shifted my focus from just "eye vitamins" to supplements that actually addressed the physiological stress of screen work.
The Gut-Eye Pivot
One thing that surprised me in my research was the link between gut health and eye inflammation. I’m not a doctor, but as a guy who optimizes systems for a living, it made sense. If the internal logistics of the body are off, the peripherals (the eyes) are going to suffer. This led me to VisiFlora, which was the first supplement that actually changed my fatigue scores from a steady 8 to a manageable 3.
I started VisiFlora in early January. By 2026-03-12, my logs showed a significant drop in the frequency of those 3 PM headaches. Instead of hitting a wall, I was actually able to push through to 6 PM without feeling like I needed to lie in a dark room. It costs about $69 a month, which isn't cheap, but compared to the billable hours I was losing to headaches, the ROI was obvious.
How to Build Your Own Eye Fatigue Spreadsheet
If you're a dev and your eyes are burning, stop guessing. Open a Google Sheet or an Excel doc and create these columns:
- Date: Obvious, but necessary for spotting weekly trends.
- Screen Time (Hours): Be honest. Include the late-night scrolling.
- Fatigue Score (1-10): Rate your discomfort at 12 PM, 3 PM, and 7 PM.
- Supplement/Intervention: What are you taking or doing (e.g., 20-20-20 rule)?
- Headache Flag: A simple binary (1 or 0) for whether you got a headache.
In my experience, the data doesn't lie. I noticed that my fatigue scores were actually 15% higher on days when I skipped my morning walk, regardless of what supplements I took. But the real shift came from the internal support. While I mostly stick with VisiFlora now because of the easy one-capsule dose, I also tested iGenics for a few weeks. It’s a solid runner-up with 12 vision-supporting ingredients, though the capsules were a bit larger than I liked, and it took a bit longer to see the data trend upward in my spreadsheet.
Optimizing the Human Hardware
We spend thousands on mechanical keyboards, ergonomic chairs, and high-refresh-rate monitors. It’s ironic that we treat our actual eyes—the most important hardware in the stack—as an afterthought. After 14 months of testing, I’ve realized that screen habits only go so far. Sometimes the system needs a patch from the inside.
I'm still staring at my three monitors for 8 to 10 hours a day. That hasn't changed. But the way my eyes handle that load has. For a deeper look at how I tracked this day-by-day, check out my VisiFlora Review: 60 Days of Testing With Weekly Check-Ins. It’s got the specific week-by-week breakdowns of how my fatigue scores dropped.
The bottom line? Start tracking. Even if you don't buy a single supplement, just seeing the data on your screen time and fatigue levels will change how you work. And if you do decide to try a supplement, give it at least 30 to 60 days to show up in your logs. Your eyes aren't a quick-fix script; they're a complex system that takes time to re-optimize. If you're tired of the 3 PM wall, I'd suggest starting with something like VisiFlora—it’s been the most consistent "patch" for my digital eye strain so far.
Just remember to keep the spreadsheet updated. Without the data, you’re just debugging in the dark.