Review limitations

[Sledge]

I have several of The Le's pdfs, and while I was not given them with the expectation of reviews, I'm planning on doing a few. However how much review is too much? I tend to check class balance out by analyzing the levels versus core classes. This takes up a little space and is sometimes hard for others to follow. Should I be glossing over the analysis and just giving the results, or is it good to include it all?

 

[JoeGKushner]

Try including everything in your first review and see what the feedback is.

Look at the space John Cooper uses for his errata. While it's not everyone's thing, many people, including myself, thank him for it.

 

[MatthewJHanson]

I say provide the analysis, but make it easy to skip over if its not that customer's thing. End it with a nice summary paragraph that condenses your overall thoughts on the product. I know I at least will sometimes just skip to the end.

 

[Cathix]

Don't forget to share your opinions of the art, layout and ease-of-use. While I can't speak for Thele, I know I'd like to know what a reviewer thought of these areas in my company's pdfs.

 

[TheLe]

Personally I am not one to tell a reviewer how to review.

However, my favorite reviews tend to come from PC.IGN.COM, where they discuss all the different areas of the game, and then give a final summary.

I often go straight to the summary at the end of the review because of my dislike of reading. And writing. Well, and editing too.

But everyone is different. Find your own style of review and go with it. Just don't give a 1 paragraph review, because that doesn't help anyone.

`Le