The Scribe's Broad-Nib and the Programmer's Compass: Two Maps for the Same Terrain

Lately, I’ve been caught between two different ways of navigating a project. One, borrowed from a friend who is a serious calligrapher, involves a broad-nib pen and a sheet of grid paper. The other, gleaned from a software architect I admire, involves a tool he calls his "compass"—a single, evolving text file. Both are methods for plotting a course before you set foot on it, yet they feel like maps drawn in different centuries, for different explorers.

The scribe’s approach is tactile and spatial. You start with the broad nib, which cannot be rushed. Its wide edge forces a slow, deliberate pace and a physical awareness of the page’s geography. You don’t outline an essay here; you block it out. A fat stroke for a core thesis. A series of shorter, parallel strokes for supporting arguments, stacked like stones. Dotted lines connect related thoughts across the grid. The map is messy, ink-blotted, and entirely of the hand. Its value isn’t in its final legibility, but in the muscular memory of the journey. By the time you pick up your normal pen or open your text editor, the terrain feels familiar. You’ve already walked its contours with your wrist.

The programmer’s compass, by contrast, is pure hierarchy and logic, living in plain text. It’s a single file where he begins every project, be it code, an article, or a garden plan. At the top is the True North—the one-sentence purpose. Below that, indented with simple bullets or dashes, are the immutable landmarks: the non-negotiable requirements, the hard constraints. Further indentations become avenues of approach: possible tools, potential phases, known risks. The file is fluid; lines are commented out, moved, demoted from landmark to avenue as understanding deepens. The compass doesn’t care about the feel of the work, only its structure. It is a schematic of relationships, a proof of concept written in human language.

Put side by side, they reveal a fundamental fork in the road of preparation. The broad-nib map is about embodiment. It’s a rehearsal that engages the senses to quiet the mind, trusting that clarity of form follows clarity of motion. The digital compass is about abstraction. It’s a logical scaffold built to bear weight, trusting that a sound architecture will produce a sound construction. One believes the best path is felt in the bones; the other believes it is deduced by the mind.

I find myself needing both, but at different times. When a task feels nebulous and intimidating, full of unseen dragons, I need the broad nib. Its physical ritual makes the vague concrete, giving my anxiety a shape to grip. When a project is complex and interlocking, a puzzle of dependencies, I need the compass. Its cold logic shows me the load-bearing walls before I start hanging pictures. The trick, I suppose, is knowing which territory you’re actually in. Is this a wilderness that needs to be felt? Or is it a city that needs to be blueprinted? Your tools, and your trust, must follow that diagnosis.

Notes & further reading

A few pages I came back to while writing this: