Tuesday, April 22, 2014

Teaser Tuesday

It’s Teaser Tuesday again! So this Tuesday Dan’s sharing a snippet from an unreleased and untitled project that you’ll see later this year. Pretty awesome, huh? I have to keep my lips sealed about this latest novel of his, but I will tell you this: I think this is going to be Dan’s best book yet!

Scroll down to read more!

Hugs and happy reading,
Laura

Teaser #1 of Untitled Project

At the D-Wave Systems quantum computing lab in Seattle, Washington, project manager Franklin Thomas terminated the program loop inside their prototype supercomputer and squeezed his jaw in frustration, rubbing the sandpaper texture of his stubble. He hadn’t shaved in days.

Nothing was working.

Too hot. Much too hot. They were hyper-clocking the CPUs, generating way too much heat.

Enough heat to cook anything.

Franklin glanced around the lab. Rows of empty desks littered with circuit boards, racks of processors sprouting wires like gnarled tree roots, chips steaming in cryogenic helium baths.

Too much heat.

It was midnight, and the hallways leading out of the lab were dark. Everyone else had gone home for the night, like sane people.

They knew a doomed project.

Franklin sighed and rose from his terminal, fumbling for the ID card hanging around his neck to unlock the magnetically shielded room containing the prototype.

A few weeks ago, one of the other project managers had died of a heart attack. Too much stress. They were all stressed. Months behind schedule and way over budget. Bugs. Bugs everywhere. Franklin would fix them in the evening, and in the morning he’d find a dozen more, all different ones. Sloppy, like the runtime loops had been coded by first graders.

They were doing brand new science, quantum physics, superposition states and entanglement—light years ahead of the industry.

And his team coded like first graders.

A scuffle sounded behind him. Like rubber on linoleum. He spun, eyes scanning the impenetrable black hallways. Nothing.

Just his imagination, the building settling for the night. With a chill, he slid the card into the reader, feeling a rising eagerness to get home to his wife. Just this one last fix, then he’d go home.

The door clicked and swung open.

The prototype rose before him, the size of a refrigerator, all gleaming black plastic. The shell radiated heat, yet sent chills down his spine at the same time. The sight of the D-Wave Chronos Quantum Computer never failed to catch his breath in his throat.

It was worth it. It was all worth it.

He stepped across the room, static electricity prickling his skin, and opened the prototype box. Putrid smoke billowed out from inside, stinging his nostrils.

More melted electronics.

By themselves, the rack of processors running inside the box were no laughing matter. A hundred AMD Opteron 16-core CPUs clocking ninety-four trillion floating-point operations per second. But it was the box that was truly cutting edge. The protective thermal canister cooled the processors to near zero and put them in a state of quantum superposition, allowing the processors to hyper-clock in unlimited parallel states.

One by one, Franklin unplugged the ruined processors and tossed them behind him. They clattered on the floor. A small fortune’s worth of frontline CPUs, ruined. Finally he wiped sweat off his brow and slid the rack out, set it aside.

Then he stepped inside the box.

Beneath the smell of burnt plastic, the warm air tasted stale, like he had just entered a crypt. Barely enough space to kneel.

He hiked up his khakis and crouched down, reaching for the panel covering the cooling electronics—

Another scuffle. A patter of footsteps.

In the same room as him.

Franklin’s hand froze over the panel, his hairs stood on end. He peered out from inside the box, but the rectangle of light showed only half the room.

“Who’s there?” he stammered.

Without warning, the box slammed shut with him inside it, plunging him into darkness. No light.

“Hey!” He jumped up, pushing on the door. But the latch only opened from outside. Not the inside. No one had planned for the possibility of someone getting stuck inside. Why should they?

Another design oversight that would need to be fixed. Franklin knew he could force the door, but he didn’t want to damage the prototype.

Besides, he knew what this was. One of his team playing a practical joke on him. They always said he needed to relax.

“Peter, that you?” he said. “Ha ha. Very funny. Now let me out.”

But then he heard something else, something that chilled his blood. Around him, a rising mechanical whine.

Another program loop was starting.

The box was running another loop.

With him inside it.

In an instant, his irritation gave way to terror. He yelled, slammed the walls, crashed against the door with all his weight. Again, and again, but the walls of the prototype didn’t budge, as if somehow frozen in place by a rigid force field.

A program loop . . . what would happen to a person inside a program loop? The prototype entered a quantum state not meant for living things. What would happen to him?

Throat thick with fear, skin prickling, he listened to the sound of the looping box. An eerie, stretched out silence, almost like a moan. Nothing else.

All sounds from outside the box had ceased. Utter quiet. Just his own racing pulse. Just the gentle whine of the box, now his prison, running through an endless program loop. Looping him.

A bead of sweat dripped from his forehead.

Want to know more about this book? Sign up below for Dan’s newsletter to get updates on all his latest projects!

* indicates required

Saturday, April 19, 2014

The Grandfather Paradox: Writing Stories About Time Travel

When you're writing a story about time travel, there's only one thing that matters: how you deal with the grandfather paradox. I'm going to skip preliminaries and just get right to it.

The Grandfather Paradox Explained


Let's say you go back in time and for some stupid reason decide to murder your grandfather before he has a chance to impregnate your grandmother with your mom. No biggie, right? So you cease to exist, and all's good. Well, if you no longer exist, then who the hell is the murderer that went back in time and killed him in the first place? We have a paradox.

In a story about time travel, you REALLY DO need to deal with this, because it is paradox, and any time you have someone travelling back in time for any reason at all, I'm going to be asking  what would happen if they killed one of their ancestors? Even if it's by accident. Google defines a paradox as thus:
A statement or proposition that, despite sound (or apparently sound) reasoning from acceptable premises, leads to a conclusion that seems senseless, logically unacceptable, or self-contradictory.
Time travel opens that can of worms all the time, every time, no matter how you tell it. Okay, so you have a few options in how you're going to explain this one away. This is also a listnot by any means exhaustiveof how most authors tend to deal with it.

Don't Deal With It At All


This is by far the favorite method. You have time travel, your characters can go back in time and change things, and they change the past and yet somehow everything in the story's okay. Don't mention the paradox, and plenty of your readers won't even realize the logical self-contradiction you've introduced. This is acceptable for time travel romances and action adventure stories where people are travelling to ancient times for the ambiance and such, where no one cares about the logic of it all, but if anybody has to "fix" something in the past, the more curious readers will be frustrated. Because let's say John went back in time and "fixed" the broken past, then returned to the present. Now, in this different version of reality, he had no reason to go back in time and fix anything in the first place, so presumably it doesn't get fixed, in which case he would have had to go back and fix it after all, but then he wouldn't because he would have in fact fixed it, ad infinitum. It's a paradox and you can't escape it. When you don't deal with the paradox at all, there's a gaping hole in your time travel story. So, let's look at someslightlybetter ways of addressing the paradox than just sticking your head in the sand.

Create A Self-Consistent Loop


Harry Potter, book 3. Yeah, you remember. It was clever how everything tied up in the end. Harry and Hermione were able to travel back in time and save two lives, without ever letting their past selves know they had saved the lives, so their past selves reached the present and made the perfectly logical choice of going back in time to save two lives, even though their future selves had already saved those lives. If you'll remember from the movie (I don't remember it from the book) Hermione even had to toss a rock at herself to keep things consistent. But here too, the logic falls apart. What would have happened if they were sloppy and their past selves saw them? Their past selves would then do something different, and theh all the circumstances leading up to their future selves would have been different, presumably leading their future selves to not be so careless...but then we're back with the old paradox. Well, you might say, they weren't so careless. Yes, but they COULD have been careless. Shoot, what's to stop someone from CHOOSING to be careless just to test the paradox? I mean, I would. Just to see what would happen. No matter how this works out, the past and present can never be truly self-consistent in a broader sense because a character can always deliberately screw things up. We don't fault J.K. Rowling for this, because she's J.K. Rowling and Harry Potter and Hermione would NEVER deliberately screw things up. But this brings up another common answer to the paradox.

The No Free Will Version


You know how this one works, right? Even though we have the illusion of free will, the past, present, and future is actually already set in stone. So even though we travel back in time, that travelling back in time has already been accounted for in the past because the universe "knew" we were going to do it. Maybe we try to change something and then it turns out all along that it's because we changed that thing that the present is as it is today. This one might be even more flimsy than the don't deal with it at all method. Here's why: you can argue we don't have free will, but only as long as we can't see the future. If we can see the future, then we're automatically given the choice to disobey that future. Here's an example. If I know it's my destiny to call so-and-so at exactly 9:27 PM, surely I can resist calling until 9:28, even if just out of spite? Plenty of people would test that, believe me. Now, if there's some kind of cosmic force that urges my hand toward the phone at exactly 9:27, then you've got something else to explain, and "no free will" isn't good enough. Now you've got a cosmic force that forces people to obey their destinies. Which could work, but you do have to add that part in. Then again, you can always get by with...

Go So Far Back It Doesn't Matter


Authors do this by sending you back thousands or even tens of thousands of years. No grandfather paradox because your grandfather didn't exist yet, right? Wrong. Now you've got a whole bunch of ancestors you could murder. But what if you have...

Exceedingly Careful Characters


These are the guys that travel back in time and say stuff like, "Don't change anything," or "Touch as little as possible." It's a fun as hell concept, but it doesn't work that well because of the butterfly effect.

The Butterfly Effect


If you've seen the movie with Ashton Kutcher, you might know what this is. If you haven't seen the movie, or you didn't get the movie, here's what the butterfly effect is: in a nonlinear system, small changes will accumulate and become vastly larger changes down the road. What's a nonlinear system? The universe. Here's an example: I met my fiancee at a college party, got only her name, and left the party with no intention of ever seeing her again. A week later, I was at another party and wasn't really feeling it and decided to go to a different party. I walked into the second party just as she was walking out. We exchanged contact info, the rest is history. I've been with her almost six years. Can you imagine how vastly different the last six years of my life would be if I had gotten to that second party just one minute later? In other words, one minute, maybe even one second, shaped the rest of my life. You might think this is cherry picking an example, and it is. You're right. But these kinds of time moments are happening all the time, and if you change just one of them, things will turn out very different for EVERYBODY. Oh, and the farther into the past you go to change something, the greater the effect is going to be. Travel back in time a day, and you might be able to hide in a closet and not change much. Travel back a year, and today's headlines won't even match anymore. Travel back to the birth of Christ, and the USA never comes to be. Travel back to the dinosaurs, and humans never evolve. Get it? If you change ANYTHING, it's over.

Only The Main Character Remembers


This is a technique used by a lot of authors, and it's kind of necessary for a lot of stories. Your hero goes back in time, changes something, then comes back to the present. Everyone else seems to be different, but he's the same. Somehow he still remembers the "old" past, while everyone else got the memo about the "new" past. Back to the Future had a version of this. It's a fun scenario, but in no way is it logical. In fact, it's so illogical you can't even really talk about it in terms of a paradox. So I guess you dodged that bullet. Well, if we're going to talk about it, I guess it does kind of make sense. The main character's past is retained, so him changing the past is also retained, but then you run into the issue of why doesn't he know anything about this new present? To those around him, he would appear to have suddenly lost his memory, and there would have been no causal event, because they didn't see him travel back in time and change things. In their version, no one traveled back in time. Yet in his version, he did, and you've got a whole new slew of logical inconsistencies. Paradox not solved.

Okay, So What Should You Do?


As you can see, we've gone over quite a few good methods already employed by the best authors and screenwriters out there, and they've all done an inadequate job of addressing the paradox. There are a few others that don't bear mentioning, like the time tends to correct itself camp, and other equally wonky explanations. But all this begs a question...can you address the grandfather paradox in a way that makes logical sense? Or do you have to skirt the issue? I think there are good methods out there for dealing with the paradox, and they're outlined below:

You Can Look But You Can't Touch


It's kind of like the watered down version of time travel, where you can go back, but no one can see you. Or maybe you can only look. This kind of time travel works, and there's no paradox, because you can't send any information back in time to change it. The Light of Other Days is a sci-fi novel with this kind of time travel. But it's also no fun.

Parallel Universes


We're starting to get more clever now. Michael Crichton did this in Timeline, but then blew it. I love him no less because of that. The idea is there's an infinite number of universes at different stages of time, and you can travel to another universe that is identical to our universe just days/months/years in the past. This one works also, because you can change stuff, and it WILL change the future of THAT universe, but not the universe you're from. So no paradox. Incidentally, in Timeline, a man traveled to a different universe that was a few hundred years behind ours, dropped his glasses in the sand, and then we dug them up in an archaeological dig in our universe. It's not supposed to happen like that with parallel universes. That's the tiny little part that Crichton messed up, but it was an essential suspense-builder in the beginning.

The Duplicate Past


So far the best I've seen, and also a fun one. Guy goes back in time, hangs out a little bit, accidentally kills himself...but nothing happens. He still remembers his version, and his past version, well, is dead. This one's similar to the only the main character knows method. But here's where it gets fun. You go back in time, talk to yourself, and let's say they change their mind about travelling back in time. Since you still have your past where you did travel back in time, nothing happens to you, but they don't step inside the time machine when their time comes, so now there's two of you. Oops. It's kind of like every time you travel in time, you make a duplicate of the past that you can change, but you can never get back to the one you left, even though you remember it. Watch the movie Primer for an example of this kind of time travel.

The Feedback Method


We're getting tired of all these wishy-washy ignore the issue solutions, so let's just take the paradox head on, grab the bull by the horns. Let's look at what's actually going on. Someone's travelling back in time and changing stuff, which, if it's a good time travel story, should have ripple effects that propagate instantly to the future and reflect itself in the main character, in a kind of feedback loop. If we really think about how this might work, it's pretty easy to play this one out. As I'm changing things, my past is changing. What if I decided to kill my past self? I'd never get there. I might make it so far as my house, but my reality would be constantly reshuffling. Besides being crazy disorienting, I might not even physically be able to take a swing at him. It would settle into different realities but not others, depending on which ones were self-consistent. You might not even be aware of not being able to do certain things, because the moment you took a step in the wrong direction, you would have altered something that calculated out to a different scenario. Here you're not trying to explain away the paradox at all, just let it run it's course. It's a lot to think about, though, and it's easy to get wrong.

The Quantum Physics Limitation Method


This is where stuff gets a bit heavy. You've got a pretty good understanding of quantum physicsand you know it's already rife with paradoxes anywayso you craft a quantum physics-esque explanation that handles the paradox. Most readers won't understand it, but you can rest at night knowing you honored Neils Bohr and Erwin Schrodinger. Here's how a rough line of thinking might go as an example: According to the Heisenberg Uncertainty Principle, there's a limit to the amount of knowledge that you can pass back in timeand the accuracy of actions taken in the past (the farther back you go, the more inaccurate they are)and it just so happens that this limit disallows paradoxes. You've got a time machine, and you can use it all day, but the uncertainty principle guarantees that nothing you do will ever constitute a paradox. Yeah, good luck with that one. Still, it'll be a hit with hard sci-fi readers.

The Potpourri


Grab what you like from each method and put together a special case. Maybe a duplicate past scenario with a little feedback. Or a parallel universes version with an exceedingly careful character. Or a no free will version with a quantum physics explanation. The rules are really nonexistent here, because you can make your reality however you want. In dealing with the grandfather paradox, what's most important is not how you address it, but that you do in fact address it in a way that's satisfying. The worst, and I mean WORST thing you can do, is ignore the paradox altogether.

With all that said, you've probably guessed by now that I'm working on a time travel novel of my own. If you want to see how I handle the grandfather paradox myself, subscribe to my newsletter by entering your email address below and you'll get a message when it comes out:)

* indicates required

Friday, April 11, 2014

New Book Announcement: Eternity’s End


Dear readers,

I have another book to announce! I've finished writing Eternity's End, the sequel to God's Loophole and book #2 in the trilogy, and I wanted to share the cover and the back flap blurb to get you guys excited!

I hope you've been sinking your teeth into God's Loophole, the first book in the series, but if you haven't, you can visit this link to buy it from Amazon.

Eternity's End takes the trilogy in a slightly darker direction than the first book, as Gabe and Raedyn grapple with the consequences of their powers. You'll find more scene time with Sabina Boyd and other scientists that are trying to stop what Gabe, Jer, and Raedyn unleashed in the first book.

Eternity's End should be coming out in late May, although that date could change a bit. However, the book is complete at this point, so stay tuned for a teaser in the next few weeks. Now, I'm going to stop prattling on and let you check out the cover and the blurb below. To view the cover, make sure your email provider is set to display images.

All the best,
Dan


Tuesday, April 1, 2014

Teaser Tuesday!


For those of you who haven’t heard, God’s Loophole is out! (Click here to read more about it!) This is the first book in Dan’s technothriller trilogy. However, now that it’s out, I can begin to tantalize you with teasers from Eternity’s End, the second book in the novel.

So, for Dan’s first ever Teaser Tuesday, here’s a short excerpt from Eternity’s End:

Sabina Boyd hurried past the fire truck, her heels clomping on the pavement, and lifted the caution tape around the warehouse to stoop under. Inside the building, three people milled around the hole in the floor—Neil Anderson, a government geologist, and the county fire marshal.
They glanced up at her approach.
“Sabina Boyd, FBI.” She shook hands with the geologist. 
“Gene Mcgavern,” he answered, pushing up his glasses, a short, balding man in his late fifties,   “United States Geological Survey.”
She nodded to the hole. “So what are we dealing with here?”
“Well, you’re standing on a concrete slab foundation topping fifty meters of alluvial fan—sandy clay, basically, deposits from creeks and rivers. This is Palo Alto, your water table’s twenty to thirty feet deep, tops.”
“Meaning what?”
“You ever dig sandcastles when you were a kid, Agent Boyd?”
“Never liked the beach,” she said.
He raised a gray eyebrow. “You never built a sandcastle?”
“Listen, Dr. Mcgavern,” she said hotly, “I’m very busy right now, so if you could just get to the point—”
“The point is you’re digging in wet sand,” he said. “It’s muddy. It slumps over, caves in. You scoop it out and your hole fills with water, you scoop out more, and the sides cave in.” He pointed at the hole. “You’re looking at a hole dug in wet sand.”
“So it’s unstable?”
He nodded, his eyes twinkling. “You can’t dig a hole like this, Agent Boyd. Straight down, no bracing . . . hell, I can’t even see water down there.” 
A faint smell of sulfur drifted out of the hole, like rotten eggs.
“How deep is it?” she said.
He shook his head. “I can’t see the bottom. Can you?”
She rubbed fatigue out of her eyes and glanced around the warehouse, and her gaze settled on Neil’s black, patent leather shoes. “Give me your shoe.”
“You’re not tossing my shoe down the hole, Sabina.”
“I’ll grab a road flare from the truck,” said the fire marshal, heading for the door. He came back a moment later with a red stick with a white cap. He twisted off the cap, scraped the flint tip across the flare, and the tube erupted in blinding red flame.
“Stopwatch?” he said.
Neil pulled back his sleeves, readying his finger over his watch. “Go.”
The fire marshal tossed the tube into the hole.
The four of them watched silently. The flare plummeted twenty feet, then forty, then sixty . . . then a hundred. Finally, its red-hot light dimmed to a pinprick, and vanished.
“I didn’t see it land,” she said.
“What was the count?” said the fire marshal, still peering down.
“Six and a half seconds.” Neil pursed his lips, and a moment later, he had the calculation. “Over two hundred meters.”
“Jesus,” she said.
“Could be even deeper,” said Dr. Mcgavern.
She turned to him. “What do you make of it?”
“Two things,” he said. “First, I have no idea how this hole was dug. Second, by tomorrow morning, the ground we’re standing on isn’t going to exist.”
“It’s going to cave in?”
“That’s not all.” He pulled out a pen light, clicked it on, and shined it inside the hole—focusing the beam on the packed dirt about six feet below the corroded concrete. “See that?”
She leaned closer, careful not to step on the edge; the corroded slab jutted out a few feet over the hole, looking perilously weak. At last, she saw what he was pointing at.
Movement.
In the circle of light, tiny wisps of dust were slipping off the surface, floating down into the shadows.
“What am I looking at?”
“Something’s actively decaying that soil.”
“You mean the hole’s spreading?”
“That’s right.”
“Can you stop it?”
“Stop it?” He stared at her like she was crazy. “Hell, I don’t know what’s causing it . . . I’ve never seen anything like this.” 
“What’s your recommendation?”
He clicked off the flashlight. “Only one thing to do,” he said. “We got to send someone down there.”


***

If you enjoyed that, click here to add Eternity’s End to your “To Read” list, and make sure to stay tuned in during the next few weeks, when Dan will reveal the cover to Eternity’s End!

Hugs and happy reading,
Laura


P.S. If you haven't already, be sure to sign up for Dan’s newsletter below for updates on all his new releases. He announces all his books a month early and offers sneak previews and free pre-release copies only to subscribers, so make sure you're on the list:

* indicates required