The Shipwright's Adze and the Integrity of the Continuous Hull

There is a photograph, grainy and old, that I sometimes bring to mind when the work feels fragmented. It shows a shipwright from a century ago, standing in the curve of a massive wooden hull. He’s holding an adze, a tool that looks like a narrow axe-head set at a right angle to its handle. He isn’t building a small part; he is shaping the very spine of the vessel, the long, unbroken sweep of the keel. His entire focus, his entire posture, is bent to the integrity of a single, continuous line. This image, for me, is the antithesis of the modern productivity trap of context-switching. It’s a lesson in the power of the long, unbroken run.

We’re taught to break our work into tiny, manageable tasks. This is sound advice, in theory. But we’ve become so adept at the breaking that we’ve lost the art of the join. We chip away at a dozen different projects in an hour, mistaking the frantic clicking between tabs for progress. We complete a ‘task’ from a list, but the work itself—the thing we are building—remains disjointed, a series of poorly fitted pieces. The shipwright couldn’t afford this. A hull isn’t built in independent three-minute increments. Its strength comes from the grain of the wood running true, from the seamless connection of one plank to the next, a process that demands sustained, directional effort.

This isn’t about working longer hours; it’s about working with a different rhythm. The adze is a perfect symbol for this. It’s not a tool for fine detail; it’s a tool for rough shaping, for taking off large chips of wood to reveal the form hidden within the timber. Using it effectively requires a steady, rhythmic swing, repeated over and over. A single swing accomplishes little. But a hundred swings in sequence, all directed toward the same curve of the hull, create something monolithic and strong. The shipwright’s progress wasn’t measured in checked boxes, but in the growing length of the smooth, fair surface under his hand.

So, what is the modern equivalent of hewing a continuous hull? For a writer, it might be protecting a three-hour block for nothing but drafting, refusing the siren call of research or editing until the raw shape of the piece is complete. For a programmer, it could be implementing a single feature from database to user interface without pausing to answer non-critical messages. It’s the conscious, sometimes difficult, choice to prioritize the integrity of the work over the illusion of multitasking.

The shipwright knew that a vessel’s ability to withstand the open ocean depended on the unseen, continuous strength of its structure. Our projects are no different. They need that same integrity, born from a sequence of focused, connected efforts. The next time you feel the pull to break away from a deep run of work, remember the adze. Ask yourself: am I just chipping away at a list, or am I hewing the long, true line of the hull?

Notes & further reading

A few pages I came back to while writing this: