The 3:15 PM Glare and the Spreadsheet That Started It All
It’s 3:15 PM in my Austin home office, the sun is hitting my triple-monitor setup at just the right angle to be obnoxious, and I’m literally typing with one eye closed. The glare feels like a physical weight on my forehead. If you’ve ever spent ten hours straight debugging legacy JavaScript only to realize your eyes feel like they’ve been lightly sanded with low-grit paper, you know the vibe. It’s that specific 'sandpaper' sensation when blinking that makes me want to just keep my eyes shut in a dark room for the rest of the evening.
Before we dive into the logs, a quick heads-up: I use affiliate links on this site. If you decide to try a supplement through one of these links, I earn a commission at no extra cost to you. I’m not a doctor or an optometrist—I’m just a guy who stares at monitors for a living and tracks the results in a spreadsheet. I’ve personally tested and logged every dose mentioned here. Full transparency: I’m 38, I live in Austin (one of the most pollen-heavy, 'allergic' cities in the country), and I’m just trying to optimize my ocular stack so I can keep working without a pounding headache.
For the last 14 months, I’ve been maintaining an 'Eye Fatigue' spreadsheet. It’s a color-coded monstrosity where I track daily fatigue scores (1-10), headache frequency, supplement costs, and my blinking frequency. I realized recently that I am a 38-year-old man who tracks his blinking frequency in Excel; I have officially reached peak developer neuroticism. But when your livelihood depends on your vision, you treat your eyes like a mission-critical server.
The 90-Day iGenics Protocol: Hardware and Costs
I started my 90-day trial of iGenics on January 20, 2026. My baseline was rough. I was averaging an 8.2 out of 10 on my fatigue scale by the end of the workday. I’d already tried the 'hardware' fixes—blue light glasses helped a bit, and I even spent $120 on a high-end monitor light bar thinking it would solve the problem. My spreadsheet actually showed my headache frequency increased after that purchase due to the extra glare bouncing off my screen. Hardware wasn't the answer; I needed to debug the internal system.
The investment for this 90-day sprint was exactly $207. That’s three bottles at $69 each. Breaking it down, the cost per dose came out to $2.30. For the price of a cheap cup of coffee, I was hoping to stop my eyes from redlining by mid-afternoon. I committed to the protocol through April 20, 2026, and I didn't change my screen time or my desk setup during that window.
If you're wondering why I'm so meticulous about this, it's because Computer Vision Syndrome (CVS) is a productivity killer. Some data suggests it can drop worker efficiency by up to 20%. For a freelancer, that’s literally money leaving my bank account because I’m too busy squinting at a linter to actually write code.
Phase 1: The Frustrating Plateau (Days 1-30)
The first month was, frankly, a bit of a letdown. My spreadsheet for late January and early February shows zero movement in the metrics. I was still hitting that 3 PM wall, still reaching for the ibuprofen, and still feeling that 'gritty' eye sensation. I almost marked the experiment as a 'fail' in my log around Day 25. If this were a code deployment, I would have rolled it back by then.
I think this is where most people quit supplements. We’re used to instant feedback—you change a CSS property, you refresh the page, you see the result. Biology has a much higher latency. I stayed the course because I’d already paid the $207, and I’m too cheap to let three bottles of capsules sit in the cabinet. I’ve written before about my 30-day eye supplement experiment notes, and the biggest takeaway is always that 30 days is rarely enough to see a trend line move.
Phase 2: The Turning Point and the Circadian Bug (Days 31-60)
Around March 5 (Day 45-ish), the data finally started to shift. The 'grittiness' I usually felt during late-night deployments started to fade. It wasn't a sudden 'I can see through walls' moment, but rather a lack of negative feedback. You know how you only notice your computer's fans when they stop making noise? It was like that. My eyes just stopped complaining.
During this phase, I stumbled onto a realization that I think is the 'bug' in most eye care advice. Most protocols assume you’re a 9-to-5 office worker. But as a developer, my schedule is often inverted. I’m doing deep work at 2 AM under heavy blue light. Standard daytime supplementation schedules often fail for overnight engineers because our circadian rhythms are flipped. Our eyes aren't getting that dark-room recovery time when the supplements are at their peak concentration in our system. I started shifting my dose to later in the day to match my peak 'blue light bandwidth' usage.
By Day 50, my fatigue score had dipped from that 8.2 baseline down to a 6.1. It was progress, but I was still curious if there was a more efficient way to handle the 'gut-eye' connection I’d been reading about in various health forums.
Phase 3: The Day 65 Breakthrough
The real 'aha' moment happened on March 26, 2026—Day 65 of the protocol. I was finishing up a particularly nasty API integration at 4:00 PM when I realized something was missing: the temple throb. I hadn't reached for the ibuprofen bottle once all week. That weirdly satisfying lack of a headache was the first time I felt like the $2.30 per day was actually paying dividends.
My spreadsheet was finally showing a clear downward trend in fatigue. By the end of the 90 days on April 20, my average daily fatigue score had dropped by 48%, landing at a 4.3 out of 10. More importantly, I calculated that I was gaining about 7.5 productive coding hours per week. I was saving roughly 1.5 hours of 'squint time' per workday—that's time I used to spend rubbing my eyes or staring at the ceiling waiting for a headache to pass.
The Final Spreadsheet Tally: iGenics vs. VisiFlora
So, did iGenics work? Yes, the data doesn't lie. A 48% reduction in eye strain is a massive win for my productivity. However, while iGenics was a solid runner-up in my testing history, my research into the gut-eye connection during this 90-day sprint led me to a different conclusion for my next 'dev cycle'.
I’ve noticed that environmental factors here in Austin, combined with my diet, seem to play a role in how 'inflamed' my eyes feel. I’ve started looking into VisiFlora, which targets the connection between the microbiome and ocular health. While iGenics focuses on the direct 12-ingredient approach for the eyes, VisiFlora’s dual-action approach seems like a better fit for my 'system optimization' goals. I’m actually planning to switch to VisiFlora for my next 90-day spreadsheet sprint to see if I can get that fatigue score down even further.
Key Takeaways from the Log:
- Total iGenics investment: $207 for a 90-day supply.
- Fatigue Reduction: Dropped from 8.2/10 to 4.3/10 (48% improvement).
- Productivity Gain: 7.5 hours per week of deep coding time recovered.
- The 30-Day Rule: Don't trust the data until after Day 40. Biology is slow.
If you're struggling with the 3 PM wall, I highly recommend starting your own log. You can read more about why every developer needs an eye fatigue spreadsheet to get started. It’s the only way to know if a supplement is actually working or if you’re just experiencing a placebo effect. And as always, talk to your own optometrist before you start dumping new variables into your biological system—especially if your vision changes are sudden.
For my next sprint, I'm moving over to VisiFlora to see if addressing the gut-eye connection is the final patch I need for my vision. I'll be posting those spreadsheet results once the 90-day timer hits zero. Until then, keep your linter clean and your brightness down.