Fall 2026: The Handoff

The first part of this decade was largely construction.

Not construction in the clean, linear sense. There was a lot of starting, stopping, changing direction, learning something, realizing I had misunderstood the thing I was learning, building a system, outgrowing it, and building another one.

Some of it was practical. Learning to code. Learning design. Building websites. Figuring out how I work. Creating systems for tasks, notes, projects, money, ideas. Trying different kinds of work.

Some of it was harder to name.

I was trying to build a life that could actually hold me.

For a long time, the different parts didn’t fit together particularly well. The things I was good at didn’t necessarily make me money. The things that made me money didn’t necessarily use much of me. Creativity lived over here. Work lived over there. Curiosity had its own room. The future was always under renovation.

So I got very good at construction.

I got good at examining things. Pulling them apart. Asking whether they still belonged. Starting again when the answer was no.

That was useful.

It was also expensive.

At some point, rebuilding can become so familiar that you don’t notice you’re still doing it. Every new season becomes another opportunity to reconsider the entire architecture. Every change in environment becomes a reason to ask who you are now. Progress happens, but some of it happens sideways because you’re continually reconstructing the thing that is supposed to carry the progress forward.

Lately I’ve been wondering about the opposite.

What happens if things are allowed to stay built?

Not forever. Not because they’re perfect.

Just long enough to acquire a past.

A website gets another page instead of another redesign.

A skill gets another year of use.

A project becomes evidence for the next project.

Work creates relationships that create other work.

Something I wrote two years ago remains available to someone discovering me today.

A decision keeps producing consequences after I’ve stopped thinking about it.

One year gets to inherit something from the year before it.

That’s accumulation.

And I don’t think I’ve experienced enough of it yet to know what it does.

There’s a strange difference between progress and accumulation. Progress can happen inside a single moment: you learn something, finish something, make a better decision.

Accumulation requires time.

It requires not returning everything to zero.

The interesting question for the rest of this decade isn’t whether I can construct another version of myself. I have plenty of evidence that I can.

I’m more curious about what this one does with continuity.

What happens when skills stay skills long enough to become command?

What happens when projects stop being isolated events and start becoming a body of work?

What happens when relationships have enough time to develop history?

What happens when the systems underneath my life become boring enough that I can stop thinking about them and use them to make things in the world?

What happens when today’s output becomes tomorrow’s input?

I don’t know.

That’s the handoff.

The first part of the decade was spent building a lot of the machinery. The remaining years feel less like another construction project and more like an experiment.

Keep making things.

Let them stay made.

Let people encounter them.

Let consequences travel farther than the original action.

Add another layer.

See what compounds.

There will still be changes. Some things will break. Some things should be abandoned. Continuity isn’t stubbornness, and accumulation isn’t keeping everything.

It’s simply a different default.

Maybe the next version doesn’t need to begin with demolition.

I don’t really know what accumulation looks like yet. That’s part of the experiment.

I know reconstruction.

I’m very good at starting over.

I’m more interested now in what happens if I don’t.