| I co-authored my first book in 2001 and despite going through the trials that all first time authors go through, I caught the writing bug and found a new “hobby”. Since then I’ve been an author or co-author for eleven books and an editor on several others. If you are interested in learning more about the writing or editing process, check out my presentations. |
Author or Co-author
| I enjoy writing and contributing new material on a topic that can help people do their job quicker, easier, better. Writing a book is by no means an easy proposition due to the many late nights and long weekends it requires, but it is a great way to become intimately familiar with a topic. I’ve been an author or co-author for the following books: |
Editor
| After writing several books, O’Reilly asked if I was interested in editing some of their IT Professional books. There are different flavors of editors; I’ve been a developmental editor and an acquisitions editor. A developmental editor’s duties consist of managing the overall progress of the book, reviewing and editing all content, managing the technical review process, and preparing the manuscript for production. An acquisition editor evaluates new book ideas, finds appropriate author(s), and guides the book proposal through the approval process.I’ve been an editor for the following books: |
Buy from Pragmatic Bookshelf |
![]() Buy from Pragmatic Bookshelf |
Technical Reviewer
| After some portion of the first draft of a book is complete, the editor will start sending the completed chapters to technical reviewers. Technical reviewers play a key role in the publishing process by checking the manuscript for technical errors, evaluating readability, and making recommendations to add or cut content. It is a lot of work for not a lot of money, but being a technical reviewer can give you a taste of the publishing process so I highly recommend it for wannabe authors.I was a technical reviewer for the following books: |


