May 14, 2011

The Author's Journey and the Blogger's Journey

Two different arcs of writing. The author pursues a single long work; the blogger iterates publicly. Different tempos, different rewards.

5 min read

There are two ways to write, and they produce two fundamentally different relationships to time.

The first is the author's journey. You have an idea for a book. You spend months or years developing it in private. You write drafts, revise, discard, rewrite. The work is invisible to the outside world until publication day, at which point it appears as a finished object. The audience encounters the end product. They never see the process.

The second is the blogger's journey. You have an idea. You write about it today. You publish it tonight. Tomorrow you have another idea, or a revision of the first one, or a tangent. The work is visible from the start. The audience watches the process in real time.

These are not just different workflows. They are different tempos.

The Long Arc

The author's tempo is glacial by modern standards. A year is fast for a book. Two years is normal. Five years is not unusual. During this time, the author is working inside a single sustained narrative structure. Every day's writing exists in relationship to the whole. Chapter three matters because of what chapter twelve will eventually say.

This creates a particular psychological experience. You are always carrying the entire work in your head, partially formed, evolving slowly. The mental load is enormous. You cannot think about the book the way you think about a blog post - as an isolated unit. Each piece depends on every other piece. Change one chapter and the implications ripple across the manuscript.

The reward structure is delayed and concentrated. Nothing happens publicly until the book is done. No applause, no comments, no shares. You work in silence and then, if everything goes well, you receive a burst of attention when the finished work reaches readers. The feedback loop is long. Very long.

The advantage is coherence. A book can develop an argument across three hundred pages with a level of depth and interconnection that no blog post can match. The long arc allows the author to build what might be called a thick narrative - rich in context, layered, self-reinforcing. The disadvantage is risk. You invest years in a single thesis that might be wrong, outdated, or simply uninteresting to the audience you finally reach.

The Short Loop

The blogger's tempo is fast. Daily or weekly publication. Each piece is relatively short. Each piece stands alone, or at least it can. The writing is public from the moment it appears, and feedback arrives within hours.

This creates a very different psychological experience. You are not carrying a monumental work in your head. You are carrying a queue of ideas, each of which is small enough to execute in a single sitting. The mental load per piece is light. The cumulative load, over months and years, can be substantial - but it distributes across many small containers rather than one large one.

The reward structure is frequent and distributed. Every post generates some feedback. Comments, shares, emails. The feedback loop is short. Sometimes uncomfortably short. You publish something half-formed and immediately discover its weaknesses through reader responses.

The advantage is iteration. Each post is an experiment. You learn what resonates, what confuses, what bores. You adjust constantly. Your thinking evolves in public, shaped by interaction with an audience that is simultaneously your reader and your editor. The disadvantage is fragmentation. A blog can accumulate hundreds of posts without ever building toward a unified argument. The pieces may individually shine, but they do not compose into a whole.

The Tempo Conflict

Most writers who work in both modes eventually feel the tension between them. The book demands long, uninterrupted stretches of attention. The blog demands short, frequent bursts. These are not just different schedules. They are different cognitive modes. Switching between them is expensive.

The author who blogs risks dissipating the energy that should go into the book. Every insight shared in a post is an insight not saved for the manuscript. Every hour spent responding to comments is an hour not spent revising chapter nine. The blog becomes a leak in the dam that was supposed to hold back all that creative pressure until the book was ready.

The blogger who writes a book risks losing momentum on the blog. The daily rhythm breaks. Readers drift away. The identity that was built on frequent public output erodes during the long silence of book writing. When the book finally appears, the audience that would have cared most has already moved on.

A Third Path

There might be a third approach that borrows from both tempos without fully committing to either. You blog, but each post is a module that contributes to a larger argument. You are writing a book in public, one piece at a time, without announcing it as such.

This is harder than it sounds. It requires holding the macro structure of a book-length argument in your head while producing micro-level content on a daily or weekly basis. You need the author's sense of coherence and the blogger's sense of pace. You need to satisfy readers who only see individual posts and readers who are following the developing whole.

I am not sure this third path works. I am trying it. This blog is, among other things, an experiment in whether a book-length argument about tempo can be assembled one post at a time, in public, without losing either the coherence of the long form or the vitality of the short form.

Ask me in a year whether it worked.

Related