Showing posts with label 1787. Show all posts
Showing posts with label 1787. Show all posts

Saturday, July 4, 2015

Happy Independence Day


I hope everybody has a great day. One of my favorite July 4th celebrations was in 1976, the bicentennial. On a lark (or perhaps it was a inebriated neighborhood party), our street decided to enter a float in the bicentennial parade. We'd be competing against businesses and established organizations like the VFW and Shriners. The photo above shows my wife and son standing in front of our 1st Place float. (Hey, come on, it wasn't the Rose Parade.) Great memories. It drew the neighborhood together and we had a rowdy celebration with all the BBQ grills gathered in one back yard with kids running around everywhere.

If you want to read about an even older celebration, here is a description of the Independence Day gala in Philadelphia during the Constitutional Convention.  Before the snarky comments arrive, I wasn't actually at that celebration. At least, not physically. I did kinda visit when I wrote the piece.

Happy 4th of July. 




Wednesday, November 27, 2013

Historical Fiction—Doing it Right

I write historical fiction. I chose this genre because I enjoy the research and a historical novel can last forever. My first book was a nonfiction computer technology book that was obsolete before Wiley could get it on bookshelves. After that experience, I vowed never again to write a book that had a three nanosecond shelf life.

(The Shut Mouth Society is a contemporary thriller, but it still has a strong historical theme around Abraham Lincoln.)

I enjoy history. History is the big, ongoing story about how we developed as a world and as a nation. History is a gazillion stories about people who lead, hindered, or stood around as stuff happened. Every one of them has potential to be an interesting story.

In nonfiction, events should be factually accurate. Historical fiction, on the other hand, can go places where nonfiction dare not tread, but it should stay true to the tenor of events. Although historical fiction may be free of the rigors of documentation, it remains subject to the precepts of storytelling. That means historical fiction, like all fiction, must have a beginning, middle, and end and remain interesting throughout. That’s always a tough assignment, but especially difficult when telling about real events.

A few months ago, Chuck Sambuchino wrote “How to Write Historical Fiction: 7 Tips on Accuracy and Authenticity.” I agree with all seven, but would add an eighth: don’t let research interfere with telling the story. This is not original with me, of course. It is usually stated: don’t let your research show. It’s tempting to drop a factoid into a storyline. Interesting tidbits can add spice and intrigue. They may do just that, but unless the information moves the story forward, it should be cut. The prime directive of storytelling is to never take the reader out of the story. A fascinating sidebar does exactly that. In fact, the more fascinating, the more likely it will distract the reader away from the story. Good writers should cut everything extraneous to the storyline.

Adhering to an accurate timeline can also ruin a story. Tempest at Dawn is my novelization of the Constitutional Convention. In my first draft, I presented speeches in their proper historical order. My book was as disjoined as the actual convention. When someone gave a speech, it took days for an opponent to craft a rebuttal. All kinds of other subjects were discussed in between. By remaining faithful to the actual sequence of events, the critical elements of pacing and tension were lost. I decided to write a historical novel about the convention to bring life to the characters and intrigue. Exactness was defeating my purpose.

There are many top quality history books on the Constitutional Convention, so I decided to tell a rousing story that was true but not completely accurate. In my first major rewrite, I adjusted the convention sequence so speeches were immediately followed by rebuttals. Since I only included the controversial or emotional speeches, the book suddenly took on energy. I also discover that the adjusted timeline made alternate opinions more easily understood.

I resolved the ethical question with a Historical Note at the end of the book that explained I had reordered speeches for clarity. A simple solution to keep the story moving.

Sunday, October 20, 2013

"Mike Reads" reviews Tempest at Dawn

historical fiction
The "Mike Reads" blog has reviewed Tempest at Dawn. This is not exactly a New York Times book review, but I liked it because Mike took away from the book what I intended. I love writing Westerns and like the freedom to plot my own stories, but Tempest at Dawn was a five year labor of love. It was a huge responsibility to write about the founding fathers and such an important event in American history. I read or seriously scanned over 100 history books on the Constitutional Convention, and used at least 3 biographies for each of the major characters in the story. And yes, it was a story—a great story with great characters, intense conflict, and hopeful resolution.

Tempest at Dawn continues to be well received by readers and historians. At the time of this writing, and five years after publication, the Kindle version is still ranked #28 for books about the U.S. Constitution. 78 Amazon customers have reviewed the book for 4.5 stars, and 185 readers on Goodreads have given the book an average rating of 3.84.

I'll probably never again tackle a book as challenging as Tempest at Dawn, so it's gratifying that it still sells well and continues to receive attention from readers and reviewers. Thanks.