Your best days and worst days are 40 minutes apart

Some days you close three PRs before lunch. Other days you stare at a function for 90 minutes and write nothing useful.

Same codebase. Same you. Completely different output.

A University of Toronto study tracked participants for 12 weeks and put a number on that gap. The difference between a peak mental sharpness day and a low one: roughly 40 extra minutes of productive work.

What the research found

The team measured daily mental sharpness and tracked whether people followed through on their goals that day. When participants were sharper than their personal baseline, they completed more tasks and set harder ones. On low-sharpness days, they stalled on routine work too.

The key finding is that these swings are within-person variation. They're not about being a sharp or slow person in general. The same person produces at very different levels depending on where they land on any given day.

You already know this from experience. The study just quantified it: 40 minutes.

What controls where you land

Three factors reliably predict your daily sharpness: sleep quality, time of day, and mood.

Sleep quality - not just hours - is the biggest lever. One bad night can put you below baseline before you've opened your IDE.

Time of day follows a predictable curve. Most people peak in the late morning and hit a valley around 1-3pm. Working against that curve costs real output.

Mood matters more than people want to admit. Low mood reduces executive function in ways that show up in your code. You can't think around it.

The overwork finding is worth paying attention to: short-term intensity can temporarily push sharpness up. But sustained overwork - weeks of long hours - gradually lowers your baseline. You're borrowing from future days to fund today.

The part most developers skip

You can't fully control sleep quality every night. Your calendar largely dictates when meetings land.

Movement is the lever you actually have access to during the workday.

Brief physical activity directly addresses two of the three sharpness drivers. A 5-10 minute movement break raises alertness and shifts mood via endorphins and cortisol reduction. That effect shows up within minutes of starting to move - not after a full workout.

I built Movedoro because I kept having low-sharpness days I was blaming on hard tasks or messy code. Some of it was the work. A lot of it was a baseline that was lower than it needed to be because I hadn't moved since morning.

40 minutes a day, compounded over weeks, is a lot of code.