Writing a book will almost kill you. By the end, you’ll be exhausted, brain dead, and filled with a bubbling sense of anxiety. I recently finished up my first book, and here are a few takeaways from the ordeal that can be applied to pretty much any large scale project.
. . . .
Books are complicated things. It doesn’t matter if it’s a technical manual, non-fiction, or fiction, keeping track of everything requires a lot of effort, which is exactly why special software exists for helping you do that.
After trying out a bunch of different software, I settled on Ulysses (though Scrivener is excellentas well, as is Evernote) to get everything organized. Ulysses has an excellent exporter system where you can define how the formatting works, so it can easily be turned into a Word document with the specific formatting options a publisher needs (and they always want a specific format, regardless of the type of book).
. . . .
Of course, it doesn’t really matter what tool you use, but pick something before you start and stick with it. Be prepared for your notes, outlines, and everything else to become a cluttered, unreadable mess if you don’t create a system for dealing with them ahead of time.
. . . .
A schedule is great, but be prepared for everything you’re doing to take considerably longer than you think it will. This is especially the case at the beginning before you get into the flow of writing.
In my case, this was mostly about formatting. Learning what a formatting a publisher wants and digging through their style guide every other paragraph seriously slows you down. Until you get the hang of it, everything will take twice as long as it should.
Since my book’s a collection of Raspberry Pi projects, it also meant I had to actually make everything in the book, troubleshoot problems, and get projects working properly before I wrote anything. I didn’t think about this in my initial planning phase, and quickly realized that I wasn’t giving myself enough time. I had to redo my schedule completely to accommodate this.
. . . .
There’s a common adage with fiction that you should prepare to “kill your darlings”. It’s about deleting sentences or words you love for the greater good of your work. But it’s bigger than that. In reality, be prepared to kill off full paragraphs and chapters—I cut massive parts out before sending it off for editing.
And that’s just your own editing—your editor will cut even more. As I started getting notes back from my editor, I quickly realized how I couldn’t take any of those edits personally. Obviously a book about a Raspberry Pi is different than a work of fiction here, but the same basic premise remains: you will be ruthlessly edited. Accept it. I was so caught up in writing this book, I often wrote in a weird, privatized little language that was clearly a result of working too hard. By the end, I became the Raspberry Pi: small, low powered, and a bit closed off from the rest of the world. The later chapters made no sense, and the notes sent back to me are best summed up as, “what are you saying here?!”
Link to the rest at Lifehacker and thanks to Meryl for the tip.
Prior to reading this post, PG hadn’t heard of Raspberry Pi. If you’re like PG, here’s a link: Raspberry Pi.