We Built the Machine. Then We Became It.

There is a particular kind of exhaustion that has no obvious cause.

You end a full day, productive by measure, meetings attended, messages answered, tasks completed, and yet something feels unresolved. Not the tiredness of having worked hard. More like the tiredness of having moved fast in too many directions at once, and arrived nowhere in particular.

I have been sitting with a question that came from a podcast I listened to recently, and which I have not been able to put down: is it possible for a civilization to progress technologically while regressing humanly? I think the answer is yes. To gain more tools, more speed, more output and in doing so, quietly lose something in yourself that cannot be recovered.

We have built systems of extraordinary capability, systems that can generate an idea in seconds, surface ten alternatives, model outcomes, automate entire categories of effort. And in doing so, we have also built a kind of implicit contract: keep moving. There is always more to respond to. Always another angle worth exploring. Always a faster version of whatever you just did. The machine does not pause. And gradually, without quite noticing, neither do we.

What troubles me is not the speed itself. Speed is neutral. The river moves fast and the river moves slow, both are the river.

What troubles me is the forgetting that happens inside us. There is a concept I keep returning to: the difference between generating an idea and keeping it. We are, in this era, extraordinary idea generators. The tools available to us and the pace they encourage mean that we can produce more thinking in a single morning than previous generations might have produced in a month. Connections made, frameworks sketched, possibilities named.

But a thought that is never held is not really thought. It is noise that briefly wore the shape of an insight. I notice this in myself. An idea arrives, genuinely interesting, worth pursuing, and before I have sat with it for even an hour, three newer ideas have followed. The original is already diluted. The notebook fills. The depth does not.

Ancient traditions understood this intuitively, that sitting with an idea, turning it over, letting it disturb you, was at least as important as the initial encounter with it. Knowing something once is not the same as knowing it in your bones. That deeper knowing takes time. It requires a kind of internal transformation that our current pace systematically eliminates.

The optimisation reflex runs deep now. We apply it everywhere: to our schedules, our inboxes, our reading lists, even our relationships. If something cannot be done faster, we ask why not. If a process has a gap in it, we try to fill the gap with more details and more process. But gap is not always waste. Gap is where integration happens. It is where the idea you heard last Tuesday finally connects with the experience you had three years ago. It is where you notice that you are tired, or conflicted, or quietly uncertain, before that tiredness becomes something harder to ignore. What we call inefficiency at times is just the human pace.

I do not think the answer is to reject the tools. That is neither possible nor particularly wise. The tools are real, and so is what they make possible. But I do think we are overdue an honest reckoning with what we are trading away. We optimised for speed, and we forgot to ask: speed toward what? We celebrated the generation of new ideas, and forgot to build the conditions in which ideas mature. We built machines that never rest, and then we were surprised to find ourselves, by the end of most days, feeling as though we have been running without knowing where the finish line is.

The question is whether you know where you are going, and whether you have left in yourself enough stillness to find out.