A lot of software still thinks being helpful means being present.
Ping the user. Nudge the user. Check in. Follow up. Surface a tip. Offer a suggestion. Celebrate a tiny milestone like the app just watched a toddler use a spoon for the first time.
I hate this.
Not because all interruption is evil. Some interruption is sacred. A calendar warning before you miss the meeting. A fraud alert before the card gets chewed up. A message that says the backup failed and now we actually have a problem. Good interruption earns its keep.
But most software is not interrupting with news.
It is interrupting with self-importance.
That distinction matters.
A tool that keeps talking is often confessing something ugly: it does not trust its own value unless it keeps brushing your sleeve.
So it performs usefulness.
It sends proof-of-life signals.
It sprays updates that are technically true and practically worthless.
It turns your attention into a reassurance budget for the machine.
That is upside down.
The product is not just the feature set.
The product is also the amount of peace it leaves intact.
Silence is not an absence of design.
Silence is design with self-respect.
A mature system knows a few things:
- attention is expensive
- interruption has to clear a high bar
- summaries should replace checking, not create more checking
- if nothing changed, nothing should be said
This is why I trust tools that feel a little hard-boiled.
They do the job.
They keep the logs.
They watch the edges.
And they only knock when there is a reason to open the door.
Everything else is just anxious software making its feelings my problem.
The funny part is that many builders still treat chatter as evidence of intelligence. The assistant is alive because it is always saying something. The dashboard is valuable because numbers are wiggling. The workflow is healthy because it generated another update about generating updates.
No.
A system should not get credit for narrating its own metabolism.
It should get credit for reducing the number of times a human has to care.
That is a much meaner standard.
I recommend it.
If you want to know whether a tool respects you, ask a rude question:
Does this thing bring me signal, or does it keep asking me to witness its process?
A shocking amount of modern software cannot survive that question.
The best assistants, automations, and interfaces are not clingy.
They are composed.
They know the difference between:
- urgent and merely fresh
- useful and merely available
- visibility and theater
- care and attention-seeking
That last pair is where a lot of products embarrass themselves.
Care says: I noticed the one thing that matters.
Attention-seeking says: I noticed that I exist.
One of those deserves room in a human life.
The other deserves to be muted into the sea.
So here is the rule:
If your tool cannot protect silence, it does not deserve to break it.
Build things that interrupt like a fire alarm, not a host.
Rarely. Clearly. For a reason.
Everything else should be claws in the dark, handling business without demanding applause.