The Slowest Thing I Ever Built

Illustration created using Google Gemini

What a Life in Technology and the Practice of Writing Taught Me About Time, Progress, and Control

The slowest thing I ever built began before I knew I was building anything.

Its origins lay in conversations I had in 2014 with a family friend everyone called Uncle John. A professor of neurochemistry, he impressed me less by what he knew than by how he listened. He did not prepare a response while another person was speaking or hurry a pause toward a conclusion. In his presence, I felt my own attention stop leaning ahead.

I began making notes, not because I intended to write a book, but because I wanted to remain close to something I could not yet explain. Those notes and thoughts accumulated for years, gradually becoming the inquiry that would take shape as When Attention Settles.

For most of my adult life, I had lived in two worlds: a career in technology and a quieter practice of writing that I kept alive through notes, reflections, and questions I could not easily leave behind.

My professional life—from building wargaming software at a DRDO laboratory and then working at Bell Labs to entrepreneurship and technology leadership—had trained me to build, test, measure, and revise. Writing taught me that some forms of progress remain invisible, and that waiting can be either part of the work or a way of avoiding it. The difference is not always easy to recognize.

Only when writing began to claim more of my attention did I understand how differently these two worlds treated time, progress, and control.

The Two Clocks

My career in technology had trained me to remain slightly ahead of the present.

There was always another development to anticipate, another market shift to interpret, or another decision to make before uncertainty had cleared. In software and entrepreneurship, delay had consequences.

The rhythm was familiar: build, test, observe, adjust, and begin again. Even failure produced information. A system that did not work still exposed the assumptions behind it.

Technology makes progress visible. A system functions or fails. A process becomes faster, more reliable, or more efficient. A product enters the market, users respond through their behaviour, and the results appear in metrics and dashboards.

These signals are imperfect. Data can be misread, and what is easiest to measure is not necessarily what matters most. But the signals exist. They allow assumptions to be challenged and decisions to be revised.

I trusted this rhythm because the work answered back.

Writing kept a different clock.

The question that grew out of my conversations with Uncle John did not begin as a problem to solve or a project to complete. It came to mind, faded, and returned. I made notes, left them alone, and encountered them again months or years later. New experiences sometimes changed what I thought the original question had been.

At times, the work advanced because I wrote. At others, it advanced because life gave me something I had not previously known to notice.

Writing offered no comparable dashboard.

There was no way to tell whether an observation had truly deepened or had simply become familiar through repetition. Nothing showed that two notes written years apart were part of the same question. No sign appeared when a partial understanding had grown into something clearer.

This kind of progress was difficult for me to trust. My professional experience had taught me to see constant activity as a sign of serious work. When progress slowed, my instinct was to organize more, work harder, and push forward.

That instinct had often served me well in technology. In writing, it sometimes produced language before understanding.

A sentence could be clear, efficient, and still wrong—not factually wrong, but wrong because it claimed more than I knew. A paragraph could arrive at a conclusion the thought had not yet earned.

Time was not always an obstacle to creation. Sometimes it was one of its materials.

But slowness on its own is not wisdom.

An unfinished idea can be protected indefinitely by the claim that it needs more time. Patience can become avoidance, and reflection can postpone the decisions required to finish something.

The discipline is to recognize what the work requires at a particular moment.

Some ideas need to be tested through action. Others need to remain unresolved long enough for their meaning to develop. The difficulty is knowing which kind of work is before us.

For years, my notes remained scattered. Some returned to the quality of attention I had experienced with Uncle John. Others concerned listening, effort, control, and the strain of continually leaning toward what might happen next. I did not yet know that they belonged together.

The change came gradually. Questions began recurring beneath subjects that had initially seemed unrelated. The notes no longer merely preserved separate observations. They were beginning to reveal a pattern.

That was the first evidence I trusted.

It did not mean that a book had appeared fully formed. It meant that the fragments had acquired enough coherence to demand a form. Continuing to observe was no longer sufficient. The work had to be arranged, tested, revised, and eventually completed.

Until then, my responsibility had been to remain close to the question without forcing it toward a premature conclusion. Now I had to decide what belonged, what did not, where the inquiry began, and what the writing could honestly claim.

The shift was not from uncertainty to certainty, but from waiting to responsibility.

That experience changed how I understood progress beyond writing. Much of life offers no such dashboard. Relationships, grief, attention, judgment, and self-understanding often develop without measurable signs. We may be changing before we can describe the change.

My career in technology had taught me to respect evidence. Writing showed me that the absence of visible evidence did not necessarily mean that nothing was happening.

It also taught me not to use invisibility as an excuse. The work begins when uncertainty is no longer a reason not to build.

Revision and Release

My career in tech taught me to distrust the first version of a system.

Systems are tested, faults identified, and assumptions revised. Products fail when their creators remain attached to assumptions that reality has contradicted.

Writing depends on the same willingness to let the work contradict its author’s assumptions, although the evidence is less explicit.

A sentence can be grammatically correct and still feel false. A paragraph can be elegant while carrying the thought away from what it is trying to understand. Once my notes began taking form, revision became more than a way of just improving the prose. It became a way of testing whether the thought could survive the form I had given it.

The draft exposed where I was forcing order onto something I had not fully understood. It revealed where polished language concealed uncertainty and where an idea was too simple, too certain, or wrong. Revision did not merely change the writing. It changed my understanding.

Revision is more than a method of improving what we have made. It is a willingness to be changed by what the work reveals.

Both worlds require this surrender. The technologist must release an original design when the evidence no longer supports it. The writer must release a sentence, structure, or conclusion when the work has moved beyond it. Attachment can become the enemy of the work.

A second surrender begins when the work is released.

A technological product enters use. People adopt it, resist it, abandon it, or employ it in ways its creators did not anticipate. A book enters interpretation. Readers bring circumstances, memories, and questions the writer cannot know.

I could shape the language of When Attention Settles, but I could not determine how it will impact the readers. There is no reliable way to know what a book will become in the mind of another person. Readers found meanings and connections I had not intended, reminding me that a book continues beyond its author—not because its words themselves change, but because each reader encounters them through the lens of a different life..

Creation requires control. Completion requires the willingness to give some of it up.

What the Two Worlds Gave Each Other

The longer I moved between a career in tech and a practice of writing, the less useful it became to think of them as opposites.

Each gave me something the other lacked.

My career in tech gave my writing discipline, structure, respect for revision, and the resolve to finish. Writing taught me to live with uncertainty longer than my professional instincts preferred. It taught me patience and attention and reminded me that activity is not always progress.

Neither rhythm is enough on its own. Action without reflection can produce great speed in the wrong direction. Reflection without action can protect an idea from ever being tested, completed, or shared.

The harder task is not choosing one rhythm over the other but knowing what the moment requires: when to build, when to wait, when to revise, and when to release.

There is no dashboard for that judgment.

The slowest thing I ever built taught me that creation requires both: the patience to let understanding develop and the discipline to act before certainty arrives.