Author Archives: Rebecca

Fifty Shades of Grey by E. L. James

by Rebecca

This is the first of two reviews of this book. The next one will likely be somewhat more positive. So keep an eye out for another forthcoming review.

Fifty Shades of Grey
E. L. James
2012

I enjoy fanfiction, both the fact that it exists as a genre1 as well as the genre itself. Thus, when I heard that someone had written an AU2 Twilight fanfiction and then changed the names in order to publish it professionally, I decided to read it. I hadn’t enjoyed Twilight, but mostly I found it uninteresting and poorly crafted. With a different author and a different setting, this had potential.

Especially since the articles I had read about it, were mostly shocked by the fact that apparently women can like sex. Yes, even mothers! The fact that this is apparently shocking makes me mourn for the women’s movement. Given that this was the primary complaint about the book, I thought the book must be pretty good.

Alas, I was doomed to rather severe disappointment.

To a certain extent, E. L. James did fix one of the major problems I had with Twilight. The characters are well presented. The narrative descriptions match their actions. Thus, Ana is both described as shy and acts shy. Christian is both described as arrogant and acts arrogant.

Another thing the author does really well is build anticipation. What’s going to happen next?, how are these two characters going to get together?, etc. It kept me reading for about half the book.

Then I hit the first sex scene, and wow, the badness.

From there on out, as the book attempts to get more serious, it becomes something of a travesty that I had trouble slogging my way through.

It’s not clear to me that this author (or the editor for that matter) knows what sex involves or any real concept of physicality or how bodies work much less anything at all about the BDSM3 lifestyle. Given the whole plot of the book is based on the sexual awakening of a young woman and the moderate depravity of her love interest, the lack of understanding on the author’s part is a major problem.

The problem with this book is not that it was based off of another author’s work and not that it contains a lot of sex; the problem is that it’s poorly researched, poorly written, and, to an even greater extent than Twilight, it attempts to romanticize a highly dysfunctional relationship.

1 U.S. Copyright law involves a fundamental division between idea and expression. Ideas are not considered under copyright, ever; only the expression of those ideas is protected. In the past, this was taken to literally mean the exact words. Even translations were considered to be a matter of the ideas rather than the expression. More recent legal interpretations of copyright have expanded what exactly is considered an expression to include not only translations but also events, places, and characters. However, no case of fanfiction has ever made it through the court system, and thus whether or not the genre infringes on copyright remains uncertain.

2 AU in this context means “Alternate Universe.” In fanfiction, this means taking well-loved characters, relationships, and plot devices and transposing them into completely different settings and situations. In this case the Twilight characters were used in a modern setting.

3 BDSM stands for Bondage & discipline, Dominance & submission, Sadism and Masochism. (It is not to be confused with DBMS, which stands for DataBase Management Systems, with which I am somewhat more familiar.)

The rest of this review is going to involve spoilers of the R-rated variety, so I’m putting a break here. Proceed at your own risk. Continue reading →

What happened to conclusions?

by Rebecca

There are some traditional plot arcs out there that various authors use, re-use, re-interpret, or ignore entirely, depending on their choice. But there is one basic plot arc that I consider pretty universal: beginning, middle, end.

First there’s the beginning in which the writer starts the story and introduces the characters and the world and the problem at hand. Then there’s the middle in which stuff happens. Finally there’s the end in which the results are revealed for the stuff that happened in the beginning and the middle.

Is there some post-modern style now that considers endings to be passé? Because I have recently read two young adult books that I enjoyed right up until I realized that the last few pages weren’t actually going to involve any sort of conclusion.

There’s a difference between a book being the first in a series and just hacking a book into multiple pieces. Or so I had thought. But twice in a row, two otherwise well written books suddenly stopping like this. It feels like a conscious choice. It’s not a style that I approve of, but I’m beginning to really think it might be a stylistic thing rather than simply bad writing, especially since, aside from the lack of any conclusion, they were good books, or at least two-thirds of good books.

Hollowland
By Amanda Hocking
2010
(Free kindle edition on Amazon)

Remy King is nineteen, the world has fallen apart in a zombie apocalypse and she is going to go across country to get to her brother if she has to walk to do it, beating off zombies all the way. She is kick-ass and awesome, acquires a few companions and loses a few companions (but luckily not the lion, because I never before realized that a proper kick-ass heroine needs a lion companion, but this book convinced me), and is generally determined. This was pretty much exactly what I was in the mood for during my own finals madness.

Except for the fact that this is book #1 of The Hollows series and the plot transitions smoothly into plot #2 before the book ends, leaving me going: Seriously? That’s where you decided to break off? Seriously?

Cinder
By Marissa Meyer
2012

Cinder is a mechanic with a stall at the local market bringing in the only income her family sees. She’s also a sixteen-year-old cyborg in a world that considers cyborgs to be less than human. Her step-mother was not happy that Cinder’s adopted father had decided to adopt a cyborg and even less happy that he then proceeded to die of the plague just a few months later.

A lot of people are dying of the plague these days. Including the Emperor.

Which leaves the prince and heir to the throne in the rather unhappy position of being pressured to marry the queen of the independent moon colony. The lunar people have mind control powers and their royalty tend to use assassination and mutilation to get what they want.

This is the kind of crazy re-imaging of the Cinderella fairy-tale that I just can’t resist. It was excellent and crazy and fun… right up until the final climactic scene turned out to be less climactic and more of an introduction to a whole new plot arc with no conclusion in sight. Apparently there are four more books in the works.

So, what’s up with this?

Neither ending is really a cliff-hanger, per se. They’re just incomplete stories. For anyone who reads amateur fiction published online, it feels like I just came to the end of the posted portion of a WIP (Work in Progress). I had rather thought that the benefit of reading formally published books is that none of them are WIPs. It’s depressing to discover that’s not the case.

So, I ask again, is this really a style of writing that’s going around now: plot arcs composed of beginnings and middles, but no ends?

The Edible Book Festival

by Rebecca

The Edible Book Festival
An Annual International Festival
April 1st

This is a collective review and an introduction to a whole genre of books that you may not be aware of. These books are not necessarily intended to be read, but rather to be eaten.

The annual Edible Book Festival is an international celebration that always falls on April 1st, i.e. April Fools’ Day. Each city holds its own competition for the most impressive, the most creative, the wittiest, or the puniest “edible books.”

These edible books range from simple puns with food names to elaborate craft creations by pastry chefs and book binders. Amateurs and professionals alike show off their creations and compete for various prizes. They range from hilarious to awe-inspiring.

Some entries are books made of edible material. I entered my local competition with a book made of crepes, and perfect bound with melted cinnamon chips.

Other entries are puns based on famous book titles. My second entry was “Grape Expectations,” created by a still life of a cluster of grapes, a bottle of dry sherry, and two wine glasses.

I didn’t win any of the prizes, because there were some pretty excellent other entries. Some of them were:
• Tart of Darkness
• War and a Piece of Cake
• A Separate Pea
• Pride and Pretzles
• The Grill with the Flagon of Pink Goo
• A Wrinkle in Lime

It was lots of fun. I mostly ate War and a Piece of Cake afterwards with a few grapes from Grape Expectations. It could be said that I devour books on a regular basis, but normally this is said metaphorically. Not today though.

When was the last time you ate a book?

Temeraire by Naomi Novik

by Rebecca

His Majesty’s Dragon
Naomi Novik
2006

Throne of Jade
Naomi Novik
2006

In honor of Crucible of Gold being released this last Tuesday, I have to go back and review His Majesty’s Dragon and Throne of Jade, the first two book in the Temeraire series.

The books are:
His Majesty’s Dragon
Throne of Jade
Black Powder War
Empire of Ivory
Victory of Eagles
Tongues of Serpents
Crucible of Gold

I have to admit that I’ve actually only read the first two books. However! The reason for that is that I am clearly insane. Despite how I don’t do this for any other series in the world, I can never seem to start the third book without wanting to go back and re-read the series from the beginning. There are so many good scenes and characters and dialog that I can’t resist it. So I go back and read the first two books, at which point I discover that these are really wonderfully dense books in which the plot and action just keeps coming, and so I can’t really read more than two in a row without beginning to feel a bit glutted. But glutted with awesome!

Eventually I’ll have simply memorized the first two, and then I’ll be able to move on to the third and fourth book, I suppose, and I’m very excited about that prospect. But in the mean time, I have to go back and re-read the scene in which Temeraire hatches, and their first air battle, and when Laurence confronts Rankin, and has dinner with Roland, and… and… and…!

Anyway, plot: This is historical fiction based around the Napoleonic War… with dragons. As it turns out, I like historical fiction a lot more when there are dragons inserted. Especially these dragons.

The main character is Captain Will Laurence, formerly of the British Navy. A variety of circumstance, however, lead him to harnessing a young dragon, Temeraire, at which point, he was, perforce, part of the British Aerial Corp. While the war is, of course, a large driving force for the plot, a larger part circles around the differences between the very formal British society that Laurence is accustomed to, the more casual environment of the Aerial Corp, which bridges that of British society and that of the dragons, and the dragon perspective. While Will Laurence and many of the other characters are definitely characters of their time period, the dragons often act as an outside perspective on events and social mores. Dragons, for instance, have their own perspective on sexism and slavery and right and wrong, which isn’t really anachronistic because, well, they’re dragons.

His Majesty’s Dragon and Throne of Jade both really come together because Temeraire is an absolute delight, Laurence is wonderful in his awkward formality and concepts of honor, and they are absolutely devoted to each other, which just makes their differences with and regarding the world around them all the more apparent.

It’s a story about the love of a man for his dragon, and a dragon for his man. Anyway, these are wonderful books and I definitely recommend them.

Hiring the Best by Martin Yate

by Rebecca

Hiring the Best: A Manager’s Guide to Effective Interviewing and Recruiting, Fifth Edition
By Martin Yate
2006

This is yet another assigned book. One day I will again read for pleasure, but that day will likely not be until the summer. Sigh.

In the mean time, though, I was surprised and pleased to discover that I actually enjoyed this book. Job interviews are not a topic that I consider particularly interesting, beyond the sheer necessity, but the book wound up being enthralling. It goes through all sorts of questions, discussing what those questions are actually asking, how to pick which questions to ask, and how to interpret the answers that you get back. It was also a really slow read, because I was constantly scripting out how I would answer certain interview questions.

As the subtitle states, the book is about recruiting and interviewing. Yate does an amazing job of introducing and concluding with a thorough discussion of how to think about recruiting. Then about half the book in the middle lists and discusses potential questions to ask in a job interview, going over hundreds of possible questions.

It covers what traits an employer should be looking for in potential employees for different positions and then how to tailor a job interview to get at those traits. As someone who is more likely (I hope) to be in a job interview next as an interviewee rather than an interviewer, I found it helpful to consider what these questions are actually asking and how the answers will be judged. However, given my one and only experience running job interviews from the other side of the table, I am extremely grateful that I will never again be quite as incompetent at it as I was then.

Yate writes with a blunt conversational style that I enjoy, and while I don’t agree with his perspective on a couple of things (he’s very corporate sector while I’m more nonprofit sector,) it’s not a pervasive issue. It’s more of a sense that I like him but I wouldn’t talk politics with him for fear of changing that.

Despite the fact that I’m not all that interested in management, I do acknowledge that it’s useful to know about and Yate seems to know what he’s talking about and describes it well. I strongly suggest this book to anyone who’s on the job market or in management.

The Non-Designer’s Presentation Book by Williams

by Rebecca

The Non-Designer’s Presentation Book
By Robin Williams*
2010

Yay! This is a good book. The streak of unpleasant books has ended! This book is current, it has good advice, and, I admit, it’s also pretty (lot’s of sharp pictures illustrating the various principles.)

Like the other books I’ve read recently, this covered a lot of basic foundational concepts, but this time I felt they were covered in a way that respected me as the reader.

I’m now a bit daunted by the thought of actually trying to give a good presentation and a bit retroactively embarrassed by some of my previous presentations. I think the main argument to this book is that it’s important to learn how to actually use a presentation program (like PowerPoint or Keynote or a couple of the other program) and to not ever depend on their templates. You can create really excellent and elegant presentations with these programs if you know what you’re doing and what to pay attention to.

It’s a challenge; I’m going to have to spend some serious time with a PowerPoint tutorial before putting together my next set of presentation slides. But I think my next presentation will be a lot better than my various previous ones.

I imagine this book will go out of date relatively quickly, by say 2015 or 2020 at the latest, as the norms of presentations change again and the technologies described here get replaced by something newer and fancier. But for now, it’s current and lovely. I definitely recommend it.

 

* This is a woman, and not an actor.

Writing that Works by Roman and Raphaelson

by Rebecca

Writing That Works
By Kenneth Roman and Joel Raphaelson
2000

I don’t generally read books that I don’t like. Why bother?

As it turns out, the answer to that is, if they are assigned, then it matters to my grade and thus I had better go ahead and read them.

But really, this makes four for four for this one class, and I just want to read something that I unambiguously enjoy.* At least this book was relatively short and easy to speed read.

Writing That Works is a how-to book that is both extremely basic (know the meanings of the words you use and don’t confuse “its” and “it’s”) and highly dated (a lot of people are now using this crazy thing called “e-mail” to communicate with.)

The simplified nature of the rules it gives for writing means that they remain true. As important as it was to learn them in elementary school, it’s probably equally important to review them periodically. I just get irritated by being told rules that I already know AND that I would argue are often best demonstrated by their exceptions.

It is important to know the rules so that when you break them, you do so intentionally.

Oddly, Writing That Works acknowledges that some rules are meant to be broken but only in the chapter on political correctness, quoting Bernard Shaw’s definition of a gentleman as someone who “never insults a person unintentionally.” While admitting that you may occasionally want to insult someone, it fails to acknowledge that sometimes you don’t want to use the most common words in short sentences.

Sometimes it is useful to use rarer words and complex phrases. I quote Mark Twain: “The difference between the almost right work & the right word is really a large matter—it’s the difference between the lightning bug and the lightning.”

So overall, I would say that if you want to improve your writing, this is a somewhat useful book. But read it with the goal of thinking about what it says as if the statements were suggestions for you to consider rather than rules for you to follow.

* Although being able to grammatically write “four for four for” might well make it all worth it.** It’s not quite up there with “I, where you had had ‘had,’ had had ‘had had;’ ‘had had’ had had a better effect.” but it’s still fun.***

** Actually another thing that makes it worth reading is it introduced me to the story of David Ogilvy and his Russian matryoshka dolls. Ogilvy would give these dolls to his board members with notes saying: “If you hire people who are smaller than you are, we shall become a company of dwarfs. If you hire people who are bigger than you are, we shall become a company of giants.”

*** The fact that enjoy these examples of phrases which are grammatical but excruciatingly difficult to parse may have something to do with the fact that I didn’t enjoy a book about writing in a simple and straight-forward fashion.

Bargaining for Advantage by G. Richard Shell

by Rebecca

Bargaining for Advantage: Negotiation Strategies for Reasonable People, 2nd Edition
By G. Richard Shell
2006

I’m going to start off by saying that I recommend this book: it’s well written and it’s useful.

That is not to say that I enjoyed it. But for now, I’m going to focus on the “useful” aspect.

Bargaining for Advantage did an amazing job of teaching me a topic that I really wanted to avoid and doing so in as enjoyable a manner as possible, which just wasn’t all that enjoyable. It was kind of like having a really nice, capable guy for a dentist. He’s a nice guy, it’s a necessary experience, and wow do I not want to deal with it.

As I mentioned in a previous review, I did not find Difficult Conversations particularly useful because the conversations that book dealt with were not the ones that I find difficult. What do I find difficult? Bargaining.

So, my first reaction is to shudder in horror at the title. I hate bargaining, I consider myself quite bad at it, and I avoid it whenever possible. I don’t even like thinking about bargaining. To me, paying a higher price for something is an irritating but acceptable price to pay for not having to bargain.

Despite this, once more and for the same class, I read a book that I found painful to force my way through. However, I’m willing to acknowledge that it’s my own idiosyncrasies that made it so, and the book itself is actually quite good. It’s both well written and provides useful information and good advice on implementation.

The book has two main parts: the first half discusses the foundations of any negotiation and it just made me cringe because I didn’t want to have to deal with any of them. The second half is about the negotiation process and that, while still painful, was also somewhat soothing to my poor introverted and avoidance-heavy sensibilities. It walked me through how to deal with the six foundations previously introduced. I still don’t want to deal with them and I’m not looking forward to any actual bargaining experiences, but I do think I have a much better handle on how to approach those situations when they’re necessary.

Also, the negotiation styles and techniques were all illustrated with a plethora of examples from around the world and throughout history. The stories were all fun, fascinating, and informative. They consisted of little anecdotes about modern and historical figures, familiar and foreign cultures, and successes and failures at the bargaining table. They were pretty much the saving grace of this book for my sanity, since every time I started to worry too much about having to (oh dear god) deal with some bargaining technique myself, there would be some bit of historical or cultural trivia coming my way.

So to sum up, I hated reading it, but it was still an excellent book and I learned a lot.

“Difficult Conversations” by Stone, Patton and Heen

by Rebecca

Difficult Conversations, 10th Anniversary Edition
By Douglas Stone, Bruce Patton, and Sheila Heen
1999, 2010

There is a reason why I don’t tend to read self-help type books (or attend church services very often either), and that problem is separating the wheat from the chaff. I believe that no one is perfect but everyone has something of value; it’s the ratio of valuable insight to crap that can get annoying.

I rediscovered this as I was reading my next assigned text, Difficult Conversations.

There was a lot of chaff in the book and not much wheat.

I was not looking forward to reading this book anyway, because I hate difficult conversations and will attempt to avoid them if I reasonably can. I have had several situations over the years that maybe could have been improved by my being willing to confront a situation head on and a couple more situations where I was impressed with another person for their strength of will that allowed them to start a needed conversation. So, I started this book, not looking forward to the reading, but expecting it to be good for me.

Instead I discover that once more I am enough of an odd duck that when the authors talk about how I think X, Y, or Z, — and the author’s do write in the second person, “you do this”, “you do that” in order to make all of their pronouncements as personal as possible — I’m over here going, wait, but I almost always respond with G or H or J, rarely with X, and think Y and Z are idiotic. So why are the authors telling me that I always make a certain set of assumptions (which I don’t) and should instead soliciting the other person’s interpretations, when they (the authors) are making all sorts of assumptions about me and, by virtue of the medium being a book, not giving me the opportunity much less an invitation to clarify my side?

At which point I’m feeling all maligned like one of their example cases AND feeling like I’m unnatural in some way, AND feeling like an idiot for taking this personally.

When I brought up my problem with the book in class, though, expecting other students to have had similar thoughts, I discovered that apparently I really am that odd and no one else had a similar take. A lot of the other students thought it was an excellent book that helped a lot. A few of the other students didn’t care for the book for one reason or another (it was simplistic, it contained too many scenarios and not enough theory, the scenarios were all a bit too contrived, etc.), but none of them disliked it for the same reason that I did.

There were some good points. The book did offer some useful ideas about how to distinguish the real goal of several different types of difficult conversations, how to think about each type of confrontation, and how to prepare for each type. Plus, the actual writing is quite well done, and the book goes pretty fast (or it would if I didn’t have to put it down and walk away periodically.)

However, my big conclusion is that while everybody has some set of conversations that they find really unpleasant to participate in, we don’t all agree on what set of conversations those are — a conversation that I consider difficult may not be one that you do and vice versa. And this book really was not addressing my issues at all.

“In the Beginning… was the Command Line” by Neal Stephenson

by Rebecca

In the Beginning… was the Command Line
Neal Stephenson
1999

As an opening caveat, I should say that this is the first in what is likely to be a series of reviews of assigned readings. I read this book because one of my professors said to, rather than through any choice of my own. Arguably, I did make a higher-level choice to take the course, but since I’m writing a review of a book rather than the course, the caveat is still important.

I will say that I was delighted at the assignment.

This is the same author as Snow Crash, Diamond Age, and Cryptonomicon, all of which I loved. Stephenson has also written a variety of other books that I have not read, and given that this book came out in 1999 and I’m only just now reading it because it’s assigned, it should be evident that while I like this author, I choose books that I think look interesting rather than reading just anything he’s written as I do for a couple of other authors.

My first reaction is that this is a really useful introduction to the history of the personal computer. Despite the speed at which computer development happens, or maybe because of it, it’s a useful to understand what computer operating systems are and how they’ve developed and what the competing market pressures have been regarding them.

On the other hand, I’m reminded of why I am wary of interacting with authors and actors as people rather than simply enjoying their work. There are often occasions when I like a book or movie or whatever and don’t want that enjoyment to be tainted by the fact that I don’t care for the author or actor. (Robert Heinlein, I’m thinking of you. And, oh, Tom Cruise. Tom, Tom, Tom. Why?)

Stephenson isn’t too bad though. He seems like an okay sort of guy even when he’s writing a nonfiction essay and not writing with the voice of characters developed specifically to be sympathetic. However, there were multiple times when I wanted to argue back at the book and explain that while I didn’t understand the details of computers that he obviously does, a couple of his metaphors were still poorly applied and had internal inconsistencies, and the motives that he projects onto the people who act more like me than like him are not the motives that I actually have for my actions.

So, over all, this is not the most perfect book ever that simply, clearly, and correctly explains the history of operating systems. If you know such a book, please let me know, but I’m guessing it’s a logical impossibility. Instead, it makes a good attempt, succeeds at a good portion of it, introduces some interesting ideas to think about even if I don’t agree with all of them and does so with a sprinkling of fun, geeky humor.

Incidentally, the book is only 150 pages long and while it can be purchased from Amazon (which I did) or various physical bookstores, it’s also available online for free. If you’re interested in understanding more about computers without reading a computer book, go and read In the Beginning… was the Command Line.