The useful distance between idea and tool

Every tool edits the idea passing through it. Some changes are productive: a constraint clarifies the work, or a new capability reveals a direction that was previously invisible.

Other changes happen because the tool is convenient and the idea is still weak.

Do not close the gap too quickly

There is value in keeping an idea slightly separate from its first implementation. That distance makes it possible to ask whether the current tool is shaping the work or merely narrowing it.

Prototypes are useful here because they make assumptions visible without demanding loyalty.

Build, borrow, or wait

Build when the missing capability is central to the work. Borrow when the problem is ordinary and the borrowed part will remain replaceable. Wait when neither path makes the idea clearer.

The right tool shortens the distance without deciding the destination.