The Miller's True Grind: On the Patient Work of a Background Task

There’s an old mill near my home, one of those places that seems to exist outside of time. Its great water wheel turns with a slow, deliberate rhythm, a constant, churning presence against the bank. The miller’s work is not one of instant gratification. You don't pour grain in one side and have flour shoot out the other. The process is patient, methodical, and crucially, it happens in the background while the rest of the world carries on.

This came to mind recently while wrestling with a particularly heavy analytics script on a client’s site. The script was vital for their business intelligence, but its eager execution was a lead weight on initial page load, locking up the main thread and making the user wait. Every interaction, every scroll, felt like trying to walk through mud. The user’s immediate need—to read the page—was being held hostage by a process that served a purpose far removed from that moment.

We treated it like the miller treats his grain. We didn't stop the grinding; we simply changed when the mill wheel turned. By shifting that script’s execution off the main thread, using techniques like requestIdleCallback, we let the browser itself decide when to do the work. The page would load, crisp and immediate. The user would read, scroll, click. And only when the browser detected a quiet moment—a pause in the user’s activity—would the great wheel of our analytics script begin its slow, patient turn.

The Unseen Labour

The true craft, much like the miller’s, lies in setting up the mechanism correctly. It’s in the careful prioritization, in knowing which tasks demand the user’s immediate attention and which can afford to wait for a lull. This background work is the unseen labour that makes the foreground experience feel effortless.

We often celebrate the visible speed, the snappy animations, the instant responses. But there is a deeper, quieter kind of performance in the work that happens without fanfare or interruption. It is the performance of consideration, of respecting the user’s focus above all else. The miller’s flour is no less valuable because it was ground while the farmer was at market. In fact, its value is enhanced because its production didn't impede the day's other crucial work.

In our front-end craft, we must learn to be more like millers. To identify the tasks that are important but not urgent, and to build the mechanisms that allow them to complete their work without getting in the user’s way. It is a philosophy of patience, of trusting the browser’s rhythms, and of understanding that the best performance is often the work you never see happening.

Notes & further reading

A few pages I came back to while writing this: