Thursday, August 30, 2012

Blog #2, due by Mon, the 3rd


For this blog, you're going to a rhetorical analysis of sorts, based on a review of your choosing (this may be a film or television review -- you can use the review you used for your first blog if your discussion is much more thorough than the first, or you can choose a new one). 

Be sure to link to/or embed the review you've chosen in your post.

You should proceed paragraph by paragraph, explaining what the author is doing and more importantly, HOW, to the best of your ability (again, I realize you probably don't know a lot of the names of particular rhetorical strategies, so do the best you can). I've posted a list of rhetorical strategies in "Content" (we'll be using this extensively when we get to Paper #2 -- the rhetorical analysis, so consulting this now will be beneficial on a number of levels). 

What are you looking to identify? On one level, you should discuss the review's title, the lead (its effectiveness as a hook for the rest of the piece), plot synopsis, discussion of actors and performances/development of characters, directing/director,  the kinds of ideological connections the writer makes to current issues, trends, values, or events -- all the things we've discussed in class this week.

Paragraph by paragraph, explain the writer's rhetorical progression and choices. Name them where and when you can (for instance, we briefly discussed the "Breaking Bad" author's use of alliteration and sophisticated diction). 

I'm posting a sample that I believe will give you a concrete guide of how to proceed here. The more you closely examine writing, the more informed choices you'll make in your own writing. Taking apart a review, especially one you admire and might use as a template, will, without a doubt, make you closely consider how and where you'll address the "have tos" of a review (as well as other elements often treated, like cinematography, musical score/soundtrack, tone, mood, style, etc.)

The sample will be posted in a separate blog posting. 


No comments: