How are you? Almost good
Why I answer a simple question with a qualified word, and why almost everything I believe sits in a range
People ask how I am, and I usually say “almost good”.
It confuses some of them. A few stop and ask which part is missing, which is the best possible outcome and the reason I keep saying it.
The ritual answer is “good”, or “fine”, and both of us know it carries no information. It is a handshake made of words. I understand why it exists and I am not against politeness.
But I have never been able to say it comfortably, because it is almost never true, and the alternative of answering honestly in full is worse. Nobody asking in a corridor wants a status report.
“Almost good” sits between the two. It is true nearly all the time, it is short, and it leaves a door open without pushing anyone through it.
Everything I know is a range
The older I get, the fewer definite things I find.
Is the code good? It is good for the next six months, for this team, at this load. Is the design right? It is right until the requirement it was built around changes. Am I healthy? Compared to last year, mostly, apart from the thing I keep not booking an appointment for.
Every measurement I have ever taken had error bars, and every answer I have ever given about a system had conditions attached that I left out because the person asking wanted a yes or a no.
Mathematics has a lovely phrase for this, “almost everywhere”, meaning a property holds except on a set small enough not to matter. That is roughly how I feel on a normal day. Almost everything is fine, except on a set of exceptions whose measure is not quite zero.
So when I answer with a range rather than a point, I am not being evasive. I am being accurate at the resolution the question deserves.
It leaves room to be better
There is a second reason, and it is less tidy.
“Good” is a finished state. If I am good, there is nothing to work on, and I know with certainty that there is plenty to work on.
I am trying to be a better person in the ordinary ways: more patient with people who are slow to the point, less proud about being right, better at calling my family. None of that is complete. Saying “good” would be filing the matter closed, and the matter is not closed.
“Almost” admits direction. It says I am somewhere on the way, and that the distance remaining is known to me, which I find a more comfortable position than pretending to have arrived.
Not as self-criticism. As an honest description of a person in progress, which is all any of us ever are.
Definite answers are mostly a performance
Watch how certainty is actually used.
The confident estimate in the planning meeting. The architecture declared correct before the first user arrives. The strong opinion about a technology someone has used for a week. The interview answer delivered without caveats because caveats sound weak.
Most definite statements I hear are not conclusions. They are performances of confidence, because confidence is what gets rewarded.
The people I trust most are the ones who say “probably”, “in this case”, “I think so but I would check”. They are not less competent. They have simply looked closely enough to see the edges, and they are honest enough not to paint over them.
I would rather be in that group, and the greeting is a small daily practice of it.
It travels into the work
This habit shows up everywhere in what I build.
It is why I write “probably” in documentation instead of promising behaviour I have not verified. It is why the roadmap on my own projects says what I am working on rather than what I am committing to. It is why the label on the posts here about things I make says [Almost Ad], because that is exactly what they are: not a neutral essay, not quite an advertisement, somewhere in between and better marked than pretended away.
Precision about uncertainty is a form of respect for whoever is reading.
And the honest caveat
There is a failure mode, and I should name it before someone else does.
“Almost” can be a hedge. It can be a way of never committing to anything, of keeping an exit from every statement, of sounding thoughtful while saying nothing. I have met people who qualify everything into mush, and I have been that person in meetings where I did not want to be wrong in public.
The distinction I try to hold: qualify the claim, not the commitment. “Almost good” is a description of my state. It is not a reason to miss a deadline or to leave someone wondering where they stand with me.
Be exact about how uncertain you are. Then act anyway.
So, how am I?
Almost good. Ask me which part, if you have a minute.