Craft as Proof
The work is the argument1. Not the description of the work, not the rationale offered alongside it — the thing itself, in the state it was left. A site that reads well is a claim about attention. A system that holds under pressure is a claim about judgment. You cannot separate the evidence from the conclusion.
This is why the portfolio format tends to fail. It asks the maker to stand outside the work and explain it, which is precisely the wrong direction. Explanation is a hedge. It suggests the work might not be legible on its own terms, so here is a guide. But if the work requires a guide, the work is not finished.
What I am interested in is the kind of craft that makes explanation unnecessary — not because the work is simple, but because it is clear. Clarity is not the same as simplicity. It is the result of having made enough decisions, in the right order, that the remaining complexity resolves itself.
Footnotes
-
This is not a claim against documentation or context — both have their place. It is a claim about what constitutes evidence. A well-written README is itself a demonstration of craft. ↩
This was made by LinCie. Reach out if it speaks to you.