Being a Technical Reviewer

I was contacted last month by UK publishing house Packt Publishing about being a Technical Reviewer for their recently-published book WordPress Mobile Applications with PhoneGap (ISBN: 1849519862). I accepted even though I did not know a lot about the subject. However, the whole experience was a learning process for me in terms of both how the publishing world works and about the technologies I was reviewing.

WordPress Mobile Applications with PhoneGap book coverThe book is positioned as a way to:

  • Discover how we can leverage WordPress as a content management system and serve content to mobile apps by exposing its API
  • Learn how to build geolocation mobile applications using WordPress and PhoneGap
  • Step-by-step instructions on how you can make use of jQuery and jQuery mobile to provide an interface between WordPress and your PhoneGap app

The reviewing process is pretty straightforward. The chapters are sent to you by email as the book is being written and they are usually in Microsoft Word format. The chapters are early drafts and usually contain typos and formatting errors. Eventually those will be corrected by the book’s editors. Your job is to review the code and text for technical accuracy. You also make sure the chapter structure is logical and easy to follow for readers. Any corrections/clarifications/notes you make are placed in Comment tags as you do not edit the text directly. After you finish your review you then fill out an opinion questionnaire about the chapter you just read. The editors want to know what you would like to see more of, less of, if there were important topics that were missed and your overall score out of 10.

If you are interested in being a Technical Reviewer for Packt you can check out their Reviewing for Packt information page. Although you do not get paid to be a reviewer you will receive acknowledgement on both the “Credits” page and the “About The Reviewers” page where they will include a short biography about you. This is a great promotional tool for you as you can mention your blog/website address and Twitter accounts if you wish. As well, you will receive both a paper copy and an eBook copy of the book you reviewed. You will also get an eBook copy of any other book in their catalogue.

Being a Technical Reviewer is a great way to learn more about a topic and to see how the publishing industry works. It is also a neat way to see how books are put together and you can learn many useful writing tips which will help your writing in other areas including making you a better blogger. It will also especially help if you are interested in writing a technical book in the future. As a Technical Reviewer you will gain a publishing credit and it might just make your book proposal that much more enticing to prospective editors.

Advertisements

About Ken Cenerelli
I am a Programmer Writer, .NET Developer, Microsoft MVP - Visual Studio and Development Technologies, Public Speaker, Blogger, and Microsoft Azure Nerd. I blog regularly at kencenerelli.wordpress.com and can be found on Twitter via @KenCenerelli.

One Response to Being a Technical Reviewer

  1. Pingback: Azure book I technical reviewed now available | Ken Cenerelli

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: