Ah, sweet joy. Your new book is out in the world. Now, you can sit back, relax, and let the reviews, acclaim, and cash roll in. If only life were so wonderful and you could take some well-deserved rest after book publication, but unless you are Mr. King, Ms. Steele, or Mr. Gladwell, you will still have much work to do, particularly if you want others to read and buy your book.
Thursday, March 25, 2010
Writing a Book: Part 4, Promotion
Monday, March 22, 2010
Writing a Book: Part 3, Answering some Questions
I wanted to address some of the points raised in the comments section on Brian’s blog. Stan raises several interesting questions.
How did you solve the balance between themes that you personally found interesting, versus themes that would appeal to a wider audience? -
This gets to the heart of writing. I once saw Tony Hillerman give a talk in which he said “Don’t write what the readers won’t read.” Good advice, particularly if you spent hours or days tracking down some random bit of information or some side story; it is very hard to not put that fact or story in the book. One way around this is to use endnotes, which is a sly way of slipping in your research without having it break up the story line. (This change often didn’t come until much later, after I had the time to better consider my cool fact and to realize it probably didn’t need to be in the main body of the book.) I have found that if I have to struggle to put something in that interests me, then it probably shouldn’t go in the story. Another way around this is when you do feel a theme is necessary but perhaps is less interesting to you, then couch it through something that interests you.
I do get friends involved. As I wrote earlier, I often bounce ideas off them to get their reactions. I did have friends read various chapters, not for editing purposes, but to see if they thought the chapter flowed and if they thought it was interesting. I did get good advice from friends but also recognized that they would not be completely honest if they didn’t like it.
How did you balance time between research and writing? I find there is *always* one more book or article to read, and have to force myself to sit down and just write. -
Yes, there is always more research to do, particularly if you are looking to procrastinate on the writing process. One way to stop researching is to have a deadline. I gave myself two months to research and write my chapters, which definitely forced me to close the books and start writing. And, ultimately, I figured there was no way I could get every fact and figure in so I might as well move on.
Some people have suggested going with a NaNoWriMo-style approach of "write first, edit later." How carefully did you proceed when first writing, and how much editing did you do afterwards? -
I write. I edit. I write. I edit. I edit a lot when I write and am not very good at letting go and simply putting stuff on the page. I do, however, write lots of material that never goes forward. I have found that doing so does allow me to get things out of my brain and allows me to move the process along.
In regard to editing, I have a couple of things I like to do. I do edit on the computer as I go but for more serious editing I print out the document. I also will read it aloud, which helps with structure and flow. And, finally, I let the material sit overnight or even longer. I want to get the writing out of my system and try to approach it with fresh eyes.
And what was your daily writing practice? (Always at certain time of day? Always in certain cafe? Warm up exercises? Write on paper, then transcribe into computer? Did you print out drafts along the way for editing?)
I am not sure exactly what you mean by this. I write on an iMac and use MSWord.
I don’t really have a daily writing practice except to consider it a job. I am usually on the computer by 7am and off it by 5-6pm. I don’t work well at night. I usually take a nap in the afternoon. Some days I write. Some days I do research. Most days it was a combo. I write on the computer though when I am really bogged down I will write on paper. And, yes, I killed trees on a regular basis printing out drafts for editing.Thursday, March 18, 2010
Writing a Book: Part 2, the Writing
Earlier this week, I wrote a bit about the early process of writing a science book, focusing on converting an idea into a proposal. Michael and Brian did the same and then addressed the writing itself. As Michael observed, each writer takes a different approach, and mine was unlike his or Brian’s.
Monday, March 15, 2010
Writing a Book: The Idea, The Proposal, and Publishing
As I noted the other day, Brian, Michael, and I are starting what we hope to be a conversation about science books, science book writing, and science book publishing. The initial topic is on how to make a technical (and possibly, seemingly obscure) topic accessible, exciting, and of interest to a publisher, as well as to readers. As with Michael’s post, this turned out a bit longer than I expected.
The basics of the proposal are somewhat formulaic: what is the book about, who you are, or why you are the person to write the book; marketing; inspiration and competition. My proposal for Stories in Stone ran to around 60 to 65 pages. It started with a broad opening to the subject, followed by a short section on how I would approach the subject. I also included a brief outline, detailed descriptions (600-900 words) of each chapter, and one full chapter. The chapter isn’t always necessary but for an unknown author it is. You have to show that you can write. The marketing, about the author, and inspiration and competition sections took up just four pages of my proposal.
Friday, March 12, 2010
Writing a Popular Science Book: How-To Next Week
Wednesday, March 10, 2010
Mariner Tower Update
Friday, March 5, 2010
Morton Liquor Update
Thursday, March 4, 2010
Roxbury Puddingtone: Boston's Church Stone
Close up of the puddingstone
The Roxbury is to geologists what the dropped 'R' is to linguists, a sign that you are in Boston, for the puddingstone only occurs in and around the Hub. And like this linguistic trait, no one knows exactly where these rocks originated. It shares some affinities with rocks in west Africa. But it also shows traits of South American rocks. About the only thing that geologists agree on is that the Roxbury was deposited between 570 and 600 million years ago.
Like most sedimentary rocks, the Roxbury Conglomerate is the product of the breakdown of other rocks. Recent analysis indicates that it may have originated in a landscape that looked like modern-day Japan, with a range of volcanoes separated from the sea by a flat plain. Like all mountains, they were involved in a battle between uplift and erosion. And like all mountains, erosion won. Streams washed these eroded bits and pieces into a chaotic mix of sediments at the base of the mountains. In some places, gray to green lava flows abut the puddingstone, indicating that some of the volcanoes were active with molten rock flowing off their slopes.
The Roxbury sits in the middle of a suite of rocks that includes granite found in Dedham and muddy slates that occur in Braintree. These rocks formed between 650 and 505 million years ago on, under, and in oceans bordering the drifting land mass known as Avalon. In its slow movement toward North America, Avalon may also have picked up a hitchhiker or two, which further complicates its history. Ongoing research, especially finding precise dates for all these rocks, continues to clarify details of the Avalonian picture.
Others though do not even agree with these theories. In The Dorchester Giant, Oliver Wendell Holmes wrote:
They flung it over the Roxbury hills,
They flung it over the plain,
And all over Milton and Dorchester, too
Great lumps of pudding the giants threw:
They tumbled on thick as rain.Giant and mammoth have passed away,
For ages have floated by;
The suet is hard as a marrowbone,
And every plum is turned to a stone,
But there the puddings lie.
No matter what you want to call the stone, it is a nice looking rock and apparently a better stone to work with than the Leesburg Conglomerate.