Build With Limits

I used to wait until things were ready.

Ready meant polished. Ready meant I had all the answers. Ready meant I couldn't be wrong in front of anyone.

The problem is that ready never comes. Not when you're pregnant, running a full-time job, and trying to build something that matters. Not when you have seventeen tabs open and a to-do list that grows faster than it shrinks.

So I stopped waiting.

What building in public actually means

It doesn't mean live-streaming your failures or performing vulnerability for engagement. It means this:

I ship before I'm comfortable. And I tell you about it.

It means the first version of this site wasn't perfect. The copy wasn't perfect. The products weren't perfect. I shipped it anyway, because a real thing in the world — even a flawed one — is worth more than a perfect thing in my head.

Why constraints are actually the point

Here's what I've learned: constraints don't stop the build. They shape it.

When you have two hours instead of eight, you make different decisions. Better ones, sometimes. You cut what doesn't matter. You ship the thing that does.

I'm building with:

A full-time engineering job
A baby on the way
A business idea I believe in
Not enough hours in the day

And I'm shipping anyway.

What you'll find here

This build log is where I share the real version. Not the cleaned-up LinkedIn post. The actual decisions, the actual numbers, the actual wrong turns.

If you're building something — a business, a body, a system — with the same kind of real-life constraints, this is for you.

Start where you are. Build anyway.

— Amanda