There is something that happens when you make something from nothing — a proof, a function, a piece of furniture, a song — that no amount of consuming can replicate. It is not productivity. It is participation.
We live inside an attention economy engineered for consumption. Every platform, every feed, every recommendation engine is optimized to keep you receiving — content, stimulation, outrage, entertainment, information. Consumption is passive, frictionless, and endless. It is also, in some hard-to-articulate way, deeply unsatisfying in the long run. The thing that satisfies, that leaves a residue of meaning, is almost always on the other side: making.
What Making Actually Does to You
The psychological literature on creativity and wellbeing points consistently in one direction: people who make things — regardless of quality, regardless of audience, regardless of medium — report higher levels of meaning, engagement, and life satisfaction than those who do not. This holds for professional artists and weekend woodworkers alike. The act of making is not primarily about the artifact. It is about what happens to the maker.
“The object isn't to make art, it's to be in that wonderful state which makes art inevitable.”
— Robert Henri
The Craftsman's Relationship with Time
One of the stranger properties of deep making is what it does to time. When you are genuinely absorbed in a difficult problem — a tricky refactor, a complex proof, a passage that will not resolve — time behaves differently. Hours compress. The background noise of the day quiets. This state, which Csikszentmihalyi called 'flow,' is not accidental. It is the natural consequence of voluntary engagement with a task that sits precisely at the edge of your current ability. Making, at its best, requires that you operate there permanently.
The Productive Discomfort of Difficulty
The parts of a project that are hardest are also, retrospectively, the parts that were most formative. The bug that took four days to find. The chapter that required seven drafts. The joint that had to be cut three times before it fit. Difficulty is not evidence that something has gone wrong — it is usually evidence that something interesting is happening, that you are at the edge of your competence, which is exactly where growth occurs.
Making Without an Audience
Something has gone sideways in the culture of making since the rise of public platforms. There is an implicit expectation that output should be shared, validated, and optimized for reception. Side projects become launch announcements. Learning becomes content. The private sketchbook becomes the public feed. This is not uniformly bad — sharing knowledge and work has enormous value. But the conflation of making with publishing corrupts the act at its root by introducing an audience into the studio before the work is even begun.
- Make things that will never be published. The discipline of making for its own sake is foundational.
- Protect early work from critique — including your own. Judgment and creation use different cognitive modes and interfere with each other.
- Separate the making phase from the sharing phase. They are different activities with different goals.
- The audience changes what you make, sometimes in ways that reduce its honesty and increase its performance.
- The most important creative work you will ever do may be the work nobody ever sees.
Craftsmanship as a Philosophy
The craftsman's ethic holds that the standard of work is the work itself — not the reception, not the market, not the algorithm. A cabinetmaker who cuts a dovetail joint that will be hidden inside a drawer is not being inefficient. They are practicing a relationship with quality that cannot be maintained selectively. Either you care about the work or you do not. Half-care produces half-work, and the maker knows the difference even when the audience cannot tell.
Software as Craft
Code is one of the stranger making mediums in history: it is purely abstract, infinitely malleable, and yet bound by hard constraints — it either works or it does not. There is genuine craft in writing code that is not merely functional but clear, extensible, and considerate of whoever reads it next. The craftsman programmer names things well, structures abstractions at the right level, and leaves the codebase better than they found it — not because a style guide demands it, but because that is what it means to take the work seriously.
The Larger Argument
In an era of increasing automation, AI-generated content, and algorithmic optimization, the deliberate choice to make something by hand — to think a thought through to its end, to build something that reflects your specific judgment, to struggle with a problem until it resolves — is becoming a more countercultural act, not less. It is also, I suspect, becoming more important. Not because handmade things are inherently better, but because the practice of making is one of the primary ways humans have always constructed meaning.
“We are what we repeatedly do. Excellence, then, is not an act but a habit.”
— Aristotle
Start the project. Ship the imperfect thing. Build the thing that has no audience. Learn the craft that has no obvious career application. Make something — not because the world needs another artifact, but because making something is one of the most honest conversations you can have with yourself about what you value, what you can do, and who you are becoming.