I don't get tired of my own voice, because much of the text is informational. One of my long-term goals as a technical writer is to include more of my voice in my technical writing. That's the kind of technical book I've enjoyed the most over the years - writing that is clearly informative, but also conveys the author's personal experience with the subject. I hope my book does well enough to justify a second edition, and I'll revise the book to have a little more voice where appropriate.
One of the hardest parts for me is when the deadlines are pressing enough that the revision process feels like work. If I can go totally at my own pace, I just enjoy the entire process. But sometimes I have to push and write even when I'd rather do other things. Even then, though, the process is really satisfying. I want people to know how to program because it gives them some power. Basic competence in programming takes away the sense that what we're doing is "magic", but leaves people with a sense of joy at taking on hard challenges and making something that works.
I might go back to some non-technical writing at some point as well. Writing a 200-page non technical book sounds pretty appealing after working through a 500-page technical book! Might be a nice sense of balance to do both kinds of writing, in the long run.
One of the hardest parts for me is when the deadlines are pressing enough that the revision process feels like work. If I can go totally at my own pace, I just enjoy the entire process. But sometimes I have to push and write even when I'd rather do other things. Even then, though, the process is really satisfying. I want people to know how to program because it gives them some power. Basic competence in programming takes away the sense that what we're doing is "magic", but leaves people with a sense of joy at taking on hard challenges and making something that works.
I might go back to some non-technical writing at some point as well. Writing a 200-page non technical book sounds pretty appealing after working through a 500-page technical book! Might be a nice sense of balance to do both kinds of writing, in the long run.