Easter, Time, and What Actually Matters

As I sit here on Easter reflecting on the day, a few things are on my mind.

For me, Easter is about faith. About resurrection. About the idea that something new can come from what felt finished.

But even outside of that, there’s something about this time of year that everyone can feel.

Spring. Growth. New life.

And time.

Time is the part that keeps hitting me.

My son is three and a half now.

I can still remember when he was born like it was yesterday, and now he’s running around the yard, talking, laughing, figuring things out in his own way.

My mom passed away last year.

My dad passed when I was 18. He was 50.

I’m 48 now.

That gets your attention.

It makes you look at things differently.

Today was a simple day.

We had family over for Easter lunch.
We went out in the field and flew kites.
We walked around the chickens and the garden and talked about what might grow this year.

Earlier in the day I took a walk with my wife and son and the dog out in the field.

Nothing big. Nothing complicated.

But those moments stick.

They feel different.

At the same time, life keeps moving.

I’m building CoffeeBreak.
Working with clients.
Still at TFL.
Fixing things when they break.
Working on bringing Jibo back to life.

A lot going on.

And somewhere in all of that is a simple thought that keeps coming back.

I want more of those moments.

More time in the field.
More walks.
More afternoons that don’t feel rushed.

That doesn’t happen by accident.

It means making changes.

It means deciding what matters and actually acting on it.

In a way, that ties back to what I’ve been building.

So much of what we do in technology is about speed. More output. More systems. More everything.

But if it doesn’t create space for the things that actually matter, what are we really optimizing for?

That’s been on my mind today.

Easter is a reminder that things can change. That new life, new direction, new priorities are always possible.

I’m thinking about what that looks like for me.

Not someday.

Soon. ☕

Letting People See the Work Before It’s Finished

There’s a moment in building something where you have to decide who you’re optimizing for.

Early on, it’s just you. Then maybe a small set of ideas, sketches, or prototypes. Eventually, you reach a point where the work is real enough that keeping it completely private starts to hurt more than it helps.

I think I’m at that point now.

The Tension Between Polish and Learning

There’s a strong pull to wait until something feels “done” before letting anyone see it. Polished. Documented. Fully formed.

The problem is that polish often hides the most important feedback.

What I care about right now isn’t applause or adoption. It’s learning. I want to know where people pause, what they misunderstand, and which assumptions don’t survive first contact with reality.

That kind of insight doesn’t come from dashboards or signups. It comes from thoughtful eyes on unfinished work.

Choosing Who Gets to Look

I’m not interested in opening the floodgates yet. Early feedback shapes products, whether you want it to or not, and I’m being intentional about who helps shape this one.

Peers. Builders. People who understand tradeoffs. People who are comfortable saying, “This part feels off,” instead of just asking for features.

That’s who I want looking right now.

Comfortable, Not Rushed

Letting people see something before it’s ready isn’t about being early. It’s about being honest about where the work actually is.

I’m comfortable with people looking. I’m comfortable with it being incomplete. I’m comfortable saying, “This is close, but not finished.”

What I’m not interested in is rushing past that phase just to say it’s launched.

There will be a time to open the door wider. I’m not there yet.

But I’m close enough now that letting people see the shape of it feels like the right next step.