I've been talking recently with Philip Beadle about the book DotNetNuke for Dummies that he co-authored and some of the effort involved in doing it. I was then wandering through the local bookshop shortly afterwards and saw 4 copies of it on the shelves and thought to myself "That's pretty cool".

But is it really worth it to write a book - and how much payback is there in doing it? Here's a somewhat sobering blog post by Scott Mitchell about the realities of authoring a tech book.

It's really worth reading; not as a deterrent but as a reality check. If you want to write a tech book - go for it, just be prepared for it to be a labour of love, not a path to early retirement.