Slashing a Fat Synopsis

Well, I finished my first draft of the synopsis for Fire On Mist Creek.

3,642 words.

Now, opinions differ on how long a novel synopsis should be. (In my opinion, I should be rich enough to hire someone else to write my synopsis and not worry about how long a synopsis should be.) The general consensus in the writing community is that a synopsis should be kept strictly between two thousand words and, oh, fifty words long. But the shorter the better; just like opera, or congressional term limits, or that little guy from Game of Thrones.

"Did you just call me a LITTLE GUY?"


 So I have some cutting to do, and with an ax, not a scalpel. There's a certain irony in cutting a novel down to something you then have to cut down. Meanwhile, I've identified a possible publisher for the book, but according to their publishing guidelines my novel is four hundred words ... too long. (Which is not something I'm remotely worried about for the moment.)

Later I'll probably have to boil my synopsis down into a back page blurb. There'll be significant shrinkage.


This is so much easier than writing a synopsis.

The Writer's LIfe: judging and revising and young authors

I spent some time last week judging 4-H writing projects. As usual, I marveled at how good  the entries were ... many of them much better than I was at the same age. It's great to know there are still young writers and readers out there. It's also great to know my own childhood writing has disappeared.

Then I dove back into revising Fire On Mist Creek, which I wrote last fall and edited in early winter. Revision isn't all that much fun to me, so I made myself a promise: Once I get this manuscript done ... I can start work on another story. The most fun parts for me are brainstorming the story, writing the first draft, and those little edits later on, when the story's mostly done and I can relax a little. (Maybe I should have promised myself cake.)

Major revisions of the rough draft, on the other hand--pulling stuff out, moving it around, changing whole scenes and so on--not so much fun. It beats self-promotion, though.

You know what else it beats? Writing a synopsis. I hate writing synopsis ...um, synopsi ... um, synopsises. Unfortunately, for the purposes of an upcoming submission I've paused the revision, and gone over to finish the synopsis, first.

Still a better job than assembling axles at a factory, or working at a bee moth larvea farm. Trust me on that.



A Few Storm Photos, and Maybe Even a Video

It was a tense day Friday, with the same severe storms approaching us that hit areas in Iowa with damaging tornadoes. Here in Noble County we ended up under a tornado watch and then a thunderstorm warning, and the leading edge looked pretty darned bad on radar.

And there were some funnel cloud sightings and at least one touchdown filmed ... but not in Noble County. Up here it eased somewhat before it hit, with most of the really bad stuff ending up to the south of us. The same system went on to produce tornado warnings in several other states to the south and east. We got some pretty heavy lightning, along with wind and hard rain, but only a few reports of damage. So the photos I took--mostly from my back porch--made it look worse than it was.

There's also a video at the end ... if I downloaded it properly, because when it comes to video online I basically have no idea what I'm doing.

I should use days like this to work on a new story in the Storm Chaser series. Like ... a storm muse.









Wave your cowboy hat at my better half

A South Bend radio station has done a profile of Pokagon State Park in northeast Indiana:

http://www.wndu.com/content/news/One-Tank-Trips-Pokagon-State-Park-488533701.html

Part of their profile includes the Pokagon Saddle Barn, where my wife works. She's only on screen briefly: She's the woman in the cowboy hat saying "My name is Emily, but if you forget you can call me Horse Lady". I think I'm going to call her Horse Lady from now on!

In this photo (which I took while trying not to fall of a horse myself) Horse Lady is in front, looking around for the coyote that just crossed the trail.

Print Book or Audio Book? Or both?

Last year I did a review of Neil Gaiman's American Gods:

https://markrhunter.blogspot.com/2017/07/book-review-american-gods-by-neil-gaiman.html

 Emily and I listened to it on audiobook while driving back and forth to Missouri and other places over the summer. It was only the second fiction audiobook I ever listened to, the first being Red Storm Rising by Tom Clancy. I read that print book first, and was disappointed in the audio version, which was abridged and in my opinion not dramatized well. (However, I've never been disappointed in non-fiction audiobooks.)

American Gods was just a reading, rather than a dramatization; maybe that's what did it for me, but I loved it. Then the TV series based on the book came out, and got my interest enough to try reading the book myself. The audiobook narrator did such an awesome job that it seemed the print version would be weaker.

It wasn't. It seems there's no version of American Gods that isn't awesome, including the TV show.

There are places for both, of course--for instance, my wife really hates it when I read and drive. What's your preference, if you have one? Audio or print? And maybe I should tackle the graphic novel next.

Maybe someday we'll even get to "see" some of my books on audio.






The two versions do seem oddly similar, somehow.

50 Authors from 50 States: Jennifer Wilck Writes of New Jersey

50 Authors from 50 States: Jennifer Wilck Writes of New Jersey: Writers are often taught to “write what we know.” While I’ve usually taken that advice, only recently did I start to set my books in New...

Speak of the Devil: Small Heroes And Big Stakes

Speak of the Devil: Small Heroes And Big Stakes: “Nothing can prepare you for what’s coming.” ~ Ava “Hiya, champ, how was school today?” ~ Hank Pym “Thanks to you, we had to r...

movie review: Ant-Man and the Wasp

Scott Lang is just a normal guy who used to be a superhero, until he broke the law and the law made him a deal: Two years of home detention, a few more on probation, and he's a free man. Oh, as long as he never again puts on that Ant-Man super suit. Now he's only days from getting his detention bracelet removed, so all he has to do is relax, play with his daughter, and he's home free.

I think we all know Scott's not free.

"So ... Ant-Man is also the giant guy? Does he have to change his name?"


Suddenly he's reunited with Dr. Hank Pym and his daughter Hope van Dyne, both still mad Scott used the suit they gave him to go fight the Avengers in Captain America: Civil War. It seems they've discovered a way to rescue someone they thought long lost, and they need Scott to do it. But in advancing their mission, the trio runs afoul of the Feds, mobsters, and a mysterious figure whose powers can be predicted from their name: Ghost.

Ant-Man and the Wasp is one of those projects--like most Marvel movies--that was only doable in recent years, when special effects finally caught up with the vision of movie makers and comic creators. Not that movies haven't managed without it before: check out The Incredible Shrinking Man, from 1957. But when modern effects are successfully balanced with story and character, the results can be spectacular.

Ant-Man and the Wasp manages that pretty well. We get giants menacing ships, quantum level adventures, and everything in between, including one in which a Pez dispenser is used as a weapon, and a big Hot Wheels product placement that fits into a fun and somewhat unusual chase scene. No matter how good they might have made anything else, I just don't see how they could have pulled this story off without modern effects.
"Wait a minute. I have wings and a stinger, and he gets first billing?"

Having said that, they do pretty well otherwise, too. A lot of that is thanks to a solid cast including Paul Rudd and Evangeline Lilly as the title characters, and Michael Douglas as Hank Pym. Look for Michael Pena having a lot of fun, Randall Park as a befuddled FBI agent, Hannah John-Kamen as one of the more tragic figures, and little Abby Ryder Fortson, who tended to steal her scenes through shear cuteness as Scott's daughter.

Do NOT stay for the two mid/after credit scenes. They change the tone of the whole movie from fun to depression, although they do fit the movie into the Marvel Universe.

Seeing Douglas, Laurence Fishburne, and Michelle Pfeiffer makes me wonder at how much more willing the big quality names in Hollywood are to do comic book movies, now. (Of course, Pfeiffer once visited the DC universe.) The wide net of fantasy/SF will probably always get snubbed by the Hollywood elite even as they're scooping cash out of the cows (not literally--ew); but the genre's being taken more seriously than when I was a kid.
"This scene feels a little drawn out."


My score:

Entertainment Value: 3 3/4 out of 4 M&M's. No ... thinking back on the scene with Michael Pena's character under truth serum, sent that up to a full four.

Oscar Potential: 2 1/2 out of 4 M&M's. There were some good performances here, not that the Academy would ever stoop to acknowledge them, but mostly there should be some consideration for effects.

Grand-twins!

A couple of weeks ago I posted three month old photos of my six-month-old granddaughter, because getting a post ready and actually posting it are two different things. It's only right that I do the same with the grand-twins. In other words, in a case of epic fail, this post has been in my draft folder for almost four months. These are also from my dad's 80th birthday party, which took place when people were praying for summer:

Brayden debates politics, or possibly football. Probably football.

"I was promised fudge. Where's the fudge?"

If there's one thing I've learned, it's that when you get a dozen kids in a room, they make three dozen kids worth of noise.

Speak of the Devil: A Day In The Life Of A Dog

Dogs make every day better. Unless they bite you, then not so much.



Speak of the Devil: A Day In The Life Of A Dog: It is time once again for the perspective of the dog and the cat, and as always, the dog gets the first say. 7:08 AM. Waking up at...

movie review: Jurassic World: Fallen Kingdom

I'm starting to think that someday the Pirates of the Caribbean Ride will break down, and the pirates will start eating the tourists. At least in a movie, where the idea of safe things going horribly wrong and killing lots of people has always been popular.

Life finds a way ... to kill other life.


In Jurassic World: Fallen Kingdom it's been a few years since the theme park Jurassic World suffered a catastrophic "pirates eating people" story, and the island of Isla Nublar has been abandoned ... by people.

(And now I'm thinking, how cool would a pirates vs. dinosaurs movie be? Get on that, SyFy.)

A dormant volcano on the island has become active, and former employee Claire Dearing (Bryce Dallas Howard) is involved in an effort to rescue the dinosaurs before it blows. The fact that there's a volcano there at all will come as a surprise to franchise viewers, although I'm told it's mentioned in the original book. Yeah, I read it--twenty years ago.

Why does Claire, who almost died in the last movie, want to save the animals? That's what Owen Grady (Chris Pratt, doing a great job of playing Chris Pratt) wants to know. She guilts him into going along with the reminder that his own pet raptor, which he raised from an egglet, is still there.

"Dude, somebody broke my lava lamp!"

The mission's financed by a rich old man (James Cromwell), who we discover was once a partner to the original Jurassic Park founder, John Hammond. Retcon, much? But the armed "guards" who go along with Claire and Owen have their own, much more sinister agenda. Rescue dinosaurs? Yes. But toward what end?

Jurassic World: Fallen Kingdom is much better than the original Jurassic World, which in my mind isn't saying much, but still suffers from being too dark and sometimes graphic. They haven't learned the lesson the master, Steven Spielberg, taught in the original Jurassic Park (not to mention Jaws): Often the scary stuff is much scarier when it happens off screen.

Still, the stuff that happens onscreen is pretty darned spectacular, especially in the first half of the movie when our heroes are fleeing just about everything: dinosaurs, bad guys, and exploding mountains. The movie makers chose practical effects when possible, especially with close contact with the dinosaurs. When that couldn't be done, modern digital effects have progressed so much that it really is getting hard to tell them apart ... and I watched the movie in 3D IMAX, thanks to a scheduling snafu.

In the second half the movie moves to a different location, in its own way just as neat, and at this point it's probably not a spoiler to say a lot of people die. The suspense was gripping, but the gore unnecessary and unwanted for the type of movie you should be able to take your kids to. Overall I liked the characters except for the bad guys, who were such cardboard cutouts that I kept confusing their names with the same tropes who died in earlier Jurassic Park pics. In addition, the plot was very much a repeat of the themes we've seen before, from greed and inhumanity to dire warnings of what happens when science outstrips reason. For that last we at least get Jeff Goldblum's Ian Malcolm, in what amounts to a glorified cameo.

I liked the new supporting characters played by Justice Smith and Daniella Pineda, and although it appears to have been her first major acting role, Isabella Sermon does a great job as this movie's kid-in-jeopardy.

"You scream so much better than the two boys from the last one."


My score:

Entertainment Value: 3 out of 4 M&Ms. Worth seeing, but it still pales in comparison to the original Jurassic Park. But then, what doesn't?

Oscar Potential: 2 out of 4 M&Ms. With the exception of some plot holes, nothing about the movie is bad; but other than the effects and cinematography, nothing about it is great, either.

Speak of the Devil: Impending Firework Disasters

Speak of the Devil: Impending Firework Disasters: "We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain ina...

How The First World War Led To American Independence

Four years ago I wrote my regular newspaper humor column about Independence Day history, which few people read because it was about history. Ironically, about two months later my regular newspaper column became history, but that's another story.
As I said in the opening to our book "Hoosier Hysterical", history would be a lot more fun if it was made ... well ... fun. So I had fun with this, which has been changed slightly because I'm four years older.


SLIGHTLY OFF THE MARK


            Ever since Christopher Columbus first landed in the New World and hid all the Viking artifacts, America has been a land of opportunity, independence, and smallpox.

            Eventually the British colonists decided to go off and form their own country. (Except for Canadians, who were just too polite to leave.) Since our schools don’t teach enough history these days (there’s so much more of it now), I thought I’d give you a quick timeline of how we, the people, went from tea to coffee:

            1756: The French and Indian War

            This was probably the first World War. No, seriously: Over here we just mention the French and Indians, but the rest of the world called it the Seven Years War. It spread all over the globe, like a viral YouTube video, but with more cannon fire and disease. Nations involved included Austria, England, France, Great Britain, Prussia, and Sweden. Oh, and the Indians.

            (Later on Prussia, not wanting to be confused with Russia, changed their name to Germany.)

            Why does this involve American Independence, which came decades later? Because it cost the British government so much to defeat their enemies (and the Indians) that they began taxing the colonists to help pay for it. And yet they didn’t allow the colonies to raise their own armies, and there was that whole taxation without representation thing.

            Oh, and one more thing: The whole world war began (well, mostly) because a young Virginia militia leader ambushed a French scouting party in the far west wilderness … near Pittsburgh. In later years, George Washington would be more careful to start battles after war was declared.

            1770: The Boston Massacre:

            No, it wasn’t a sporting event. It started when a group of colonists began throwing snowballs at a squad of British soldiers (In Boston. Sheesh.). That’s not so bad, is it? Then the colonists starting tossing sticks and stones, which, contrary to popular belief, can indeed break bones.

            This is a perfect example of why you shouldn’t throw stuff at people with guns. Five colonists died and the soldiers were arrested, but they were mostly acquitted thanks to the crafty defense by a young lawyer names John Adams.

            1773: The Boston Tea Party

            Tired of high taxes, an unresponsive government, and Earl Gray, colonists (In Boston—sheesh) dressed up as Indians, sneaked aboard ships (In the harbor—sheesh), and tossed 342 chests of tea into the water. In today’s dollars, they turned Boston harbor into the world’s biggest cup, with $750,000 worth of tea. They were led, of course, by the famous Boston patriot Folger “Starbuck” Maxwell.

            But why blame the Indians? They didn’t even drink tea.

            1774: The First Continental Congress

            They didn’t get much done. But in their defense, they were a Congress.

            1775: Patrick Henry stirs the pot

            With the grievances of the colonists ignored by a remote government—sort of like today, only without Facebook—a radical named Patrick Henry, upset because he had two first names and no last one, began making fiery speeches and resolutions.

            The truth is, Henry was kind of a deadbeat. Worse, a lawyer. But man, he sure could talk good, and his actions helped ignite the American Revolution. You’ve probably heard the last line of his big speech, which was “Give me liberty or give me death!” Luckily, he got liberty.

            1775: The Midnight Ride of Paul Revere.

            He rode through the countryside yelling, “The British are coming!”

            Sleepy residents yelled back, “Shut up, you fool! We are the British!”

            Then he got arrested, probably for violating the noise ordinance, and the ride was completed by William Dawes. Unfortunately for Dawes, the name “Paul Revere” sounded better in poetry.

            Also 1775 (busy year, there): The Battle of Lexington and Concord

            Revere had discovered the British were marching by sea, which slowed them down considerably because the horses didn’t swim well. That gave the Minutemen almost a full two minutes. It was plenty of time to gather in Lexington, to protect stores of arms and gunpowder, and Concord, to protect the grapes.

            1775 (saw that coming, didn’t you?): The Second Continental Congress

            Didn’t get much done. They made up for it in 1776, though.

            1775 or so: The Battle of Bunker Hill

            It was actually fought on Breeds Hill.

            177—wait for it—5: Patriots occupy Montreal, Canada

            Things were looking up, up there. And that’s the last time things looked up for the Revolutionaries in the north, who discovered Canadian hospitality didn’t extend to invasion.

            1776 (finally!) Egged on by the British, Cherokee Indians attack along the entire southern frontier

            They were still upset about the whole Tea Party fraud. Also, they were mad about getting named for a country on the other side of the world.

            June 7, 1776: Richard Henry Lee points out to the Continental Congress that they’ve been rebelling against the British for more than a year, and wouldn’t it be a good idea to actually declare themselves to be rebelling?

            June 11: Five Congressmen are appointed to draft a Declaration of Independence. The other four talk Thomas Jefferson into doing the writing, pointing out that he’s the only one who’s invented a portable desk to use.

            June 12-27: Jefferson writes a rough draft, only to receive a rejection letter from the committee.

July 1-4: The entire Congress rips apart the Declaration. (Not literally. Sheesh.) Jefferson quits writing and goes into politics.

July 2: Congress declares independence, just as the British fleet and army arrive to invade New York. Talk about timing. John Adams declares that July 2 will forever be celebrated as Independence Day.

July 4: Having already declared independence, Congress now adopts the Declaration of Independence, declaring something they’ve already declared. John Adams’ head explodes.

July 9: George Washington has the Declaration read before the American army. The soldiers nod politely and ask when they’re going to get paid.

There was much more to it, of course. In fact, you could say the American Revolution went on until the US Constitution was adopted in 1788, or even until we fought the second Revolutionary war in 1812, which might also be related to the real second World War.

Now, that’s a funny story.

Flags are cool. This one's at the Albion Fire Department, so it's also hot.

50 Authors from 50 States: Kay Phoenix: Hello from Las Vegas

50 Authors from 50 States: Kay Phoenix: Hello from Las Vegas: Let me tell you about my hometown. Las Vegas is more than just the stretch of road that slices down the center, holding world famous casin...