The Scribe's Spoil and the Grace of the Struck Line
We talk a lot about flow states and deep work, about building systems that carry us forward with frictionless momentum. The goal, we are told, is to build a leak-proof pipeline from intention to execution, where ideas flow unimpeded onto the page or into the code. This is the received wisdom: to eliminate hesitation, to silence the inner critic, to just produce. But I’ve begun to suspect that this relentless focus on forward motion ignores a crucial, vital component of true craft: the spoiled line.
Consider the medieval scribe, bent over a vellum page, a pot of expensive ink at his side. His work was unforgiving; a single mistake could ruin days of labor. We imagine him as a paragon of meticulousness, which he was. But what did he do when he made an error? He didn’t have a delete key. He couldn’t command-Z his way back to innocence. His only option was to strike through the mistake—to draw a line through the errant word or phrase, acknowledge the fault, and continue writing. This marked passage, this blemish, is the spoil.
Our modern tools, for all their power, have taught us to be ashamed of the spoil. We edit in invisible mode. We crave the pristine final draft, as if it sprang fully formed from our foreheads. The messy, iterative, human process of creation is erased from the record. We are left with only the perfect result, which in its perfection, can feel sterile and, oddly, inhuman. More dangerously, this erasure makes us fear the act of writing itself. The pressure to be perfect from the first keystroke is a cognitive poison. It leads to the blinking cursor, the paralyzed hand, the page that remains空白because we are terrified of making a mark that isn't correct.
I propose a different practice, a different metric for a productive session. It’s not about the number of pristine words you keep. It’s about the number of honest lines you are willing to strike through. The spoil is not a sign of failure; it is the archeological record of your thinking. It shows you where you diverged, reconsidered, and chose a new path. It is the mark of a mind engaged in a real-time conversation with itself.
So, try this. For your next piece of work, turn on the feature that shows your edits. Write a sentence you know is clumsy. See it there, in all its ungainly glory. Then, strike it. Don’t delete it—select it and apply a strikethrough. Write the better version beneath it. The page will look messier, but your mind will feel clearer. You are not hiding your process from yourself. You are granting yourself the grace of the scribe: the permission to be wrong, to correct, and to continue, with the evidence of your journey preserved right there on the page. This isn’t deliberate inefficiency; it is profound efficacy. It is the practice of getting real work done by honoring the crooked, human path that real work always takes.
Notes & further reading
A few pages I came back to while writing this: