DevOps Zone is brought to you in partnership with:

I'm a writer, programmer, web developer, and entrepreneur. Preona is my current startup that began its life as the team developing Twitulater. Our goal is to create a set of applications for the emerging Synaptic Web, which would rank real-time information streams in near real time, all along reading its user behaviour and understanding how to intelligently react to it. Swizec is a DZone MVB and is not an employee of DZone and has posted 67 posts at DZone. You can read more from them at their website. View Full User Profile

Write Sitting Down, Edit Standing Up

05.09.2013
| 3287 views |
  • submit to reddit

On March 26th I giddily said it takes about two months to write a technical book. Still high from the recent success it seemed like the thing to do.

Hemingway writing

Hemingway writing

It is now May 9th. I am editing.

Well, sort of. I had thought my writing was awesome, that there will be hardly any editing needed and on the 9th of April, just two weeks later, there was a reality check in my inbox.

It was the editor, “Hey this is really great, solid writing, I just fixed some spelling and markup for ya.”

And truly, all the fixes were either typos or British English – they want American. Something about markets.

“Oh and shorten the book by 60 pages. We said 100, you wrote 180, we can do 120 tops.”

*gulp*

It is now May 9th. I am editing.

The stickler is that my beta readers said they’d like even more content in the book, definitely not less. Obviously, I can’t cut any content out of the book and I can’t make the code examples shorter either. People have already complained the examples are a bit terse and hard to understand at moments.

I could take out some screenshots, but this is a book about creating shiny visualizations for the internet. Screenshots must stay.

The only thing left is the writing. I have to go through the whole book and use less words to say more.

*gulp*

Facing such a monumental task, it is therefore not a surprise I’ve only spent about 30 hours editing my book in the last month. That’s averaging just an hour per day – the average for writing was two and a half.

And editing time isn’t even half as efficient as writing time. For every two minutes of staring bleary eyed at the screen, dragging the words through my mind like so much barbed wire, I spend five minutes prancing about on the internet feeling like I’m riding a unicorn in comparison.

Editing really is sheer drudgery. There is no flow. There is no inspiration. Just a constant ruthless cutting and rewording. All those little things you thought added a special flair to the writing, let your personality shine through, entertained the reader.

Waste. Plain old waste. Vomit of a writer who’s been staring at the screen too long.

It all has to go.

And the writing is much better for it. But you’re still sad to see it all go.

Actually, not so much sad, as indifferent. You don’t feel anything but the monotonous drudgery of rewriting something you’ve already written and not coming up with anything new. You can’t; add something new and the word count goes up not down. Can’t have that!

It’s been fairly successful, too. I’ve finished the first two chapters. One cut down from 14 to 9 pages, the other from 51 to 40. Just by improving the writing. No loss of content.

But it’s just so … it’s terrible.

This weekend I discovered a trick, though. I was at a friend’s place and as I was editing in the kitchen when I realized that the chairs are terrible and the table is the wrong height.

Peeved, I moved to the counter. Editing standing next to the kitchen counter, shoulders slouched to stare at the screen …

… before I knew it, two hours had passed and I'd edited five pages of text. Amazing! I had fallen into flow. Editing! Flow!

I don’t actually know if this was because of my friend’s kitchen or because I was standing while writing. But today I’m going to repeat the experiment.

Fingers crossed it works!

Published at DZone with permission of Swizec Teller, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)