A workbench is an argument
Every workshop encodes a theory of how work should go. Most people never notice they are living inside someone else's.
Updated 2 min read 1,420 views
A workbench is not neutral furniture. It is a set of claims about how work should proceed, made physical, and then quietly obeyed for years.
The claims a bench makes
Height is a claim about whether you will mostly stand or mostly sit. Depth is a claim about how many things you are expected to have in progress at once. The presence or absence of a vice decides whether the bench is for assembly or for shaping.
None of these are announced. You inherit a bench, or buy the one that fits the space, and then spend a decade adapting your practice to its argument without ever hearing the argument stated.
Reading a bench
The next time you are in someone else's workshop, look at three things:
- What is within arm's reach. Those are the tools the work actually uses, regardless of what the person says the work is.
- Where the clear space is. Every bench has one patch that stays clear. That patch is the real work surface; everything else is storage pretending otherwise.
- What has been modified. A drilled hole, a clamped-on jig, a strip of tape marking a measurement. Modifications are where the bench's argument lost to reality.
The same is true of a repository
Everything above holds for a codebase. The directory structure is a claim about what varies together. The test setup is a claim about what is worth being confident in. The presence of a scripts/ folder full of undocumented shell files is a claim that somebody kept losing an argument about tooling.
The difference is that a bench is honest. It sits in the room, obviously physical, obviously chosen. A repository's arguments hide behind the appearance of necessity, and are much harder to notice you are obeying.
Rearranging on purpose
The useful move, in both cases, is the same: once a year, take everything off, and put back only what earns its place.
The things you hesitate over are the interesting ones. Hesitation means the tool is used rarely enough to question but often enough to miss. That is exactly the set worth thinking about deliberately, rather than by default.
Written by
Mira Solheim
Contributing writer
Writes the field notes column on tools, workshops and working with your hands.
New writing, now and then
One email when something new is published. No noise, no tracking pixels, unsubscribe in one click.
2 comments
Sign in to join the conversation.
This landed at the right time. The bit about protecting the first hour rather than the longest one is the part I keep getting wrong.
Thanks — that framing came from watching how badly a fragmented morning wrecks an otherwise clear afternoon.