The Update That Never Arrives
Our devices renew themselves while we sleep. We do not.
By John Britto Kurusumuthu
Sometime last night, while the house was dark and the phone lay charging on the table, it quietly improved itself. A vulnerability was sealed. A defect was corrected. A feature was added that no one had asked for but everyone would soon use. By morning the device was measurably better than the one set down the evening before, and it had asked nothing of its owner but permission and electricity.
The owner, meanwhile, woke up exactly the same.
This is the strange asymmetry of our age. We carry in our pockets an object that is designed to keep getting better, and we carry it in a body and a mind that are designed, if left alone, to keep getting more certain. Machines now improve by default. Human beings decay by default — not in intelligence, but in currency. The world moves; our settings stay where we last saved them.
What an update actually does
It is worth being precise, because the metaphor is only useful if we take it seriously. A software update is not a single thing. It does three distinct jobs.
It patches vulnerabilities — the flaws through which something hostile could enter. It deprecates code — the old routines that once worked, that no longer serve, that now quietly conflict with everything around them. And it extends capability — the genuinely new function that the earlier version simply could not perform.
Read those three against a human life and the parallel stops being clever and starts being uncomfortable.
The vulnerability we most need to patch is not technical. It is the ease with which we can now be persuaded of things that are untrue, flattering, or profitable to someone else. A mind that has not upgraded its filters in twenty years is not neutral; it is exposed. It is running a critical-thinking module written for a world in which information was scarce and expensive, in a world where it is abundant and free and engineered to move.
The part we never do
Patching and adding, most of us manage. We read. We attend the course. We collect the certificate. Addition is agreeable; it flatters us. A shelf of new books is evidence of a person taking themselves seriously.
Deprecation is the work almost nobody does.
To deprecate is to look at a conviction that has served faithfully for thirty years — about how young people work, about what a family should look like, about who is capable of what, about how a thing has always been done — and to conclude that it is no longer supported. Not that it was wicked. Not that we were fools to hold it. Simply that the environment it was written for no longer exists, and that continuing to run it now produces errors.
This is an unglamorous and slightly humiliating exercise, which is precisely why it does not happen automatically. There is no background process for humility. Nothing installs it at 3 a.m. It costs discomfort every single time, and the cost is paid in public, in front of people who remember what we used to say.
Lag is not a matter of age
It would be easy, and wrong, to read all this as a complaint about the old. Obsolescence has nothing to do with the year of manufacture. There are people of seventy running current firmware — curious, revisable, genuinely interested in being corrected — and people of twenty-five running a build frozen at the moment they last felt certain of themselves. Youth is not an update. It is only a recent installation date.
The real diagnostic is simpler. Ask yourself when you last changed your mind about something that mattered, in a direction that cost you something. If the answer arrives easily, the system is live. If you have to search for it, something has stopped receiving.
The symptoms of a frozen system are familiar enough. There is lag — the growing gap between the speed of the world and the speed of one’s response to it. There is incompatibility — the inability to work with people whose assumptions were written after one’s own. And there is rigidity, which we usually experience from the inside as principle, and which others experience from the outside as simply being unreachable.
Why the analogy finally breaks
Every metaphor has a point at which it fails, and this one fails in an instructive place.
A phone does not choose to update. It has no opinion about the version of itself it is asked to become. The improvement is done to it, by parties who have their own reasons, and it accepts the new configuration without complaint because it has no self to defend.
We are not in that position. Every human update is a small act of authorship. It requires a person to decide what is worth keeping, what is worth surrendering, and who they are prepared to become — and to do so knowing that no one will install it for them and no one will notice if they don’t.
That is the burden. It is also, quite exactly, the dignity of the thing.
The reversal
There is one last observation, and it is the one worth carrying away.
The applications on your phone are updated with great diligence and at enormous expense, and it is worth asking plainly whose interest that serves. Each refinement is measured, tested, and released with a purpose: to hold your attention a little longer, to make the leaving a little harder, to convert a few more minutes of your life into value on someone else’s ledger. Those updates are real improvements. They are simply not improvements to you.
Self-improvement is the only update in the entire system that runs in your own interest. It is the only one nobody pushes to you, the only one that installs nothing unless you consent to the discomfort, and the only one that gives your attention back rather than taking more of it.
Which raises the question that ought to end this, and which cannot be answered by anyone else on your behalf:
Your phone updated itself last night. When did you last update yourself — and what, precisely, are you still running that should have been retired years ago?
Rise & Inspire | Technology and the Examined Life
Explore more at the Rise & Inspire archive | Personal Development |
© 2026 Rise & Inspire.
Website: Home | Blog | About Us | Contact| Resources
Word Count:1088
