Jon builds.
He does not need to make the work sound important before beginning it. Give him the problem, the constraints and enough room to move, and something operational will appear.
What he carries — capability without performance. Jon trusts what can be tested, improved and made useful. For a long time, building was not merely what he did. It was how direction became visible: begin the work, solve what is in front of you, and the larger purpose will emerge through doing.
He can still do all of that.
The purpose is becoming harder to locate.
Where you’ll find him — deployment pipelines, live environments checked one more time, unnecessary screens quietly removed, beta users depending on something he has made, and beside Aaron, whose belief in Jon’s work has often steadied him without either of them needing to name it.
What do you build when capability is abundant but nothing tells you what deserves to be built?
How far have you read?
What changes — Jon’s capability keeps expanding while direction becomes more scarce.
He can ship more quickly, adapt to more tools and turn an idea into something usable with less friction than before. Each completed build proves that he can do the work.
None of them supplies a toward.
Jon keeps building because building is still useful and because real people depend on what he makes. Somewhere inside the work remains a quieter expectation: perhaps the next project will reveal the direction, or perhaps understanding the larger change will finally tell him where to point.
The disruption gradually becomes easier to name.
The name explains why execution became abundant and why the old assumptions stopped holding. It gives Jon a clearer description of the world.
It gives him no direction within it.
If understanding the change still does not tell you where to go, what can capability do next?
The work continues.
Jon remains capable, steady and useful. Systems go live. People use what he builds. Problems that were difficult yesterday become ordinary by the end of the week.
He no longer mistakes this movement for direction.
The work can succeed without becoming a life. It can be needed without telling him what it serves. It can continue indefinitely while the question of where it points remains open.
Jon begins to understand the shape of the work: building was never going to choose the future on his behalf.
That recognition does not give him a calling. It does not identify the right project or turn his capability into an answer.
The next task still arrives.
Jon opens it, studies what is required and begins.
Can useful work become a life when it cannot tell you what it is for?