Technical writing is hard work, and not for the faint of heart.
Good technical writing is hard because you can't BS, if you have any craft and you're not writing online help files then you're forced to work within a defined process that mandates crtical reasoning. Writing can eat up huge chunks of time and creative effort.
I'm actually starting this blog against my better judgment. One, because opinions are like, well, you know the old saying. Two, like everything else I'm passionate about, writing can become an obsession to the point of being a pain in the ass. In February of 2003 I was asked by Wrox Press to write about the SQL Standard for an upcoming book, Professional Standards for Programmers. One month and several deadlines into the project, Wrox and their associates went bankrupt, and I've sworn off writing since. When I saw Joseph Sack's post, A Book's Death, Rebirth, and Re-rebirth, I got a strange feeling of deja-vu, or something like it, and got motivated to write for the first time in a while. Congratulations to Joseph on a job well done. As for me, I've got some writing to do.