I've been toying with the idea of writing a book recently. Probably not a big 200 page job but even 50 pages on some niche subject. I always remember Jeff Atwoo

I've been toying with the idea of writing a book recently. Probably not a big 200 page job but even 50 pages on some niche subject. I always remember Jeff Atwood once said: "If I had to make a list of the top 10 things I've done in my life that I regret, "writing a book" would definitely be on it." (http://www.codinghorror.com/blog/2012/07/coding-horror-the-book.html http://www.codinghorror.com/blog/2012/07/coding-horror-the-b...) - he means specifically a proper printed book by the way. I'm really intrigued by the success of people like Nathan Barry who wrote The App Design Handbook (http://nathanbarry.com/app-design-handbook/ http://nathanbarry.com/app-design-handbook/) and Designing Web Applications (http://nathanbarry.com/webapps/ http://nathanbarry.com/webapps/). I'd imagine the best way to approach it would be to just try to write a bunch of semi-disjointed blog post type articles on a particular subject, say Customer Development, then edit them together with an introduction, conclusion and some filler content to manage the transitions between articles. That way even if you never actually finish the book you can still release the articles on a blog or email list if you feel like it. That said, your situation is definitely different since you were approached about writing a book on a particular subject. Most hackers who sit down to write a book probably won't have that going for them.