Book Writing Experience

Compared to Engadget, TechCruch or CNET, Slashdot is not the fastest news source on the internet. But the reason I still read Slashdot every morning is its community.

Ask Slashdot might be the best thing on Slashdot. I've tried to reproduce this phenomenon on Blognone but haven't achieved that level yet.

Today, there is a thread on Ask Slashdot about Tools & Surprises For a Tech Book Author? . The answers are varied but some really strike my mind:

First, expect it to be another full-time job. It takes up as much time as you have, and even more, and forget about having a personal life while you're writing it.

That's exactly what I have discovered during the Drupal book.

Make writing a habit. Set a production schedule and stick to it -- its too easy to take a day off, which then turns into two days, into a week, and then just gets worse and worse. Set out a plan, both long term and short term, track your progress, update the plan as you go, and keep writing.

It can't be more true. My session last 6 months and counting (even with detailed schedule!)