When I was a full-time professional violinist, I spent a lot of time seeking out all the self-help material I could find concerning deliberate practice and technical efficiency. I've found that the same mindset has been essential for my development as a writer. Writing, like playing the violin, is a technique. And although there may be some irreducible element of inspiration and talent in both, there are ways of approaching these activities that can make them manageable and even pleasurable. The purpose of this series of posts is to gather some ideas, both theoretical and practical, about how such processes can work for the writer of long documents such as books and dissertations.
1. Why is writing hard?
The first step to doing anything difficult is to acknowledge that it's difficult, and to understand that it's ok to experience challenges. The second step is to try to figure out why it is difficult, the better to solve the problems facing you. There are many reasons why writing is difficult--some practical, some technical, some aesthetic--but for now I'll focus on a theoretical difficulty particularly pressing when writing long texts. (My framing of this idea is based on Popper's arguments concerning empiricism, theory, and observation.)
Thoughts can take any number of shapes, and they can connect to other thoughts in any number of ways. To write thoughts down is to translate a set of largely amorphous ideas into fixed, linear form, with specific words, sentence structures, and a set order. This process is an act of interpretation: one that (like all interpretations) is carried out with an overarching theory about how and why the writing should take the shape it does. In other words, when we try to capture ideas on the page, we do not only contend with the ideas themselves; we also adopt some sort of theory about what 'the book' or 'the dissertation' will end up being--and it is this theory that allows us to know how to even begin tackling the ideas in the first place. Every sentence in a document is written with a theory about what the document is. But the difficulty is that with each sentence written, the document becomes better-fleshed-out, diverges in all its messiness from the idealized theory, and, even more important, changes the nature of the theory we might hold about the project as a whole. That is to say, every sentence is both written under a theory of 'the document' and alters the theory of 'the document' that operates in the writing of future sentences. By the time one reaches the end of (say) a 90,000-word draft, one has essentially produced a document in which most of the component parts--the paragraphs, the sentences--are part of about 90,000 different conceptual books or dissertations.
Actually, perhaps this is a simplification. The speed with which theories of 'the document' change will itself be subject to change as the draft unfolds. In my experience, the first 5-10% of the document is written under a highly consistent theory governed by an outline (assuming one is using an outline!); then change accelerates as development occurs, and each sentence/paragraph exerts a bigger pull on the overall theory; and finally, after about 80% of the draft is written, the theory of the document once again becomes more stable. Of course, it's highly unlikely that the stable theory one arrives at for the final 20% of the draft is similar to the stable theory one held while working on the first 5-10%.
So, even in this weaker statement of the problem, the basic point remains that you will probably produce a first draft in which about 80% of the sentences belong to thousands of different conceptual books, none of which is actually aligned with the finished draft, which is necessarily a jumbled mess.
2. What to do about it
This way of framing the challenge of writing may seem needlessly theoretical, but a number of practical points follow directly from it. Here are some extrapolations:
1. First drafts are necessarily awful. Many writing self-help guides (including most famously Anne Lamott's Bird by Bird) acknowledge the awfulness of first drafts. But these guides tend to do so ruefully. We are told that coming to terms with the awfulness of first drafts is a kind of self-acceptance--as though we simply need to acknowledge that we aren't smart enough to write perfect first drafts. I think that this way of framing misses the point. The problem of first drafts, as I see it, isn't that "we're not smart enough to get things right the first time"; the problem is that first drafts are necessarily awful because they are written under a huge variety of mutually-contradictory theories of what 'the document' will end up looking like. In other words, the awfulness of first drafts is inherent, and there is absolutely nothing we can do to escape it. It follows that this awfulness is something to embrace and make friends with.
2. From (1) it follows, in turn, that it's best to write an entire first draft before starting to revise or edit. People take many different approaches to this practical question; and even for me, a hardened embracer of bad-first-drafts, there is always a temptation to try to revise during the initial drafting process, for no better reason than the sheer frustration one feels at producing a 200+ pages of terrible, cluttered, aimless, unpolished prose.
However, there are a few reasons not to give in to the temptation to edit. The first two reasons are practical, and have nothing to do with the philosophical framework I'm outlining. First, the more one writes, the more momentum one gathers. It's often easier to push through the pain to the end of a document when one writes in a single sweep of productivity. Second, the mindset needed to produce words on the page is very different from the mindset needed to revise what's already there. The biggest difference between the two mindsets is that the first requires a real lack of inhibition and a confidence and belief in one's powers of creativity, whereas the second requires coolheaded discernment, self-criticism, ruthless questioning of one's ideas, etc. It's rarely easy to switch back and forth between the two mindsets, so it makes sense to disentangle them, accomplishing as much as possible under the first mindset before adopting the second.
In addition to those practical points, there are some theoretical reasons to write the entire first draft before embarking on any revisions. The most important is, simply, that revisions, just like first-draft writing, are carried out under a 'theory of the book'. In order to revise any sentence, paragraph, or chapter, you need to have some idea of how it fits into the whole, and what angle you're revising for, and why; otherwise, you don't know what to keep, what to expunge, what to fix, or how. And it's inherently impossible to know these things without having a complete theory of 'the book' as a whole. And, returning to the initial point, because that theory is changing until near the end of the first draft, revisions can't really happen until then. So it makes sense to put off revising until the initial drafting has taken place.
Note that the idea of writing the entire manuscript before revising does not translate into the process of writing individual chapters. Many people I know attempt to write and polish individual chapters before completing the rest of the manuscript. (This is particularly true of academics, who often use individual chapters as conference papers or articles, and write and polish one-at-a-time.) However, there are a few problems with this approach too. First, it presupposes that you know where in the document each argument or example will belong. In everything I've written, ideas move around significantly during the course of revisions, so that paragraphs that began in (say) chapter 1 might wind up in (say) chapter 5 or 6, or vice versa. Polishing individual chapters makes such moves difficult. Second, even when arguments don't move around between chapters, when individual chapters are polished before the entire draft is complete, it can be difficult to integrate nuances of arguments between the chapters. Finally, on a psychological level, as Ayn Rand points out in The Art of Nonfiction, it can be demoralizing to go from a polished final draft of one chapter to a messy first draft of another, and this can bring its own set of emotional and psychological challenges. Again, better to get all 90,000 words of ideas out of one's system, in all their unpolished messiness, before deciding what to do with those ideas and how to shape the next stage of the document.
3. Edit the complete manuscript in iterations. Editing, like writing, will change your sense of what the document is saying. Therefore, editing should be carried out in multiple stages, since it is unlikely (or impossible) that any one round of editing will create the final version of the document. Rather, the final version of the document emerges from various layers of editing: the revision of chapter 1 will necessitate changes in chapter 6; but those changes in chapter 6 will also cause changes in chapters 1, 2, 3, 4, and 5, which will in turn cause changes in chapter 6. These large-scale processes of bringing the book "into agreement with itself," so that the individual components have ceased to contradict each other or repeat after each other, is a fully absorbing mode of editing--and it's difficult to accomplish it while also tinkering with sentences and word-choice. So, separating out the various rounds of editing can be helpful in making each one as efficient and productive as possible.
How many rounds of editing are needed? This is probably a matter of taste and personal preference. The way I think about the issue is mostly psychological: as Eviatar Zerubavel advises in The Clockwork Muse, the ideal number of drafts is high enough that no individual draft introduces the pressure of getting things perfect all at once, but low enough that the process doesn't seem endless. Of course, these calculations will be different for different people. Zerubavel recommends doing 7 drafts; so far, for long documents I think I'm a 5-draft writer. (By contrast, when I write articles, I typically need only 3 or maybe 4 drafts, since it's comparatively easy to be coherent and integrated when you're dealing with only a single thread of argument.)
My process for going through the drafts looks something like this. First, I write a complete, messy, awful first draft. I attempt to do this as quickly as possible, both because I want to ride the wave of enthusiasm, and because I know that the writing will need a lot of revision anyway, so there's no point in taking even a minute longer than is absolutely necessary to get the awful first draft on paper. I attempt to write approximately 1,000-1,200 words a day during the first draft stage, and I stop myself once I've reached this goal, even if I'm midway through a sentence (especially if I'm midway through a sentence!) because I don't want to exhaust my ideas and have nothing to say the next day. By stopping myself at a given word limit, no matter how excited I am or how well things are flowing, I guarantee that I'll be able to hit the ground running the next day. At the rate of 1,000-1,200 words a day, you can write a 90,000 word draft in approximately two and a half or three months.
Having written the draft, I then take stock. I think about the flow of argument, I think about ways to re-order the pieces, and I think about what might be missing, which sections need to be lengthened or excised, etc. I then write a second draft, moving significantly more slowly than in the first draft. My goal for the second draft is always to make sure the paragraphs and chapters are roughly in the right order. At this stage, I still do not worry about the awful prose. The sentences are a mess, but I try to get the ideas in vaguely the right place in the manuscript. When writing my book, I also experimented with retyping the entire manuscript in a new, blank document from scratch for the second draft (following the advice from Zerubavel). I found this to be extremely helpful for two reasons: first, because printing the MS and retyping it from scratch gives me simultaneously a written, fixed first draft to work on as well as the freedom of a blank document. I feel safe making changes and trying experiments knowing that I won't lose work I've already done. Second, it allows me to (subconsciously) revise some of the sentence-level prose as well, since it's very difficult to retype a terrible sentence without making tiny tweaks that improve it. Although fixing the prose isn't my goal at this point, I can make little changes in the process of typing the new draft that I probably wouldn't think to make (and perhaps wouldn't even notice) if I were just picking through the same document as the original first draft.
Having written the second draft and gotten the ideas vaguely in the right order, I then repeat the process at the level of the prose. First I take stock; then I retype the entire document once again.
For drafts nos. 4 and 5, I no longer retype the document; at this point, the main ideas are in the right place, and my goal is to make the prose flow as well as possible.
To be continued, with thoughts on outlining, stamina, and other aspects of the process of writing long documents.
No comments:
Post a Comment