I Think I'll Build in Private

Lately, I’ve been thinking about building.

Not just projects, but skills.
Habits.
Resilience.
Ways of working.

And I keep circling back to the same quiet idea:

I think I'll build in private instead.

---

The Current Drift

There’s a strong pull right now toward:

Building in public
Shipping MVPs
Narrating the process as it unfolds

I understand why. There’s energy there. Momentum. Visibility.

But I’m noticing something in myself as I learn new things and experiment with different workflows and tools.

I think early-stage work doesn’t want an audience.

It wants space.
And privacy.

---

Personal Skills Are Also “Builds”

When I’m developing a new skill or habit, it behaves a lot like a project in its first weeks.

It’s:

Awkward
Inefficient
Full of false starts

If I talk about it too early, something subtle happens.

The work shifts from doing to explaining.

From learning to narrating.

From experimenting to defending.

None of that helps at the beginning.

---

Private First, Stable Later

I’m finding value in keeping things quiet while they’re still forming.

That applies to:

New ways of working
New tools
New rhythms
New projects

Not because they’re secret.

But because they’re unfinished.

Privacy lets me:

Change direction without friction
Abandon experiments without cleanup
Let ideas harden before they’re named

It’s easier to build something solid when it’s behind closed doors.

---

Not MVPs, But Craft

I’ve also been questioning the reflex toward MVPs.

MVP = Minimum Viable Product

Minimum works when speed is the constraint.

But sometimes the constraint is coherence.

Sometimes I don’t want the smallest possible version.
I want a version that feels complete enough to stand on its own.

For me, that takes time.
And privacy.

---

An Observation, Not Advice.

I’m not telling anyone what to do here.

I’m just reporting what I’m noticing in my own process right now.

When I build in private, I've found I:

learn faster
stay calmer
make fewer identity-level commitments
let results speak before stories form

Eventually, some things will be shared.
Others won’t.

But the work feels better this way.

---

A Working Thought

Build quietly.
Let things stabilize.
Show the work when it can walk on its own.

For now, that’s the direction I’m leaning.

No announcement.
No MVP.
Just building.

---

Aaron Rose is a software engineer and technology writer at tech-reader.blog and aaronrose.blog.