Donald J. Bingle February 2021 Newsletter |
|
|
The big news, of course, is that the Kickstarter for Flash Drive, the third book in my Dick Thornby Thriller series, continues. At this point, the project is over 75% funded (Thanks, everyone!) and there are still plenty of cool rewards and stretch goals left to come. Even if you've already backed the project, watch your updates as I plan to offer some great add-ons this week. And, if you don't want to fuss with Kickstarter, you can still preorder Flash Drive as an ebook on Amazon, BN.com, and Kobo, with a scheduled release date of March 1. Go HERE for all the links. Print books can't be preordered (except through the Kickstarter) right now. |
|
|
| | Excerpt from Flash Drive Prologue May 28, 1993 Thwack! Yet another grasshopper slammed into the glass, splattering yellow-green ichor. The windscreen wiper shoved the smashed insect’s shell and one still twitching hind leg into a curving wall of accumulated goo and viscera at the edge of the wiper’s reach. Archie stared ahead, peering through the messy windscreen into the black void of the Outback at night. He reckoned the multitude of twinkling stars were outnumbered by the flashes from his headlights glinting off insects fluttering in his path. Still, he held his semi to a constant hundred kilometers per hour on the lonely road seven hours east and north of Perth. Archie didn’t really care if he could see well. The road was reasonably straight and he knew better than to swerve if a ‘roo wandered into the big rig’s path. But he did need to stay awake. If his ride wandered off the road into open ground, there was no telling what might happen. He could hit a rock, slide into a dry wash, or get caught up by bushy vegetation or soft soil, with no one around to help get his tractor-trailer back on the straight and narrow. He turned up the classic rock on the cab’s tinny radio and cracked his side window enough for a stream of air, but not so wide as to suck in a torrent of hoppers. For the thousandth time, he wished he’d left the coast earlier so he’d be driving this small stretch from Menzies to Leonora in the arvo, when it was still light out. Sure, it would be warmer and the scenery was pretty damn boring when it could be seen, but at least he would be able to see something besides the flashes of insects in the black through a filter of insect guts. He squinted his eyes and peered into the empty. A moving slash of intense yellow-white light assaulted his eyes, forcing them fast shut. At the same instant, the radio music dissolved into a mass of crackling static. Archie instinctively hit the air brakes, while simultaneously downshifting as fast as his bulky transmission allowed, even though he had seen—could still see in the scene momentarily imprinted on the back of his retinas—there was nothing in the road ahead. Nor was there anything unusual in the flat salt expanses and mounds of near-constantly dry Lake Ballard to the left—an area which should have been enveloped in blackness this time of night. He opened his eyes, catching a moon-sized streak of yellow-orange light in the sky ahead to his right. At the same time, a long, deep, thunderous, pulsing roar assaulted his ears and rattled the fenders of his slowing rig, like a rolling earthquake triggered by a mining explosion a hundred times stronger than he’d ever experienced. Meteor strike? No, the bright streak was still airborne, moving across the distant landscape too slowly for a shooting star by his reckoning, about the speed of a plane. Unlike what he knew about meteors, it also maintained a constant altitude as it progressed, rather than arcing down from the sky and slamming into the ground. By the time Archie had come to a complete halt in the middle of the god-forsaken roadway and flipped on his hazards, the light had disappeared behind distant hills. But then a sudden horizon-to-horizon burst of blue-white light lasting several seconds emanated from behind the hills where the light had gone down. He sucked in a breath and waited. Moments later an overwhelming, low rumble thundered across the barren terrain, like a freight train and an earthquake and a gargantuan explosion all rolled into one. Where the blue-white light had flashed, a red, spherical—or, at least, hemispherical—dome pulsed above the horizon. He flicked off the staticky hiss of the radio, but let the truck idle as he got out to take a clearer—less bug-smeared—look at the strange phenomenon. Now the engine’s throaty chug was the only thing breaking the silence. Diesel was dear, but he let it run. He worried whatever this was might mess with the electrical system of his engine and he might not be able to start her up again. Nuke? He couldn’t see a mushroom cloud, but the glowing red ball was much dimmer than the flash, or even the streak of light which preceded it, so he couldn’t be sure. Besides, that didn’t make a lick of sense. There was nothing out here in the never never worth nuking. Route 49 wandered northwesterly past Leonora; the red orb throbbed to his north but seemed too far east to be near the road. Lake Darlot? No, farther east. Maybe down Bandya way. Nothing between the two fly-specks ‘cept maybe a few mines and even fewer sprawling sheep stations. Maybe that was the point. Nothing there. A perfect place to test nuclear weapons—maybe even nuclear missile systems. But that meant a military presence: facilities, equipment, personnel. And that meant large scale, convoy type movement: Bushmasters, G-Wagons, personnel carriers, and trucks of all sorts. And he hadn’t seen or heard of anything like that, not on the roads he traveled and not on the roads—or godforsaken excuses for roads—that the drivers he hung with at the diners and diesel pumps of local truck stops traveled. That meant black helicopters and all that crazy conspiracy shit which went with ‘em. He hadn’t gone troppo. He didn’t subscribe to such nonsense on a regular basis, but God knows, there was nothin’ regular ‘bout what was goin’ on in the lonely nowhere tonight. A jet crash? Maybe. Not a likely route, though, even for Qantas. There wasn’t really anything to do ... anything he could check or investigate ... not with the source of the lights beyond the horizon, but he couldn’t just drive on. Instead he waited, his rig’s hazard lights flashing behind him as he stood on the side of the road, watching something unknown pulse in the distance. An apocalyptic hazard light? Two hours later, the red orb suddenly winked off and he was alone in the dark with nothing but a strange story, a million stars, and a billion or three ‘hoppers, flies, and midges. He’d barely have enough diesel to make Leonora. What the hell was that? Want to find out what happens next? Go HERE for all the links. | | |
|
| | From the Writer's Desk: Prologue vs. Chapter One You probably noticed that my latest book doesn't start with Chapter One. It starts with a Prologue. In fact, all of my Dick Thornby spy thrillers (Net Impact, Wet Work, and Flash Drive) start with a prologue instead of going straight to the first chapter of the book. Two of my other books, Frame Shop and Greensword, start with prologues, while Forced Conversion does not. The Love-Haight Case Files, which in set up as four different cases, starts with a Preamble. (And, of course, I can't say anything about the book I ghost-wrote, lest it help you identify it.) Whether to use a prologue or not is the subject of much debate, most of it inane and ridiculous. People declare they can't stand books with prologues and will never read one. Others think they are essential in certain types of books. These strong opinions are, imho, the result of too many writers writing ... and too many readers rightfully disliking ... giant, expositional info-dumps of world-building before they get to the main action/narrative of the book. (The preamble to Love-Haight introduces the world--basically that magic has returned to San Francisco and caused supernatural other-than-human creatures to come into existence, who need legal representation--but it is super-short.) Long, expositional info-dumps are generally a bad way to start a book. Instead, you want to have something which will immediately draw the reader into the book. Lots of times people think that equates to an action scene where bullets (or spears or vehicles) are flying and people are dying, but that doesn't have to be the case. In fact, putting people in danger who the reader has no reason to care about isn't as compelling as some people assume. And being in the midst of of a battle with factions the reader doesn't yet know anything about can be confusing and off-putting. The beginning of a book should hook the reader. It can do that with action, but it can also do that with suspense, mystery, or sheer novelty. But most importantly, none of those things have anything to do in my mind with whether you should use a prologue instead of letting such hook occur in your first chapter. So, what's special about a prologue? Others may differ, but I think a lot of the justification for a prologue springs from one simple fact about what readers generally assume when they start reading a book. They assume the the first character they meet is the protagonist and that the main action of the book takes place, or at least starts, in the time and place where the book starts. So, if your hook involves the main character in the time and place of the primary plot-line, you don't need or want a prologue. I believe that you should use a prologue when you want to start with a scene which does not involve the main character and/or occurs at a different time or place than the main plot-line of the book. Why? Because the fact it is a prologue signals the reader that the the main plot-line involves someone or something else. It may be solving the crime which occurs in the prologue, dealing with events set in motion in the prologue, or how other people deal with what is set up in the prologue, but some kind of shift or separateness will occur. And, while I have written tales with bookend structure, I'm not a terribly big fan of prologues/teasers/openings which occur in the future from the main action. See below. 24 Hours Earlier (A Blog from February 4, 2014) Two quick knife thrusts skewering my gut, then the man in black leather twisted the knife and ran, but not before grabbing the McGuffin. As I lie here on the floor, blood soaking into the medium pile carpet, my vision dimming as life flows out of me in crimson pulses, I wonder if it was all worth it. The betrayal, the confrontation, the plotting, and all the burials -- Jeez, it's a lot more work to bury a body than you think. And for what? Life was so simple, so happy, so violence-free just a day ago ... Okay, so there's nothing about that intro that is true, except that I did "lie here." But, I'm sure you've seen (better written) intros like this before in stories, books, movies, and, especially, televisions shows. Desperate to have an action scene or a cliffhanger as a hook to grab the audience before they can change the channel or stop perusing the book and saunter down the aisle to pick up something with a bimbo on the cover, writers too often love to skip ahead to the climax of their story, then head back in time and run the story forward to explain how the hero got into such a desperate situation. For example, in the movie version of Starship Troopers (you know, the one with Doogie Howser as a military scientist who dresses like a Nazi stormtrooper), the movie starts out with an action sequence of soldiers firing their machine pistols at a exo-skeleton alien bug, advancing as they do so (cause bullets are so much more effective when shot from three feet instead of fifteen feet) until one gets grabbed and impaled by the bug. Then we skip back and watch the soldiers enlisting and training and showering and talking tough until they arrive at this scene, which ends up not being pivotal in any way. The device is even more common in television shows -- so common that it drives me crazy. Sometimes, the clip is even set up as a cliffhanger, when it isn't really one or when it has no relation to the main plot. I see this kind of thing so often on television, especially on action-oriented shows, that I am sick to death of it. So, what is the point of this post? To tell you as writers to STOP doing this. It's hackneyed, it's overdone, and it makes what might be a good story a crappy, cliched one. Readers may put up with being misled, but they certainly don't like to see the trick as blatant manipulation. And they really don't like to be lied to. If you start with a pivotal action moment and backtrack, you, at best, undercut the suspense as to what is going to transpire in the story. The reader/viewer knows the protagonist is going to survive to reach this point and that certain events will have to occur to create the situation (the volcano will erupt; the bad guy will steal his gun; whatever). Worse yet, the scene may reveal other critical clues about the story arc -- who the bad guy is, when the event occurs, who else is there or not there. In short, the action teaser has all of the egregious faults of the worst movie trailers, but with no upside because the viewer/reader is already consuming the product. Sure, it's great to start your story/book/movie with a hook, especially an action hook, but if you can't do that naturally with either a prologue or the first chapter, then maybe your story shouldn't really be starting where you have it starting. "24 hours earlier ..." captions should be like exclamation points, used sparingly and for very good reasons. So if you are thinking of doing either, think again, and just say "NO!!!!!!!!" Okay? | | |
|
|
A Review of The Ballad of Songbirds and Snakes A Hunger Games Novel by Suzanne Collins If you don't already know, Suzanne Collins has a new Hunger Games book out, a sequel about the early life of President Snow. I think Suzanne Collins is an excellent writer and that the Hunger Games series not only had great narrative description, dialogue, and scenes, but a surprisingly good plot. Sure, you can argue the world of the capital and the districts stretches credulity, but within that premise there is a surprising amount of attention to detail and sensible, but clever, plot twists and turns. Writing a prequel is tough at the best of times (ask George Lucas) because readers already know what happens later and therefore have preconceived notions about what happened in the timeline of the prequel, yet Collins manages to pull off this difficult feat. Even more, she makes Snow a compelling, complex, and interesting character and continues to deliver shocking twists and turns along the way, all while providing the reader with all the action and event touchstones they came to love in the original trilogy. Highly recommended. Five stars out of five. Get it here on Amazon. |
|
|
Jean Rabe and Craig Martelle just released their new fantasy adventure novel, Black Heart of the Dragon God. I plan to review it in next month's newsletter, but you can already get it on Amazon as an ebook (including in Kindle Unlimited) or print. Why wait? Get it here. |
|
|
Sacrifice, by Andrew Boylan Get a free U.S. Audible code to review this tale. A filmmaker down on his luck. A desert town full of secrets. An ancient cult reborn. After a decade of failure in Hollywood, Benny Hernandez has run out of money and options. No matter how bad the times have gotten he can’t imagine ever going home again. The small, desert town where Benny grew-up holds nothing but nightmares that he still hasn’t entirely awoken from. Late one night, his old, high school girlfriend, Diana Armijo, calls begging for help. She believes the cult they escaped years ago has resurfaced in the mountain village nearby. Can Benny face the demons of his past to tell the story of a lifetime? |
|
|
Donald J. Bingle is the author of seven books and more than sixty shorter works in the horror, thriller, science fiction, mystery, fantasy, steampunk, romance, comedy, and memoir genres. His books include Forced Conversion (near future military scifi), GREENSWORD (darkly comedic eco-thriller), Frame Shop (murder in a suburban writers' group), and the Dick Thornby spy thriller series (Net Impact; Wet Work, and Flash Drive). He also co-authored (with Jean Rabe) The Love-Haight Case Files (a three-time Silver Falchion winning paranormal urban fantasy about two lawyers who represent the legal rights of supernatural creatures in a magic-filled San Francisco; sequel is in the works). Don also edited Familiar Spirits (an anthology of ghost stories). Many of Don's shorter works can be found in his Writer on Demand TM collections. Get the audiobook version of Net Impact at Audible.com, Amazon, and iTunes and the audiobook version of Wet Work at Audible.com, Amazon, and iTunes. Full disclosure: Various links in my newsletter or on my website may include Amazon Affiliate coding, which gets me a small referral fee (at no cost to you) if you purchase after clicking through. |
|
|
|
|