When I received my contract to write How To Do Everything with HTML, I had no idea what I’d gotten myself into.
Oh, I knew I was going to write a computer book.
What I didn’t know was that the whole process would be done at a pace that bordered on insane.
Because technology changes so quickly, computer books are produced on a much faster timetable than other books. Otherwise, they can be obsolete before they ever hit bookstore shelves. The ink on my contract had barely dried when my editor e-mailed me and asked me to develop a chapter delivery schedule.
I had 20 weeks to write a 600+ page book.
If that weren’t stressful enough, I discovered that the entire writing, editing, rewrite, and proofing process would take place simultaneously.
It went something like this: For week number one, I had to write my first chapter. That included more than just writing the text. I also had to develop the HTML code. And I had to design and create all my own illustrations. After I turned in chapter one, the next week I turned my attention to the second chapter.
Like chapter one, I had to write the text, code, and illustrations. But I also had an additional task.
I had to incorporate tech edits for chapter one.
The publisher had graciously hired a technical editor who went through my HTML code and found all the bugs. Then he kicked the file back to me so that I could fix it. Thus, in the second week I had to write a 20-30 page chapter, create the computer code, design and produce my own illustrations, and incorporate the tech edits from chapter one.
Then things got even more challenging.
By about the fifth week I began to receive copy edits. So now my weekly workload involved writing a new chapter, developing the HTML code, designing and creating my own illustrations, incorporating tech edits from previous chapters, and reviewing copy edits from previous chapters.
I didn’t think it could get any worse.
About three quarters of the way through the project, page proofs began to come in, chapter by chapter. So in the last month or so, every week I had to write a new chapter, develop code, design illustrations, fix bugs, review copy edits, and correct page proofs.
It was like running down a railroad track with a mountain on one side, a cliff on the other and a locomotive breathing down my neck.
By the time I reviewed my last page proof, I felt like I’d just finished the writer’s version of the Ironman triathlon. I breathed a huge sigh of relief when I sent off that final file.
A sinking feeling followed that sigh of relief.
I was ready for a long rest, but that would have to wait. About halfway through the project I’d suggested an idea for a follow-up book on Cascading Style Sheets (a related language that works hand-in-hand with HTML). The publisher liked the idea, gave me a new contract, and told me to get started right away.
For another 20 weeks, I kept running down that railroad track.
It was an exhausting process, but I’m thankful that my first books were produced this way. The schedule was brutal, particularly for a brand new writer. But I learned a valuable lesson.
I learned that I never need to let writer’s block defeat me and that I can produce consistently every week. There were many days when I didn’t feel like writing. However, because of the breakneck pace and tight production schedule, I didn’t have time to wallow in self-pity or give in to writer’s block.
I had to produce.
If I gave in to writer’s block, then the next week I would have twice as much work.
And so I wrote.
For me, writing two computer books in the space of nine months was like boot camp. The publisher put me through the wringer.
But in the process, I learned how to deal with writer’s block.
I sit down and write.
Do you struggle with writer’s block? Or have you developed a way to deal with it?