There is a particular kind of clarity that only shows up when you are building under constraint. A sleeping child in the next room. A calendar that no longer belongs entirely to you. A body that is asking for rest while the backlog keeps asking for one more thing.

Constraint is not the enemy of craft

Before becoming a dad, I treated constraints like obstacles: time, energy, attention, budget, focus. Now I see them more like a product spec. They force the shape of the thing. They tell you what the system can actually carry.

The best product decisions are often deletions

Fatherhood makes scope painfully concrete. If a feature needs three late nights to explain itself, maybe it is not ready. If a change cannot survive a clean git revert, it is not really done — it is hope.

You do not find time for the things that matter. You architect for them.

Feedback gets louder when it is personal

A product user might churn quietly. A toddler does not. Family life has a way of making weak systems visible immediately: bad routines, unclear handoffs, missing recovery time, decisions that depend on everyone having infinite patience.

Three things I check before shipping anything now:

Can it survive a tired, distracted operator?
Does it fail loudly, or does it fail quiet and mean?
Would I trust it at 3am with no one else awake to help?

Notes to self

Build the smallest useful thing, then listen.
Protect the people the system is supposed to serve.
Do not confuse complexity with care.

typescript
function shipUnderConstraint(scope: Scope): Scope {
  // Constraint isn't the enemy — it's the spec.
  return scope.essentialOnly()
}

If you want the fuller version of this argument, I wrote more about the overlap in the about section.

Built by Dad is my place to keep those lessons close: product notes, systems notes, and the reminders I need when ambition gets loud and the nursery gets quiet.