Pages

Friday, November 02, 2012

Crossed

Well, that was a whole lot of nothin'.

For whatever reason, I was on a dystopian YA kick a while back. As such, I promised myself that I'd keep up with the different series. So when I got the chance to read Crossed by Ally Condie, I was looking forward to it. I seemed to remember that this was an interesting story, what with poor Cassia trying to decide who she was going to love, either Ky or Xander, in spite of the oppressive Society. I couldn't wait to see what happened next.

To my surprise, not much happened. The story picks up with Ky in the Outer Provinces and Cassia in a work camp. The two of them look to find each other and then search for where they should go next.

And that's about it. The plot is really thin in this one. There's lots of rumination, lots of poetry quotations, lots of walking and climbing and rafting. And in the end, it felt like I was reading . . . well, nothing significant.

I might check out the next book in the series, but it's not going to be high on my priority list, that's for sure.

Wreck-It Ralph

Thanks to my wonderful wife (who is a wizard at finding cool deals), I was able to see a sneak preview of Wreck-It Ralph a little over a week early. This was a great opportunity, simply because I'd been looking forward to seeing this movie pretty much all summer. I heard it described as a sort of Who Framed Roger Rabbit? but with video game characters. Given how much I love my video games, I couldn't wait to see who got included. I was hoping for a whole smorgasbord of characters. Sadly, there weren't as many as I hoped for. On that account, I was a little disappointed.

But only on that point. I went in expecting a light, silly movie, one designed to stoke up nostalgia and little else. But what I found instead was a well-crafted story. A silly one, sure, but I was pleasantly surprised at how great this movie turned out.

You can get the gist of the plot from this trailer:



Poor Ralph. All he wants is to appreciated for once in his life. But his quest to become the hero endangers his game and many others.

What can I say about this movie? It's awesome. While I was a little dissatisfied with the lack of cameos (there were a lot of classic characters wandering around in the background), the ones that did show up made logical sense from within the story. The internal logic hangs together well too. The characters are a blast. The story, while somewhat simple, was a hoot.

The greatest surprise for me? Alan Tudyk voiced the Candy King. I had no idea until the end credits started rolling. I suspect the people I was sitting next to thought I was crazy when I saw that.

The one caveat I can share is this: beware the ending, especially if you're bringing kids. There's some dark stuff going on in the ending. I mean, I know they're video game characters, but some of the stuff that happens at the end struck me as a bit . . . well, dark.

But it's a great movie nonetheless. If you're a video game fan, go see this movie. Even if you're not, it's a great movie. Just be sure to see it soon!

Wednesday, October 31, 2012

The Law of Superheroes

If you haven't guess by now, I'm a colossal geek. That applies to my recreation choices (mostly videogames), the TV shows I watch, and the movies that I gravitate towards. And that also includes my interest in all things superhero. Believe it or not, I'm not a big comic book reader. I've got a passing familiarity with the Marvel and DC universes and I'll certainly check out some series and titles from time to time. But, as evidenced by my debut novel, I still have a great love for masks and capes. That's part of what attracted me to the book The Law of Superheroes.

James Daily and Ryan Davidson are both comic book fans and lawyers, and they spend the better part of this book seeing how the two worlds might possibly intersect. For example, let's say that a masked hero captures a criminal. Could the hero testify in court while disguised? Could a hero sue someone for revealing his or her secret identity? If a battle between superheroes and villains wrecks a big part of a city, will insurance pay for the damages? Daily and Davidson seek to answer all of those questions and more.

Where was this book when I needed it? When I was writing Failstate, I puzzled over a lot of these questions and I didn't feel comfortable contacting a lawyer to ask my questions. Here we have a great resource for geeks and comic book fans that not only answers those questions, but does so in a way that you can learn a lot about the legal system. In short, it's an excellent book that helped me learn quite a bit. I highly recommend it.

Tuesday, October 30, 2012

Advice for Star Wars 7

Normally I don't pay attention to business news. I've got no mind for economics and unless it directly or indirectly impacts me, I'll only skim the business section of Google News. For example, when I see news about publishing companies merging, I'll see who bought who and maybe read analyses of what that might do for me. But then I forget about it a short time later.

But today's news? Well, that got my attention. It's not every day that you see Disney spend $4 billion to purchase Lucasfilm. That means that any future Star Wars projects will come with mouse ears attached.

In some ways, this shouldn't surprise us. At least, it didn't totally surprise me. Not the price tag, certainly. George Lucas has created quite the little empire for himself. And the fact that Disney did the buying doesn't surprise me much either. If you've been to Epcot Center recently, you've seen the theme rides and the dance parties that feature Darth Vader boogie-ing down and accepting the fealty of little girls. So there was a pre-existing relationship there. Given the fact that Disney also has bought Marvel, and that leads to some interesting possibilities in the future. Marvel vs. Star Wars fighting games, anyone? Or maybe Darth Vader and Wolverine will cameo in Epic Mickey 3.

But what caught my eye was the little factoid in there that "Star Wars 7," whatever that will be, is targeted to be released in 2015.

To quote one Dr. Sam Beckett, "Oh, boy." Or, perhaps a bit more appropriate, "I've got a bad feeling about this."

My initial reaction was one of revulsion. Yes, Episode III finally, sort of got it right, but that's only because the bar had been set so low. George Lucas lost his ways, seduced by the dark side of digital effects, focusing on that over and above such mundane details as, oh, I don't know, storytelling, characterization, and so on. And while I've heard that the Clone Wars animated series is pretty good, I've been glad that we wouldn't see any further assaults on my childhood memories.

But then I noticed this little nugget in the middle of the stories, a quote from George Lucas himself:

“For the past 35 years, one of my greatest pleasures has been to see Star Wars passed from one generation to the next,” said George Lucas, Chairman and Chief Executive Officer of Lucasfilm. “It’s now time for me to pass Star Wars on to a new generation of filmmakers.”

So wait . . . this new movie would be one without George Lucas in direct control?

Interesting.

Further reading reveals that Lucas has turned over control of Star Wars to a lady named Kathleen Kennedy, and that he's shared ideas and plotlines and all that with her, that he will serve as a creative consultant for the future movies (yes, there will be more than just #7).

Initial feeling of worry returning.

Now I've been a Star Wars fan for a long time. Some of my earliest memories are of watching the original trilogy with my family to the point that we had them all memorized. I've read many of the novels. And I've played a lot of the videogames too. I've been a loyal connoisseur for decades now. And even though I doubt that Ms. Kennedy will ever stumble across this, my humble corner of the Interwebz, I do have some advice for her about what to do with Star Wars 7, which I'll share with you now:

1) Don't make them sequels. Or, to be more specific, respect the Extended Universe. A lot of authors have spent a lot of time telling the story where Return of the Jedi left off. The Empire fell and rose again. Memorable characters, such as Talon Karrde, Corran Horn, and Mara Jade, have trod the galactic stage and left an indelible imprint on it. And the main characters have been through a lot too. They've gotten married, had kids, lost kids and spouses. One of them even died (although I won't say which one). While I know that the books and such aren't probably "official canon," it would be a shame to slash-and-burn all of it. So if Star Wars 7 is indeed a sequel, set it in the far future. Avoid the Skywalker clan and their related associates. Tell us a new story set in the same universe and leave the EU to the fans.

2) Bring in some ringers. It's great that Lucas has given you his thoughts and ideas and I would never suggest you jettison them. But maybe hire in some folks with proven track records when it comes to telling Star Wars stories. Have Timothy Zahn take a pass at Lucas's ideas. Hire Michael Stackpole to flesh out the stories. Bring Drew Karpyshyn in, especially if these movies are set in the Old Republic period. There are plenty of talented writers who know this universe who could be used to help get this project off the ground and make it a classic. Speaking of which . . .

3) Don't confuse flash for substance. I think one of the chief problems with the prequels was the fact that so much of it was focused on the visual effects. Don't get me wrong, the effects were awesome and made the movies a lot of fun. But it was clear that Lucas's focus was on the sizzle, not the steak. The story is full of plotholes (which are fun to exploit at times), the characters are lackluster, and overall its disappointing. Make sure that whoever writes the script an craft a good story. Make sure whoever sits in the director's chair can say more than just, "Faster, more intense." Definitely don't get rid of the visual effects. Just use them to support the story, not overwhelm it.

4) Whatever you do . . . don't include Gungans, midichlorians, or characters from the original trilogy as children. That's just a bad idea all around.

But hey, what do I know? It's just a thought.

Wednesday, October 24, 2012

The New Recruit

Is it any wonder than I'm a Jill Williamson fan? It's not just because Jill is a good friend and my "agent sibling" (seeing as we're both represented by the awesome Amanda Luedeke). No, I'm a fan because of her writing. She's done it once again with The New Recruit.

Spencer Garmond is just an ordinary teenager. He loves playing basketball and yeah, he gets in trouble from time to time. But one of those times leads him to a difficult choice: he can either go to a private military school or he can join the Mission League, some sort of special service organization run by Christians (or "churchers," as Spencer refers to them). If he goes to the military school, that would mean the end of his budding basketball career. So he decides to check out the churcher's mission whatever.

That's when he learns that this is no ordinary mission trip. The Mission League is so much more. Soon Spencer finds himself heading to Russia, where he'll find himself caught up in the middle of an adventure that could completely destroy the Mission League from within. Will Spencer finally start to accept his calling? Or will the League's enemies finally bring it down?

I really enjoyed this book. It's not just because I received a free copy to review (which I did, but I bought a copy anyway. More on this in a bit). And it's not just because Jill is my friend. It's because once again, Jill created a rich world with some memorable characters. Spencer is a deep character with some very obvious flaws, and that's good. He's by no means perfect. I particularly like his discomfort at the churchers' behavior. That rang very true to me. I also appreciated the shorter chapters, which kept me reading the entire time and didn't let me off the hook.

My one complaint, and it's a minor one, is the sheer number of characters. A few of them blended together after a while and I couldn't keep them straight. But they were minor players in the overall story, so it wasn't an issue all that often.

At any rate, this is a great new book and you should definitely check it out. And I can help you there.

As I mentioned earlier, I received a free copy of this a few weeks back. Well, that was after I bought a copy at the ACFW National Conference. I'm not big on having doubles on my bookshelf, so let's give away one of them. If you comment below with your e-mail address disguised (such as email (at) domain (dot) com, y'know?), I'll pick a random reader out of a hat a week from now (that's right, on Halloween).

Tuesday, October 02, 2012

Wool Omnibus

I love a great success story, and Wool - Omnibus Edition is certainly that.

Imagine a future where the only human survivors live inside an underground silo. There's a definite hierarchy to the silo. There's the up top and the down deep. There are rules and law, the chief of which is this: don't talk about the outside world. That kind of talk gets you sent out for a "cleaning." But what happens when a young woman from the down deep to be the silo's new sheriff. This upsets the status quo and threatens to tip the silo into absolute chaos.

I can't say much more than that due to spoilers and all that, but this was a fantastic read. Hugh Howey did a fantastic job of creating a believable world with some great characters. I felt completely immersed in the silo's world and there were times I wished I could join the story to help out. I had to keep reading.

What makes this even greater is that Howey is a publishing revolution success story. Howey published the first story in this omnibus as a stand alone short story via Amazon's Kindle Direct Publishing service. It became so popular that he wrote more stories and he's even sold the movie rights.

So if you want a good sci-fi, dystopian read, be sure to check this one out.

Wednesday, September 19, 2012

Save the Date

Every now and then, I like to take a stroll outside of my geeky genres and read something a little different. So a few weeks ago, I decided to dip my toe into the waters of romance.

Don’t look at me like that.

Actually, I’ve wanted to read something by Jenny B. Jones for a while now. Jones usually writes Christian Young Adult books and I’ve heard that she’s hilarious (I’ve never had the pleasure of meeting her officially, although I have seen her in the halls of my writing conferences). When I heard that she decided to publish an “adult” novel, I figured it might be worth checking out. Hence why I bought Save the Date.

Lucy is a geeky girl who runs a non-profit organization that helps rescue young women who are too old for the foster care system but too young to make it on their own. Alex Sinclair, a former professional quarterback and heir to a hotel fortune, is running for the Senate. You wouldn’t think the two of them would ever need the other’s help, but they do.

See, Lucy’s non-profit is running out of money and she’s in danger of losing her facilities. Alex is drowning in the polls and needs something to boost his numbers. So when the two of them run into each other at a gala hosted by Alex’s parents and the press jump to the conclusion that they’re dating, a revelation that helps Alex’s campaign, Alex hatches a plan: if Lucy will pretend to be his fiancĂ© up through the election, he’ll pay her the money she needs to keep her charity going.

Simple, right? Not exactly. There’s the fact that Lucy and Alex have a painful past together, even if he doesn’t remember it. There’s also the fact that Lucy’s ex-boyfriend has come back to town and is wanting to get back together. And both Lucy and Alex have problems that they’d rather not face.

This was an enjoyable read, a lot of fun. Like I said, it’s a bit outside of my wheelhouse, so to speak, but I still liked it enough to polish it off in a day or two. The faith content is strong and the writing is fun. The fact that Lucy is a geek particularly sealed the deal for me. So if you're a fan of the romantic genre, this might be one for you.

Friday, September 14, 2012

FTL: Faster than Light

The bane of my existence right now is Kickstarter. I actually have to stay off of it most days because I know that I'm going to find something that I like and I'll want to dump some money into supporting it. My particular weaknesses are the games, both board and computer. I want to get them all!

Case in point: FTL: Faster than Light. On the surface, it looks like a throwback to "simpler times." The graphics aren't complex. Neither is the sound. And yet, this game is a lot of addicting fun.

You are in charge of a starship, one with a vital mission. The Rebels are going to wipe out your government, but you have the battle plans that reveal the weakness of their massive flagship. You must get your plucky crew across a randomly generated galaxy to do battle with the flagship. While you go, you collect scrap, missiles, drone parts, and fuel. You upgrade your ship with new systems and weapons. You pick up Sounds easy? Guess again.

This game is hard. Extremely hard. As in, I've played this game dozens of times and only beaten it three or four times, and each time, it's surprised me. The enemy gets progressively harder, but the final boss is a beast. Worse, there's no way to save the game to go back if you make a mistake. There is a brutal learning curve to this game and it is still a blast. Ever since I backed FTL on Kickstarter, I've had access to the beta. The additional features that have snuck into the game as they worked on it has made it awesome. This is a great game and a challenging one to boot. It's worth the investment.

Wednesday, August 22, 2012

Let's Cast Failstate!

One of the funny things that's happened since Failstate was published was that a rumor somehow got started that I had a movie deal in the works. I'm not sure how that got started, but several people (who don't know each other) have asked me about it. I suspect it might have something to do with the starred review that Publishers Weekly gave me back when the novel first released. The last lines of that review were:
Otte has a TV show full of sequel possibilities; here’s hoping.
And maybe that got twisted into "John has a movie deal in the works?" I don't know. That'd be awesome, but it hasn't happened yet. Hollywood, if you want to talk movie or TV deal, call me! Or my agent, actually.

Anyway. Earlier today, I spotted a blog post by author Rachel Coker (of whom I am intensely jealous; she was first published when she was 16. Although, come to think of it, the stuff that I was writing when I was 16 was garbage, so it's probably better I waited an additional 20 years to figure out what I was doing). Rachel mused about who she would cast in a movie adaptation of her book. I haven't read Interrupted yet (although it is in one of my to-be-read baskets and high on the list), so I can't comment on her choices one way or the other. But that got me to thinking.

What if, by some bizarre stroke of divine intervention, someone did want to make a big budget version of Failstate? Who would I want to play the roles?

And the more I thought about it, the more I realized . . . I have no idea.

Seriously. I suppose part of the problem is that I'm not up on teenage actors (or actors who can pass for teenagers). Or it could be a fault of my writing craft.

But still, it's fun to dream, so I'm inviting you to dream with me. Let's cast a hypothetical Failstate movie! If you've read the books, who do you think should play the characters?

Before we get started, let's establish one quick rule: the people you cast have to be actors who can play the role today. No "time machine" casting. As awesome as it would be to go back in time so we can cast a teenage Nathan Fillion as Failstate, the laws of physics blah blah blah.

So who do you see in those roles? Let me know!

Thursday, August 09, 2012

Partials

This is one of those books that jumped off a bookstore shelf at me and screamed, "READ ME!" I have no idea why. I think I liked the cover. Huh. Anyway, I just finished reading Partials by Dan Wells.

At some point in the near future, humanity is teetering on the edge of extinction. Most of humanity was wiped out by a group of synthetic lifeforms called Partials when those artificial people rebelled against their human masters. Then, to make matters worse, the Partials unleashed the RM virus, an epidemic that wiped out the majority of the human survivors. Only a couple thousand are left, bunkered down on Long Island, trying desperately to survive. That's not easy, though. Every time the human survivors produce a new baby, the baby catches RM immediately and dies. The youngest human being just turned 14 and things are turning desperate. The Senate has lowered the mandatory pregnancy age to 18 and a lot of people are not happy about it.

This is the world that Kira finds herself in. She's about to turn 16 and she's training to be a medic in a hospital. When she learns that her "big sister" is pregnant, Kira vows to find a cure to the RM virus. And she strikes upon a wild idea: why not see how the Partials deal with the virus? This leads Kira and her friends on a desperate hunt to not only capture one of humanity's avowed enemies, but see if they can find a cure in record time. But Kira has to be careful, because she might learn more than she wanted.

This was a pretty good book. I thoroughly enjoyed reading it. I found it interesting the way Wells described humanity's attempt to survive in a nearly abandoned part of what was New York City. For me, the most fascinating part was another of Kira's "sisters," Xochi, who was the music freak. She had gathered baskets full of MP3 players and had named them after the people who had monogrammed their names on them.

In some ways, the plot was a bit predictable. I had two of the twists pegged before they came. But that didn't diminish my enjoyment of this book. There appears to be a sequel in the works, and I, for one, can't wait to see where the adventure goes next.

Monday, August 06, 2012

Fuse of Armageddon

Fuse of Armageddon by Sigmund Brouwer and Hank Hanegraaff left me feeling a bit conflicted.

Quinn Mulvaney is a private negotiator in Israel. He handles kidnappings and hostage situations for insurance companies. But then, he's caught up in a massive plot. A Palestinian terrorist has kidnapped a wealthy American televangelist, one who has long preached that America must support Israel, no matter what. Quinn is asked to negotiate with the terrorist, even though he has strong feelings about the man's fate. But by doing so, Quinn finds himself in the middle of a far larger plot, one that could embroil the entire world in a gigantic holy war. For powerful men are using the hostage situation to fulfill what they think are God's prophecies. Can Quinn stop the plot? Or will this whole situation kill him?

I really, really wanted to like this book. I really did. But in the end, it left me kind of flat. The characters are mostly unlikeable, including the main ones. The plot is a bit too convoluted, with schemes followed by counterplots and even more counterplots and even more counterplots, so many that the whole story seemed to collapse under their collective weight. And the whole thing is preachy. Oh my goodness, is it preachy. It bludgeons us over the head with the blunt end of its premise.

And yet, for all of its flaws, I think this is a book that should be read and have a far wider audience, simply because its message is so important. Fuse of Armageddon makes the important point that theology matters and can have devastating real world implications. In particular, Brouwer and Hanegraaff attempt to show the impact that dispensational premillennialism has had and can have on the Middle East, particularly the conflict between Israel and Palestine.

I've actually been talking about this a lot over at Speculative Faith. If you want to get caught up on the discussion, you can watch the video playlist. In short, I'm not a fan of dispensational premillennialism. I'm a strict and ardent amillennialist. And this book helps explain why I take it so seriously. End times theology can have a major impact on the way we view the world today and interact with it. That's why I think more people should read this book, if for no other reason than to think through some of the messier implications of what they could or do believe.

Saturday, August 04, 2012

What Can Videogames Teach Us About Backstory?

So earlier this week, I was a presenter at the NextGen Writer's Conference, an on-line conference for teenage writers. It was an absolute blast! Rather than just write a post, though, I decided to go all high-tech and do a video. And here it is:



This won't be the last videogame/writing related video you'll see from me, though. I have a few more ideas and, at future conferences, I'll be presenting more of them. And I'll always be sure to share in this little corner of the Web as well.

Tuesday, July 31, 2012

The Memory Eater

In the interest of fairness, I helped write this book, so my review might be a little biased. But I finally got to read The Memory Eater, which was edited by Matthew Hance.

What if there was a device that could wipe out your memories? What would you want erased? What kind of havoc could the memory eater cause? Or are there instances where destroying memories would be helpful? Is it worth the risk? Would there be errors?

Fun premise, right? That's why I submitted my story, Satisfaction Guaranteed, to this anthology. After it was accepted, I was curious to see how other authors would approach the same subject.

And these are good stories. I liked some more than other, but that's only natural. I think my favorite, when it's all said and done, is Souvenirs from Another Life by Lauren C. Teffeau.

So if you've got some money, go ahead and get this one too. And enjoy some truly memorable stories.

Wednesday, July 25, 2012

Of Limited Loyalty

Michael Stackpole has always been one of my favorite authors to read. I "discovered" him because of his Star Wars novels, but I've come to enjoy his independent projects just as much, if not more so. That's certainly the case of Of Limited Loyalty, the sequel to At the Queen's Command.

In an alternate history, where magick exists, the colonies of Mystria have a new threat within them. Ian Rathfield has been sent by the Queen to investigate the rumors that a group of colonists have left the Crown's territories and have created a settlement called Postsylvania. Rathfield's job is to bring those errant colonists to heel. Prince Vlad, the Governor-General of the Mystrian colonies, sends Owen Strake, Nathaniel Woods, and Kamiskwa with Rathfield to guide him.

Things go off the rails for the expedition for several reasons. First of all, the Postsylvania colony is using forbidden magick, making them heretics. Not only that, but apparently the folks of Postsylvania have awoken an ancient threat, one that will not tolerate the Mystrian colonies.

But it's not just the threat to the west that has our heroes worried. Prince Vlad is being put under pressure by the grasping Bishop Bumble, who suspects the prince of meddling in forbidden powers. And Owen Strake is having trouble with his wife, Catherine, who doesn't want to live in the colonies but would rather be home in Norisle.

All of this pales, though, when that ancient evil stirs and threatens to destroy everything.

I really enjoyed this book. Stackpole's alternate version of the American colonies is really cool. When I read the first book, I wished that Stackpole would explore the relationship between magick users and the Church a bit more and I got what I asked for. There's an intriguing conspiracy brewing in this world that I can't wait to see more fully developed in the next book.

My only gripe (if you can call it that) is the almost anticlimactic nature of the final confrontation with the aforementioned ancient evil. I suspected that they would be the main baddies, so to speak, for this story and that they would become a permanent part of the story. But it doesn't feel like that at the end. I could be wrong, and I'm really not complaining. This was a good read and a lot of fun.

But I do have to say that I feel sorry for Owen Strake. I'm really hoping things get resolved for him soon.

Saturday, July 21, 2012

The Dark Knight Rises

Let's start right off the bat (pun not intended) by saying that this post is not about what happened in Aurora. That is an unspeakable and, in some ways, unexplainable tragedy. It's never wise to start pointing fingers and assigning blame so quickly (as some people have felt the need to do). I suspect that the shooter's motivation is a lot more complex than a simple, one-word answer, such as "guns" or "Hollywood" or whatever. For those of us on the outside looking in, the best thing we can do is offer support to those in need and join the ancient prayer of "Kyrie, eleison." Lord, have mercy.

With that out of the way, let's talk about The Dark Knight Rises.

I went to see it Thursday night as part of a movie marathon. I got to the theater at 6:00 so I could watch Batman Begins and The Dark Knight before the final movie kicked off at 12:01 am. As much as I'm paying for that now (I got to bed at 3:30; not a wise choice), I think that helped keep the other two movies fresh in my mind.

So what's the plot of this one? Well, it's several years after the events of The Dark Knight. Inspired by the legend of Harvey Dent (and blissfully kept in the dark about the monster he eventually became), the citizens of Gotham City have cleaned up their act. Crime is down, people are feeling more prosperous, and everything is coming up roses. For the most part. Sure, there are still the poor and downtrodden, but they're mostly out of sight.

Not everything has gone well for Bruce Wayne, however. He's become something of a recluse, hiding in the rebuilt Wayne Manor, his body slowly falling apart from his time as a vigilante. It would take something major for him to rejoin society and don the cape and cowl once again.

That something is Bane, a terrorist with a very odd mask. Bane is the leader of a mercenary group, one that is suicidally loyal to him. He comes to Gotham armed with a complex plan with a simple goal: level the playing field for everyone. And then kill everyone.

Thrown into the mix is a cat burglar named Selina Kyle and you've got a great movie, one that kept my attention all the way through.

Were there bad parts? Yeah, a few. I wasn't entirely enamored with Bane and his headgear. It wasn't just the fact that he sounded like he had a Darth Vader noise machine wired in there. Tom Hardy's choice of accent (whatever it was) threw me off for a while and there were times when his voice was hard to understand. And while I get Christopher Nolan's decision to not mention the Joker out of respect for Heath Ledger, that silence didn't fit the story all that well. That's my grubby little opinion, but there you go.

But there were plenty of surprises in the movie. I, for one, was pleasantly surprised by Anne Hathaway. I seem to have something of a blind spot for her. When I heard she was playing Selina Kyle, my immediate reaction was, "Really? The girl from The Princess Diaries?" But I think Hathaway did an excellent job. She captured Selina Kyle's playfulness, cleverness, and ferocity in a way that worked.

There were also two surprise twists that I didn't see coming, although I should have seen the first one. I mean, I know the Batman mythos fairly well. I should have seen through the smokescreen that Nolan set up around some of the characters to realize what was truly going on. But instead, I swallowed the deception and chalked it up to "artistic license," which made the reveal a lot more fun. The second twist, I didn't see it coming and laughed out loud when it happened. If you've seen the movie, it's the one that happened right before the ending.

And can I say how much I loved Joseph Gordon-Levitt in this too? Simply awesome.

So I'd say that this is a film worth watching, a great non-superhero superhero flick that really wrapped up Nolan's trilogy well. I've read rumors that Warner Brothers is already starting plans for a Batman reboot. I would not want to work on that movie, because Nolan has left some mighty huge shoes to fill.

Tuesday, July 03, 2012

The Amazing Spider-Man

You know, I used to do more on this blog than just review books and whine report on my writing endeavors. I used to talk about movies and video games and occasionally music. I have no idea why I got away from that. It's not like I stopped going to the movies or stopped playing video games. I'm thinking I should rectify that. Starting tonight. Which is appropriate since I just got back from seeing The Amazing Spider-Man.

Okay, honestly, do I have to do a plot summary? We've been there, done that. Radioactive spider, new found powers, yadda yadda yadda. The origin story is pretty much the same as the last go 'round with Tobey Maguire. As a matter of fact, I was one of the people who originally shook my head in dismay over the fact that Hollywood was rebooting the franchise so shortly after unleashing the steaming pile that was Spider-Man 3 upon the world. But then I started hearing good things about it. And, I have to admit, I'm a sucker for superheroes. Go figure.

So let's talk about what's different in this movie. We see Peter Parker's parents. They've disappeared for some reason, leaving him with his Uncle Ben and Aunt May (wonderfully played by Martin Sheen and Sally Field). Mary Jane Watson is nowhere to be seen. Instead, it's Gwen Stacy (played by Emma Stone) who causes our friendly neighborhood wall-crawler's heart to go pitter pat.

And Andrew Garfield as Spider-Man? Wow. Awesome. You can tell he gets the character.

Anyway, the plot centers around Dr. Curt Connors, a scientist at Os Corp who dreams of fixing people through interspecies genetic engineering. For example, using lizard DNA on patients who have lost limbs. Sort of like how Connors is missing an arm.

So, yeah, in some ways, the plot is a little predictable, especially if you're familiar with the characters that inhabit Spidey's world. But at the same time, the filmmakers took some great liberties with the origin story. Some things were missing (such as J. Jonah Jameson, but after the way JJ was played J. K. Simmons, no way I'd want to follow in his Hitler 'stache). The story was simply great.

The acting was awesome as well. I'd take Emma Stone's Gwen Stacy over Kirsten Dunst's MJ any day . . .

. . . that sounded a lot better in my head. I mean Emma Stone did a fantastic job as Gwen.

And may I say, this movie has almost convinced me that 3D movies are okay. I normally don't like springing for glasses for a movie that doesn't quite need 3D. Watching Spidey swing around New York in 3D is worth the extra buck or two.

All in all, this was a great movie. I'm not sure it edged out The Avengers as my favorite superhero movie to date, but it came pretty close to doing so.

I'll be throwing out more reviews as the weeks go by. But for now, go check out this movie. It's worth it.

Friday, June 29, 2012

Wordcount . . .

. . . never mind. I won't call it a "Wordcount Wednesday" two days late.

So I haven't added any new words just yet. I spent the last week or so reading Failstate #2 (I still don't have any idea what I want to call this thing). Thankfully, I've come to realize it's not the mess I thought it was. There's a fun story in there after all. I'm actually quite relieved to learn that.

I still think some stuff is missing, but I'll get to that in a moment.

Those of you who have been reading my blog for a while know that, when I first wrote Failstate, I hit kind of an interesting snag. For some reason, I wrote that story in such a way that the plot would only have been possible if a week had eight days in it. In this blog post, I detailed how I created a calendar and, using Post-It notes, figured out the chronology.

This time around, I realized that I didn't have an eight day week to worry about. Instead, a lot of the events happened in what you might call a temporal vacuum. With very few exceptions, I didn't ground the scenes into a discernable timeline. Days were just scattered through the story and that really didn't work. So, once again, I got out the calendar sheets and started to work.

Here's before:


If you look at that mass in the top page, that's part of what I'm talking about. A lot of scenes with no discernible anchor points. I basically wrote down chapter numbers and a brief, one or two word description of the action for reference. Like last time, I wound up with an "orphaned" chapter, one that needs to be slipped in somewhere.

After putting together the mess, I sat down and took a closer look at what I had. I tried to keep in mind some of the "missing pieces" that I noticed, stuff that needed to be put into the story to make it flow a little better. This is how the calendar looks now:



So there we have it. The purple Post-Its represent new scenes or chapters that have to be written. So all in all, not too bad.

There were a lot of victims in the process, though. I cut several scenes that just didn't do much of anything, including about 7,500 words in one gigantic axing.

The next step is to start work on the notes I've taken and see how this all gets stitched together. Onward and upward!

Thursday, June 21, 2012

Wordcount Wednesday

Or Thursday, I guess. Technically. If you want to be technical.

I want to be asleep right now. I should have gone to bed a while ago, but I didn't. And I'm glad I didn't. I'll pay for it in the morning, but I am pleased to announce:

Failstate #2 is in the can.

I just put the final words to the page. The epilogue is done. And this monster weighs in at 118,247 words. For those playing at home, Failstate is about 100,000 words. So the sequel is going to need to slim and trim down a bit.

But not now. Now I plan to go to bed.

Saturday, June 09, 2012

Sapphique

After reading Incarceron by Catherine Fisher, I was really looking forward to reading Sapphique. With its living prison, memorable characters, and strange, other-wordly vibe, I figured this was going to be a wild ride. And it was.

I just don't have a clue as to what actually happened here.

The story picks up where the first book left off. Finn has escaped from the living prison, Incarceron, only to find himself trapped in a different prison. Is he the lost Prince Giles, like Claudia, the daughter of Incarceron's Warden, believes? Could he really be the heir to the throne? And what about Finn's friends, Keiro and Attia, still trapped inside the Prison? What about the political machinations of Queen Sia's court, trapped forever in an illusion of a time long gone. And what of Incarceron itself? What strange plot is it hatching?

I finished reading this book a few days ago and I'm still stumped by it. I have a feeling that "something significant" happened in this book, that Fisher is trying to say something deep about humanity and junk, but for the life of me, I can't decode it. It was an okay book, I suppose, but everything got started so suddenly that I was left wondering if I missed something.

All in all, this book didn't recapture the magic of the first one. It was a fun read, but nothing memorable.

Wednesday, June 06, 2012

Wordcount Wednesday

Okay, I am in so much trouble right now.

Let me explain why. As of tonight, Failstate #2 is at 90,579 words. That means I added 11,840 words this week. That's awesome!

Except I'm supposed to be wrapping this up. And I'm pretty sure I'm nowhere near the end yet.

Buckle up, folks. This next week is going to interesting.