Why My Engineer Brain Almost Ruined Reading Time

The instinct to optimize meets the most unoptimizable thing in the house

I should tell you something about myself that I’ve mostly kept out of these letters: I’m a software engineer. Thirteen years of it. I build systems for a living, and I am paid, specifically, to make things measurable, efficient, and fast.

You can imagine what I did when my son was born.

I read about reading. I made lists. Somewhere in my notes app there is — I’m not proud of this — a plan. Milestones, inputs, a rough schedule of what should happen when. If you’d asked me at the time, I’d have said I was being intentional. Looking back, I was doing what engineers do to everything we love: instrumenting it.

Here is the problem. Reading time refused to behave like a system.

The bug that wasn’t a bug

My son wanted the same book. Not a rotation of enriching titles. The same one. Again. And when we finished it, again.

My engineer brain filed this immediately as a defect. Repetition without variation is a stuck loop. A stuck loop means something’s wrong. My job, obviously, was to unstick it — introduce new material, vary the inputs, keep the system progressing.

So I’d reach for a different book, and he’d push it away, and I’d feel a small, ridiculous flicker of professional failure. The pipeline has stalled.

Except it hadn’t. I just couldn’t see what was running.

Somewhere around the fortieth read — and I mean this literally, we were deep into double digits — he started finishing the sentences before I did. Then correcting me when I skipped a word to get to bed faster. Then pointing at the word while he said it.

The loop wasn’t stuck. The loop was the program. Every reread was a pass over the same data, and each pass was doing something I couldn’t observe from the outside: matching sounds to shapes, predictions to outcomes, this word to that one. The repetition I kept trying to fix was the exact mechanism doing the work.

I had found a bug in production and the bug was me.

What was actually building the reading life

When I stopped trying to manage it and just looked at what was working, none of it resembled my plan.

It was books from birth — not scheduled, just around, in every room, the way cups are around. It was the same handful of favourites read into the ground. It was Alphablocks on the days screens happened, and stories on the Yoto player during the long stretch before dinner, and magnetic letters migrating around the fridge for months before they spelled anything.

Notice what’s missing: drilling. Flashcards. A curriculum. A tracker. Anything with a progress bar.

Nothing about it was efficient. It was slow, repetitive, unmeasured, and frequently boring for the adult involved. And it worked — not despite those qualities, but because of them. He learned to read the way children learn to talk: by marinating in the thing, at his pace, with someone he loves nearby.

There was no dashboard for that. There couldn’t be. The most important variables — comfort, curiosity, the feeling that books are where good things happen — don’t emit metrics.

The wrong metric, not the wrong brain

I want to be fair to my engineer brain, because in the end it didn’t ruin reading time. It almost did, and then it became useful — once I gave it a different job.

The instinct to optimize was pointed at the wrong metric. I was optimizing for visible progress: new books, new words, new milestones. What the system actually needed was reliability: the same lap, the same time of night, the same beloved book, for as long as he wanted it. Boring is a feature. In my day job we’d call it stability.

And the one engineering habit that survived — the only one — is observation. Not tracking. Watching. Noticing that tonight he’s looking at the words instead of the pictures. Noticing which page he always slows down on. Observation without a spreadsheet attached turns out to be most of the job.

I wrote last week about the ten seconds before you help. This is where those ten seconds came from. I didn’t develop patience because I’m a naturally patient person. I developed it because I watched my own optimizations fail against a three-year-old and a book about a bear, repeatedly, until the data forced me to update.

If you have an optimizing brain too

You don’t have to be an engineer to have one. Plenty of parents run the same firmware — the milestone-checking, the app-downloading, the quiet arithmetic of whether your child is ahead or behind. The instinct comes from love. It just points the wrong way.

So here is the whole method, such as it is: keep the books within reach, reread the favourite past the point of your own boredom, let the letters live on the fridge doing nothing, and watch instead of measure.

The reading life we ended up with looks nothing like the one I planned. It’s better, and I can’t take credit for the difference. All I did, eventually, was stop interrupting it.

Some systems don’t need an engineer. They need a lap, a lamp and the same book again.