RIP A.C. Crispin

It is a sad day for the science fiction community.  Author Ann Crispin (A.C. Crispin) passed away this morning.

Star Trek fans probably know her best for books like Sarek and Yesterday's Child.  She wrote many Star Wars books including the Han Solo Trilogy.  Her last novel is a prologue/prequel to Pirates of the Carribean titled:  Pirates of the Carribean:  The Price of Freedom.

Star Trek and other fans can read her farewell at:
http://www.startrek.com/article/ann-crispin-says-goodbye

Ms. Crispin taught at many writer workshops.  In fact, I participated in one at Atlanta's Dragon Con in 2007.  I'll never forget her personal critique of one my submission and a question she asked about one character in particular.  "Does she pee?" 

No, I'm not joking.

Ironically, this year was the first year I have been able to participate in Dragon Con since then.

RIP Ann and thank you.

Robot Nurses and Tractor Beam May Be Here Soon

In another example of Star Trek influencing real-life technology/research, NASA is spending $100,000 to analyze tractor beam techniques at its Goddard Space Flight center.  The article referenced discusses past research and intial successes with "optical tweezers" that can trap objects in small lasers.  Near-future applications could include installation of such devices on rovers to be sent to other worlds or deep space probes - allowing them to collect samples that otherwise would not be obtainable.  Personally, I like the idea of the "optical tweezers."  This could be a good term/technology for writers to use, especially if they want a credible tech basis for their writing.  When I first heard it, I was thinkinging mainly about healthcare applications - like optical surgery, but you make your own decisions.

Speaking of healthcare, Roomba owners might find this interesting.  Toyota and iRobot has developed a home-use "robot nurse" named Ava which could be available for purchase as early as 2013.  I must admit that the video attached to the article isn't exactly something to ooh and ah about.  Ava looks like a mobile broomstick/post with a tablet computer on top.  That tablet would seem to be the key as the iRobot CEO mentions can show the face of a doctor or actually connect to a real physician.  What isn't really mentioned is that this device could probably be easily adapted for healthcare monitoring.  I mean basic vitals could be taken with attachments (automatic blood pressure cuff, pulse sensor, pulse/ox meter, respiration...) that are currently used by medical professionals.

The robot article also shows an example of another device attached to a patient's leg from the knee to the foot.  The caption shows the device as something that could help patients walk, but not just by giving support and possible muscle enhancements.  Patients who undergo knee surgery could use this device as part of their rehab and reduce the time needed with a physical therapist.

I've discussed bigger examples of this type of technology in my Iron Man 1/2 post last year.  One thing I find interesting is the size difference between the device shown in the post developed last year and the picture of the device on the person's leg.  While there are obvious differences in functionality, it's still interesting how much more streamline the medical device is and it's technology is only one year newer.

The World Is Ending - Postponed From Earlier Date

You heard it here.  Of course, chances are if you are reading this post after Friday, October 21, 2011 the prediction was wrong.  I'm sorry, I mean it might have just been postponed....again.  You may remember the predictions of radio preacher Harold Camping who said Judgment Day would come May 21, but when it didn't happen, he said that was just the spiritual judgment day.  The world will end more quietly Friday October 21.  So should we waste time continuing to write and edit, or just have fun in our last 24hours (plus or minus).  I mean, I have some work deadlines coming up from my paying job. 

You know what really sucks about this prediction?  If it's true, I'll miss the opening of Avengers.

Sometimes these "news" stories are odder than any fantasy or sci-fi story and makes me think about doing something like a short story with such a theme.  Although, I think it works better for a comedy.

Cool Stuff From Kepler For Science Fiction Writers

A couple of days ago, I found a link to an interesting article on space.com.  The article/slide show focuses on the strangest alien planets found by the Kepler spacecraft/telescope.  Some of the worlds discovered could be particularly interesting for science fiction writers who want to include real science to add to the story credibility.  Here are a few examples of worlds from the slide show and how they could be used. 

• Closest planet:  Epsilon Eridani b orbits an orange sun-like star only 10.5 light years away.  Whether your story uses faster-than-light (FTL) travel, near-light-speed, or stasis, you could reference such a world as a staging area for sending ships deeper into space.  A space station or planet-side outpost coule be used.  It could also be a staging area for an aggressive species planning to invade Earth.
• A planet in Globular Cluster M4 is referenced as the oldest planet found - an estimated 8 billion years before Earth.  If you want to discuss more advanced races, an older planet is a good place to start, that way you don't have to get into debates on the speed of the evolutionary process.  They had a head start.
• Fastest planet:  at only 740,000 miles from its sun, this planet makes its orbit every 10 hours.  I honestly couldn't say how to use it, but it just seemed too interesting not to mention.
• Waterworld:  A hyperspace-hop, slipstream-skip, and warp-jump away at only 40 light years lies GJ 1214b.  Researchers believe that this planet (about 3X the size of Earth and over 6X as massive) is most likely a water world.  I shouldn't have to give the obvious suggestion that humans move to this world for the water.  It could be a good place to bring up aquatic alien life (sentient or otherwise).  But another possiblity is another staging area.  Load up on more water for consumption and/or splitting water atoms to take oxygen for life support and hydrogen for fuel.
• Dying world:  WASP-18 is another world with a fast orbit - less than one Earth day and scientists theorize it could be orbiting closer to its star and impending doom.  This could be tied to lost civilization, planetary evacuation types of stories.  Encountering ships from the survivors.
• Most Habitable:  Gliese 581 d.  Only about 20 light-years away this is apparently the world with the greatest possibility for being habitable.  It's about 8X as massive as Earth.  I googled for a bit more since I'd heard of Gliese 581 before and found similar stories about the Gliese 581 c possibly being habitable.  Note that 581c also has a quick orbit  - 13 days.  Again, obvious story-lines one could use include staging area for deeper space travel, colonization...  Consider the potential difficulty of colonizing a world with a short orbit.

Keep in mind that Kepler's mission is to search for Earth-sized/like worlds.  Some of these don't fit that description, but they're interesting nonetheless.

Trying to Regroup and Recoup

How do you regroup and restart writing when faced with a loss of past work/edits?  I figure that one is to do the same thing I did when I finished my first novel draft - have some fun with a short story.  When I glanced at some of my recent blog stats, I noticed my post on the Star Trek fanfic contest had some recent hits. 

The good and bad of it is that I've got a couple of ideas for stories, but I'm not sure which to choose.  Contest rules limit to one story.

One idea follows the last Next Generation cast movie - Nemesis.  With the Romulans becoming friends, all of the Trek villains are now allies.  Starfleet wants to promote Picard to admiral and make him a figurehead in the Federation.  Some high ranks in Starfleet are worried that with all the known Trek villains now friends, that this will actually split the Federation.  Why?  You'll have to read it and find out.

The second story idea takes place about a year after the JJ Abrams Trek movie.  The Enterprise has spent lots of time touring the Federation with the crew being more like celebrities than Starfleet officers and explorers.  Kirk finds things becoming very routine and actually getting dull.  When a chance for action comes about, he jumps at the chance - too quickly and people die for the first time as a direct result of his orders.  How will he react?  Think about it.  His situation is really no different than a Navy Academy Senior going from the classroom directly to command of an aircraft carrier.  Is he truly ready to command?

So, which to write?  I think both have potential.  Obviously I think they do or I wouldn't consider them!  I'm open to input.  Which sounds more interesting?

Share your feedback and

Write On.

Redundant Backup Is An Oxymoron

I've been procrastinating about this post because I'm embarrassed to admit this.  I've been in a major writing/blogging slump because a few months ago I hit the unlucky/stupid jackpot.  My computer had a virus and, while many files were saved, much of my writing was lost.  Fortunately, I had it all backed up on a USB flash drive - that got left in my pants pocket and washed - aka RUINED.

At first, I thought all was lost until I went to our old computer and did find a copy of my story.  The problem is it was about 1-2 years out of date.  So, I'm back to a raw draft - most of my edits lost and friends who've edited for me deleted their copies.  For now, I'll probably have to shelve this piece and, when I have time to write again, work on another project.  There are plenty of creative voices in my head.  I'm sure one of them has something entertaining to say.

Learn from my stupidity.  Don't just backup often, make a couple of backups to keep your work safe!

Motivate To Write Through Non-Writing Projects

After about 2 months of working out, training, and happily sweating off about 25 lbs, I finally tested last Saturday and earned my second degree black belt in Tae Kwon Do.  Of course, one of the best aspects of that was the fact that my six-year old son was there to watch it.  He seemed more interested in his iPad for the most part, but took notice sometimes when Daddy got up for sparring, grappling, and board breaking.  What dad doesn't like to succeed in front of his child? 

For the most part, I've done no writing or editing work on my own projects during this time, but I'm hoping to change that some now.  In some ways, I think this break is good for me as a writer.  I'm in the best shape I've been in for a few years, I have a renewed sense of self-confidence because of what I have just achieved, and now I can come back and look at my projects with a fresher perspective.

I know some people who seem so dedicated to their writing that there's no room for anything else.  I don't think that's good for anyone.  Too much focus on one thing will lead to burnout and frustration that much faster.  Don't be impatient.  Sometimes it will help writing to walk away from it and do something else.  Some science fiction writers are former military.  I've seen how some writers are also artists or have other hobbies. 

Another consideration is that I believe that my martial arts training helps my credibility as a writer.  I remember in writing workshops hearing people say, "Write what you know."  Incorporating outside interests into writing helps the credibility of a story, and makes associated research easier/more pleasurable (less like "work").  Also, think of your favorite writers.  When reading the bio on the backs of the books, how often do you see that they've had military service, or other activities where their expertise shows clearly in their writing?  As a reader, does that make you more interested in the author than if the book bio simply listed a college and no "life experiences?" 

Personally, I like reading good books written by interesting people.  I'd be very proud to include things in an author bio as: former member of the United States Army.  2nd Degree Tae Kwon Do Black Belt (maybe 3rd by the time I actually publish).  Of course, my most important credential is, and always will be, Daddy.

Get out, take on the world and

Write On.

Good Quote For Writing and Life

This Saturday, I'm finally taking my second degree black belt test.  At my school, ETO, one requirement is to write an essay.  Since I'm testing for second degree, my topic was how a black belt turns to back into a white belt.  A friend of mine gave me a good quote from author Louis L'Amour that fit this perfectly:

"There will come a time when you believe everything is finished.  That will be the beginning."

Obviously this relates easily to writing and editing and how often do we, as writers, hear that?  I've heard other versions, like "When you think you're done editing, you're half way there."  It really is similar in concept to martial arts.  Getting my first black belt was great, but I knew I still had so much I could learn.  And more importantly, I wanted to learn more.  Writers have to carry that same hunger.  Once the story is written, you must WANT to go back through it over and over and over again to make the manuscript sparkle like the brightest diamond.  Then, take a step back, rest and start again.

Plant Technology

Here's an interesting article from Fox News on research that will turn ordinary plants into security devices.  The plants turn white when certain elements enter their environment. 

Now think about this for writers.  Take this to the next level.  If technology exists to make plants change in the presence of certain chemicals, what about people?  Setup a biological defense against specific aliens.  Or even more specific.  Say a law enforcement agency has a simple DNA sample.  What about plants that could detect that person's DNA?

Think of how this could be used.  Rather than a large team of tech experts with sophisticated and complicated equipment, maintenance of the system could be done with a biologist.  A story could highlight how this approach could be used at facilities with fewer financial resources.  Create plants that, once "fed" a sample of DNA or certain chemicals, it reacts in their presence.

So keep researching and

Write On.

Reviewing A Draft Before Sharing

Recently, I went through and critiqued a short story through Critters.  It was one of the worst things I've read.  The writing was so bad and littered with inexcusable grammatical errors that I completely lost track of what the story was about.  Because the writer sent the draft in such poor condition, I really think he/she will not get the best feedback on the story because I believe other readers/critiquers will also be distracted by the poor writing.  Also, since there are lots of stories to choose from constantly through Critters (and other online writing/critting groups) that some may start, get fed up and decide to choose another story that is easier to read.  Poorly written stories can take more time to critique.

Now, let me remind everyont that I'm a fan of Critters.  Overall, I feel they've helped my draft novel, Legacy Soldier, progress and improve.  They also helped me find some stupid mistakes.  There is only so much you can do to edit your own work because you're so close to it that you know what you want to say and sometimes confuse that with what you're actually saying in the story.  That's where having others to give an objective read is important.  That said, we as writers should try to give our best draft to beta readers/editors.

Even a first draft shouldn't go out as just after it's been written.  If you want the best quality feedback, send the best quality drafts.  I know I've mentioned these tricks/tools before, but let me go through a few again.

Run a spell/grammar check.  These tools aren't infallible, but they do help clean up a story.  Another trick I've heard is to read your story/chapter to yourself out loud.  Does it sound right?  If you have a friend/family member willing, let them read it to you.  If they have trouble reading parts, you may want to re-write.  If you don't have someone who can do that, a tool I've found helpful is a free downloadable text-to-speech software called Ultra HAL.  C/NET rated the free version pretty well.

So remember, write, read, re-write, read again, and

Write On.

New Year Goals

Happy New Year.  Like many others, I'm setting a couple of goals for 2011.  And, of course, most are related to writing.

First, I want to complete edits on Legacy Soldier and start sending it out to agents and publishers.  I've sent it out to a few and did get some partial requests, but in the end they all turned to rejections (those who've replied).  There are a couple other big agents I want to target, but I want one more coat of polish on the manuscript first.  Keep that idea in mind.  Just because you have sent off your manuscript doesn't mean you should just sit back and hope it's adequate.  Take some time away and then look it over again.

Second, I've started two new stories and I want to finish one - maybe just at novella length.  One is an urban sci-fi mystery story called TIA.  TIA is short for Temporal Investigations Avatar.  The technology allows the user to send their consciousness back in time to watch a crime.  The catch is that the past isn't as linear as most thought and a person must be trained to navigate to the time and place of the crime to find key pieces of evidence and identify the criminals.

The other is an alternative Earth urban fantasy were the eastern 13 states have been taken over by werewolves.  The protagonist is part of the military Border Patrol that tries to keep the werewolves from advancing.  Her team is tasked with protecting a lab that might have developed a vaccine for the werewolf condition.  The lab is attacked and her lover bit.  With a no-tolerance policy (those infected are killed) and only one vial of the vaccine surviving the attack, she has to get the vaccine to headquarters while safeguarding her lover hoping that the vaccine will also lead to a cure before his condition is discovered and he's executed.

So wish me luck, enjoy the new year and
Write On

Escalation or Twists. What Carries A Story Better?

Most people reading my blog know that I'm involved in a blog chain through the Absolute Write Watercooler.

FWIW, this was my submission.  Note, that my story has a slight twist and so do some of the other blog chain submissions.  It reminded me of a discussion I'd had with friends about story format/styles.  When it comes to action-oriented stories, particularly science fiction and fantasy, I've noticed most of the stories fall into two major categories.  Escalation and twist.

Escalation based stories seem to start action fast and early.  As the story progresses, the action drives it.  While this is interesting to me early, I tend to get a little bored with them about half-way through. I've read a number of sci-fi/fantasy books that seem to fall into a generic mold.  Have you read stories that do this?

Open with an unusual finding - Mysterious temple, space ship, planet, portal, hidden lab, secret government facility...  Main characters enter/investigate (even though they shouldn't - like going upstairs to hide in a horror flick rather than running out the door or calling 911 on a cell phone) and are attacked by small creatures, or lightly armed guards.  Small arms takes care of the immediate threat, but then the threat gets bigger - new traps requiring something different:  new technology or bigger guns.  Some stories give multiple concurrent scenes from different POVs - ground troops, aerial attacks, orbital combat.  All going on at once and while they're tied in together, it's still a variation on the same theme.  The nice thing about those is that they do give different angles on the storyline, but still follow the same formula - action intensity.

Unfortunately for me, it's like watching a comedy.  I actually don't find most comedies funny.  Why?  Because I spend all my time looking for the joke.  What makes a joke funny? Timing/execution, and surprise.  There's usually no surprise in comedies.  Some are amusing, but in general, I get bigger laughs from dramas where the joke comes out of left field.  If I want to watch a "comedy" on TV, I'll watch pro wrestling.  That's basically an action sitcom to me.

Action stories are much the same.  I like anticipation.  When I've read books using escalation, I've been tempted to skip whole chapters if they seem to just continue the action or increase it (more soldiers, bigger weapons, or other "bigger action").  At the very least, I sometimes read topic sentences and skip the rest of the paragraph. In the worst case scenarios, I just put the book aside.

Why don't I give specific examples of these story?  Simply put, they're published and I'm not, so who am I to judge?  I'm willing to bet those who read this post will have one or two of their own examples.

As for the twists, those are my favorites.  These stories may not always keep up the pace of action, but tend to keep my interest better even in the slower partsYou don't know what's going to happen and can't skip whole chapters.  I want to look for the surprise, the plot twist and complexity.  That's what carries a story for me.

I know that I'm oversimplifying, but it seems to be the trend that I've seen.

Anyway, let me just end saying Merry Christmas and

Write On.

Deleted Battle Chapter

Thought I'd post this deleted chapter.  I really enjoyed writing this chapter as it was going to be the first "real" battle in the book.  One hope I had was that by adding an action chapter like this early, it would help excite readers.  One thing that made me realize that isn't always the best approach was reading the first book in Jack Campbell's Lost Fleet series.  The first book, Dauntless opens with a fleet basically retreating from a battle and most of the book has them on the run.  The actual battle doesn't take place until the very end, but it was still one of the best books I've read.  Now, I did leave some action scenes/chapters, but removed this one for word count and the simple fact that it includes no main characters to the story.  It was more of a gratuitous battle scene.

However, the battle did set the stage for the main plot to begin unfolding.  My main character was working on a research project when word arrives that a "friendly" ship was destroyed stopping an enemy ship en route to Earth.  This information reached the research station with orders to mobilize personnel (including the main character) to another ship and prepare for the enemy. 

Again, I really enjoyed this chapter, but in order to reduce word count, I deleted it and just included a reference to it in the message sent by the

Remember, this was a first draft of the chapter, so it is probably a bit rough.  Hope you like it though.  It might give an idea for how I tried to set up battle scenes (wanted them to read with some credibility).

Enjoy and Write On.

Chapter X

Captain Terrance Curtis stepped onto the bridge for his watch shift on the Reliance.  The destroyer-class cruiser was said to be the fastest ever constructed by Ganeshans.  Despite the honor of being the commanding officer, Captain Curtis sighed at his orders.

“Investigate star system for signs of enemy presence,” summarized the orders.  The details that followed did not provide any useful information.

The most advance ship in the fleet chasing sensor ghosts from other systems along possible paths, he thought.  Unfortunately, he also saw the logic in the orders.  Reliance possessed the speed and maneuvering agility of smaller cruisers and more firepower than any ship in its class.  It was also the closest ship to the designated coordinates.

He walked to the main science station.  First Officer, report.

The officer on duty nodded to him responding telepathically, Not much to report, sir.  All scans of the sectors give no indication of a recent FTL conduit.

Captain Curtis’ eyes opened slightly wider.  Clarify what you mean by ‘recent.’

Of course, Captain.  We have picked up possible signs of FTL activity.  Analysis of the system scans show minor deviations in the orbital patterns of system debris consistent with a small FTL corridor.  Most likely a probe.  We estimate it occurred no more than sixty days ago.

Captain Curtis pulled the scan details on his PDU.  It had taken nearly two days to scan and analyze the details.  He had hoped to find nothing to justify leaving, but that would not happen now.

Comm officer, prepare an FTL compod.  Include the scan data, analysis, and the most likely courses based on known Ozaran territories, probable incoming and outgoing FTL conduit coordinates, and recent intelligence reports.

A young woman with short black hair turned and to the captain, Sir, the FTL conduits were in the same area.  Whatever came here didn’t continue.

Captain Curtis pulled up the data on the system where the sensor ghost leading to his orders was identified.  The improbable had happened.  Along the projected course, there was only one logical target for the Ozarans.  And they’re practically defenseless, he thought.  Whatever they would send, sooner or later it would come through this system.  The last system they would have to leave FTL for a final course adjustment.

He sat in the command chair and activated the ship wide comm.

“Attention all hands, this is the captain,” he began.  “We have confirmed a recent enemy presence and are in the process of informing Tactical Command.  We will continue to patrol this system at general alert status until reinforcements relieve us or we receive orders to leave.”

Captain, the compod is ready, Captain Curtis heard from the communication officer.

Captain Curtis knew it would take nearly thirty days for the compod to reach its destination and another thirty days to hear a reply.  If reinforcements would come, it could take days longer for them to arrive, assuming there were any ships close by.  Even when the first ship, or ships, arrive that would not mean Reliance would be relieved.  But for at least the next sixty days, they were the only line of defense.

For twenty days, Captain Curtis kept his crew occupied, running combat readiness and emergency drills.  For the last five days, the captain instituted a competition recommended by the first officer for each of the four watches.  Each watch crew was given the same exercises, and the crew that displayed the best readiness won.  The first officer’s watch crew won three times straight and Captain Curtis was determined to break that streak.

“This is the captain,” he boomed over the comm. “Prepare for drill zero two six.  We’ll start with precision firing tests and follow with simulated targets.  Remember, you’re the captain’s watch and as captain, I should not have to settle for second in anything on my ship.”  He eyed the bridge crew, not needing telepathy to feel their tensions.  “When we have won the next five competitions, I will personally buy each member of this watch a flask of Ozarian ale.”

Cheers erupted from the bridge.  Ozarian ale was a favorite of military personnel for years even though aside from having the look of Ozaran blood, there was no other connection to alien enemy.  Captain Curtis remembered the story that when the first barmaster introduced the non-alcoholic beverage, he marketed it under the idea of drinking the blood of an enemy after a victory.

Bribing the crew, Captain? The first officer mused.

A good captain knows how to motivate the crew,  Captain Curtis replied.  Besides, I heard you promised three days of R&R for each competition your watch wins a majority of the competitions.  You know, it’s my duty to approve, or deny such requests. 

The first officer smiled and walked off the bridge leaving Captain Curtis to his war game.

“Contact, port-side, twenty five degrees positive on the dorsal side,” called the tactical officer.

Captain Curtis head snapped in the direction of the tactical station.  The simulation he selected started with contacts to stern.  Tactical officer, confirm simulated or real contact.

“It’s real, sir.  The simulation hasn’t begun yet,” the tactical officer replied.  “FTL conduit forming twenty five light minutes from it.”

So whatever it is, it came through almost twenty five minutes ago, Captain Kerr thought.  “Battle stations!  Tactical, I want to know what we’re dealing with - size and number of vessels approaching.”

Intercept course Captain? the helmsman asked.

Captain Curtis shook his head. Hold position, helm.  I want to see if they turn to us or run.

I don’t understand.

If they run before we confirm their identity, it could mean they are a smaller vessel that could identify us first.  That could indicate they’ve made advancements in scanning technology.  We’ll send that information on.  Captain Curtis stared at the main viewer and the indicator highlighting the location of the FTL event horizon.  “Comm officer, prepare an FTL compod.  I want a live feed of all our transmissions, scans, and log entries sent to Tactical Command when we are within five light minutes of the incoming vessel.”

The next ten minutes passed in silence.  Then the tactical officer spoke up, “I have confirmation on the enemy ship’s course.  Ozaran medium cruiser is on course to through the system, zero point one five light and accelerating.  Based on current course, they’ll be able to go back to FTL in ten hours.  I’m projecting probable targets along their most likely FTL flight path.”

“I think we know the probable target,” Captain Curtis interrupted.  He knew the Reliance could easily overtake the enemy vessel, but did not want the Ozarans to know how easily.  “Set intercept course and accelerate to zero point two five light.”

We could intercept almost an hour sooner at zero point three light.  The helmsman sent his question telepathically because verbally questioning a superior’s orders was considered a violation of protocol. 

Captain Curtis knew everyone on the bridge had the same question, but only the helmsman deliberately shared it.  He’s opportunistic, but not pushy.  My kind of officer.  Captain Curtis tried to keep the thought sheltered from the helmsman’s telepathic mind.

“We’ll show the Ozarans what we can do soon enough.” This was the only response Captain Curtis shared.

Seven hours passed.  Ordinarily, the next watch crew would be ready to take over, but with only minutes until Reliance engaged the Ozaran vessel, the captain had ordered them to man the auxiliary stations.  Reliance was the faster, but the medium cruiser possessed greater firepower.

“Tactical, I want every scan detail you’ve done on that ship linked to my PDU immediately.”  The tactical officer complied without any reply.  Captain Curtis went through various details.  He confirmed the obvious weapon placements, seeing no blind spots to exploit.

“I want a readout of their power distribution.  Setup an overlay on the main viewer with real-time scans,”  Captain Curtis knew real-time was relative.  The scans would have the same light-speed based time delay, but by the time they reached engagement range, the delay would be negligible.

“Two minutes until we’re in weapons range, Captain,” the tactical officer announced.

“Helm, adjust course, ten degrees positive z-axis.  We’re close enough that if they drop mines I don’t want to run into them.”

“One minute until firing range.”

Color fluctuations through the Ozaran ship figure on the viewer caught the captain’s attention.  He knew what it meant even before the tactical officer spoke again.

“Enemy vessel is raising shields and powering weapons,” the tactical officer said. 

Captain Curtis could see from the power readings, not only did the Ozaran ship outgun Reliance, it had more powerful shields.  We have to hit them first and it has to count.

“Helm, take us to zero point three light, maximum acceleration.  Tactical, raise shields and ready weapons.”

“Yes sir,” both officers replied.

Seconds later the tactical officer called out, “Enemy ship is firing.”

Captain Curtis watched the tactical readout as the energy weapons and missiles passed behind Reliance, where the ship would have been had they not accelerated.  He programmed coordinates into his PDU and transferred them to the tactical station.  “Aft ventral thrusters, bring us perpendicular to the enemy vessel.  Target all forward weapons on these coordinates and set to fire.  Set helm to automatically reverse engines as soon as the first salvo of missiles launches.”

Thirty seconds later, the exchange of fire between warships began.  For a long five seconds the shields on both ships flared colorfully as they disbursed energy absorbed from incoming fire.  The power surges briefly distorted the display on Reliance’s main viewer.

“Damage report,” the Captain Curtis called.

“Forward shields down forty percent, FTL system damaged,” replied the crewman at the engineering station.

“Status of enemy vessel.”  He could see most of the information on the main viewer, but wanted confirmation of details.

“They’re shields are weakened and a minor hull breach near a dorsal weapons emplacement.  I’m also reading fluctuations in their power output,” replied the tactical officer.

Captain Curtis nodded.  The power fluctuations were significant.  He knew the Ozarans were trying to re-route power to firm up shields in the damaged section, but to do so would require drawing power away from other areas, leaving them more vulnerable.

“Helm, get us back into firing position for the same target.  Keep us on a parallel course.  Tactical, as soon as we’re in firing range, target their engines.”

“Yes sir,” replied both officers.

“Thirty seconds until weapon’s range,” the tactical officer announced.

Captain Curtis watched the enemy vessel larger on the main viewer.  He gripped the armrests on his command chair as Reliance began firing.  The Ozaran ship’s shields flared, disbursing the energy of the attack throughout.  The view looked like a series of rainbow waves rippling through the shields.  To the captain’s surprise, the light show stopped quickly.  It could only mean one thing.

“Helm, evasive full starboard!  Tactical drop mines!” he shouted.  Sudden explosions rocked Reliance hard enough to throw Captain Curtis from his chair and to the deck.  He heard commotion throughout the bridge as the crew scrambled to get back to their stations.

“Report!” he ordered.

The crewman at the engineering station was the first to reply.  “Bridge computer is inoperative, Captain.  We’re blind here.”

That was not a report Captain Curtis could accept.  He retrieved his PDU.  “Auxiliary control, this is the captain.  Bridge systems are down.  Report status.”

Moments later the familiar voice of the first officer replied.  “Main engines down to seventy percent capacity, ventral shields down, and we have multiple hull breeches.”

“What happened?”

“The Ozaran reversed engines as we fired on them and they hit us hard as they passed below.  Our automatic targeting system compensated enough to maintain eighty percent targeting efficiency.”

“What’s the status of the Ozaran vessel?”

“I’d have to say we gave as good as we got.  Their dorsal shields are down and their bow shields took severe damage when they collided with a couple of mines.”

“I’ll be down there in a minute.  Bring us around and protect our ventral side.  Have a medical crew report to the bridge to tend to wounded.”

“Yes sir.”

Captain Curtis ran from the bridge and into an elevator, keying the command to take him to the auxiliary control deck.  Two decks before reaching the destination he felt himself thrown into one of the elevator walls.  We’re hit again, he thought.  He quickly realized the elevator had stopped.  He tried the override, but it did not respond, so he opened the control panel and pulled the emergency release lever forcing the hatch to move slightly.  He continued pumping the lever until the hatch slid open enough for him to squeeze through.  Lights flickered in the corridor as he went to the emergency access conduit barely ten running paces away.  He slid the manually operated hatch aside and climbed into the conduit, using its ladder to climb down the last two decks.  Moments later, he arrived in the auxiliary control room.

“Report,” he called as the crew turned to face him.

“We’ve both made another pass on each other,” the first officer began.  “We were able to hit their unprotected dorsal section with particle cannons while keeping our ventral side protected.  We’re reading more power fluctuation in the Ozaran ship.  I think we’ve damaged their main power systems and they’re trying to re-route backup power.”

“They’re almost in weapon’s range, coming directly towards us,” another crewman announced.

Captain Curtis turned his attention to the viewer as the Ozaran ship closed.  “Helm, full reverse for fifteen seconds, then I want full forward acceleration and starboard thrusters.  Tactical, program firing solution with forward and starboard weapons.”

The crew complied with practiced efficiency.  Shields lashed again and the power surges again created distortions in the viewer.  Then a crewman turned to the captain and first officer.  Horror covering her face as she reported, “Sir, enemy vessel has fired their port maneuvering thrusters.  We’re on a collision course now!”

“Emergency evasive!  Sound collision alert!” the captain shouted.  He quickly realized his ship’s inertial dampeners had also sustained damage as Reliance’s helmsman complied with his orders.  The captain nearly lost his footing, stumbling forward a step before regaining his balance.  The emergency klaxon sounded throughout the ship as the two vessels closed. 

“Put the enemy vessel on the main viewer,” the first officer ordered.  Almost as soon as he finished speaking, the Ozaran vessel appeared. 

It was so close that the ship filled the viewer.  Seconds later, both ships began firing.  Captain Curtis imagined that, from the outside, the weapons fire between ships so close would look like a solid sheet of multicolored energy between them.

Again, Reliance lurched under the impact of the enemy weapons.  Captain Curtis realized that, at such close range, targeting efficiency was irrelevant.  There was almost no chance of missing. 

Power surges overloaded most of the displays and systems in the auxiliary control room.  He looked at the functioning displays at the tactical and engineering stations to see the impact points on his ship.  He realized that the only reason they could survive was that as the helmsman implemented the evasive maneuver, he has also fired maneuvering thrusters to keep the most heavily shielded section of Reliance facing the Ozarans.

The firing finally stopped and Captain Curtis made his way closer to the engineering station.  “Report.”

“It’s coming in slowly, sir” the engineer said.  “Main computer has taken damage, all shields are down, hull fractures across…”

Another series of explosions interrupted the engineer’s report.  His console exploded in front of him, leaving deep gashes and burns on the man’s face.  Captain Curtis, also cut and bleeding from flying debris, checked his crewman’s pulse.  He lowered his head and turned to survey the damage in the room.  A support beam had broken through the ceiling and killed the first officer.

“We’re hit again, Captain,” the tactical officer yelled.  “I don’t understand.  We were out of range and they couldn’t have maneuvered that fast…”

“They deployed more mines and we ran directly into them,” Captain Curtis replied looking at the wreckage.  If we sustained structural damage this deep in the ship, the damage must be vast.

He moved from one station to another trying to query the ship’s status and that of the Ozaran ship.  When none responded, he pulled his PDU and tried to link into the ship’s main computer.  It was slow, as the engineer said, but he began to retrieve some data.  Reliance had suffered catastrophic failure in its defense and drive systems.  The main power core was unstable.  All that was still functional was minimal sensors, emergency life support, and a couple of maneuvering thrusters.  Then he tried to access the sensors to determine the status of the Ozaran ship.  All he could retrieve was its general location, course, and speed.

“Helmsman, I need maneuvering thrusters.  Turn us seventy degrees to port.”

“Sir?”

“Just follow my orders,”  Captain Curtis said.  Then he went to the communication station, unsure if it worked, he tried a ship wide call.  “Damage control teams, focus on engines and weapons.  Emergency medical team to auxiliary control.”

Captain Curtis then turned and walked silently from the auxiliary control room.  He followed the corridor to a hatch with a sign that said “OBSERVATION LOUNGE.”  As he entered one of the few leisure rooms on Reliance, he sighed at the devastation.  The entire outer wall was made up of three clear plexi-panels allowing crew members to relax and watch the outside.  Metallic emergency panels now covered two of the panels.  Furniture and other items in the room were piled up against the emergency panel and the remaining plexi-panel as a result of the explosive decompression obviously suffered in the room.

A tear came to his eyes as he moved the debris from the storage compartments built into the far wall.  He finally retrieved a digital enhancing scope, typically used by crew members for stargazing.  But Captain Curtis had a much closer target to view through the scope.  He quickly found the Ozaran vessel and set the scope for maximum magnification.  The ship had split and the two major sections were adrift and tumbling.  He felt some satisfaction in the moments when the dorsal section faced Reliance showing hull breeches throughout.

“We gave better than we got,” he whispered.  He stared again and then frowned as he saw a projectile launch from the aft section of the Ozaran ship just before a series of explosions, beginning with the engines engulfed the severed section.  He knew immediately from the trajectory the projectile wasn’t a weapon. 

He set down the scope and pulled his PDU querying the computer for the status of their FTL compod.  He sighed in relief to see that it had entered FTL two minutes before the battle had begun.

Now we just have to hope that our compod reaches our reinforcements before theirs does.  He knew that was not the only concern.  The Ozarans, knowing their ship was destroyed would certainly send a larger force.  He hoped that, even though the compod launched from Reliance did not have data on the battle that his superiors would realize Reliance was lost and send a stronger force also.

An alert klaxon sounded again, followed by a garbled automated message.  “Alert, main power core overloading.  Failsafe is not responding.  All hands abandon ship.”

Captain Curtis did not leave the room.  He knew the escape pods could only store provisions and atmosphere for a few weeks and it would be at least two months before any allied ships arrived.  Any crewmembers who survived the explosion were almost certain to face slow death from starvation or oxygen deprivation.

He turned over a chair and pulled out his PDU.  He queried his personal files and looked though a family album.  Images of his wife and two adult daughters appeared.  He had hoped to make it home in time to see his youngest daughter graduate from her medical training.

 “I love you all,” he whispered continuing to change from image to image for the next seventy-two seconds.  Then Reliance exploded.

Now What?

Now that I've begun submitting my query letter and story to literary agents, the question is what to do now?  Writer creativity cannot live on editing alone, so I need to decide on my next project.

The first, obvious, project to consider would be a sequel to Legacy Soldier:  Hybrids Deployed.  While this does follow my personal favorite genre - military science fiction, it also has some disadvantages.  First, military science fiction is not exactly a fast-growing area.  In fact, as many experts have pointed out in articles and blogs, it's on the decline.  A second issue is that if the goal is to get published, should I devote my time to continuing a series when the first hasn't been published?

Fortunately, I have many voices in my head.  But the problem is figuring out which has the most marketable idea.  I've had online discussions about this on a few forums, and typically get the same response - just write something.  To me, it's not that simple.  Most of the advice I've gotten has been purely from a writer's perspective and it seemed to be about continuing the art.  It doesn't matter what I write as long as I write.  But the ultimate goal is to publish, right?  While writing is an art form, publishing is a business. 

So what are the top choices?  I have an epic fantasy that I shelved for working on Legacy Soldier.  The fantasy is started, but being epic fantasy, it's very complicated - world building and plot details.  I might have more luck with something a bit less complicated.  That and, like military sci-fi, epic fantasy doesn't seem to be a growth market for rookies.

I have two voices in my head that are probably twins.  Seriously.  They're "pitching" an urban fantasy and urban science fiction murder/mystery story.  The fantasy protagonist is a college student who's mother is a criminal investigator/profiler.  The science fiction protagonist is the profiler.  Naturally the other detail is that the student has an ability that she must learn to use (been using it for years, but never understood it) helping her mother with an investigation.  The profiler in the science fiction version is introduced to a new technology that she must learn to fully utilize.  I don't have a name for the fantasy story, but the sci-fi version would be called TIA (an acronym, not a name).  One thing to consider here is that I could open this with the hint fiction I posted from the December blog chain.  It seemed well received.

The last one is, and I don't believe I came up with this one, an urban fantasy/alternate reality story that has the US in a civil war - humans vs. werewolves.  The wolves have basically taken over the east coast, so I call this one Beast Coast.

That's just a few ideas.  I wish I could work on them all concurrently, but my son would graduate from college by the time I finish anything!  Like most people, I have a regular job to pay the bills, a family, I take and teach Tae Kwon Do, and when time allows, I write.  Right now, there's so little free time with the holidays and work that I'm not likely to make much progress until February.  On the bright side, Feb 18 - 20 is the TrekTrax convention here in Atlanta and I'm already signed up for the writer's workshop.  Maybe I'll have a chance to field some of my concepts by the pros and get an idea of how to prioritize.

So, I'll dabble where I can and...


Write On

Editing and Deleting 3

As I've already mentioned, sometimes a writer has to delete a section either because of a need to reduce word count or because it slowed the story/plot.  In some ways, the sections I'm going to post did a little of both.  My novel takes place several centuries in the future.  The main character is human, but one if his parents is from another world - a descendant of human colonists who left Earth centuries earlier, but ended up lost.  They eventually found a habitable world to colonize and called it Ganesha after the Hindu God of Success/Overcoming Obstacles.

I thought some readers might like a little on how their journey went, so I tested some early chapters with log entries from the colony ship.  The first entries were from the commanding officer, but I planned to add more from other colonists.  While my beta readers liked the idea, they said that it was a little distracting, so I removed the log entries.  Here are a couple of examples. 

Chapter 1 Log Entry:

“Prometheus log, September 19, 2104.  As of 0717 hours ship time, we crossed the event horizon and into the FTL conduit, becoming the first Earth colony ship to travel faster than light.  The transition was rougher than expected.  For a few seconds, it felt like every inch of my body was being pulled apart.  I spent the last hour listening to several colonists’ theories of how and why.  That’s what happens with a ship full of geniuses.”

“There were some injuries reported by colonists, mostly bloody noses, headaches, and nausea.  Nothing the medical team couldn’t handle.  Despite that, everyone seems upbeat.  Initial projections show we should pass Pluto’s orbit and officially leave our solar system within two hours.  Captain Matthew Morris, commanding officer.”

Chapter 2 Log Entry:

“Prometheus log, December 24, 2104.  After almost fourteen consecutive weeks in the FTL corridor, we finally emerged, but not where we expected.  Our navigator confirmed that somehow we ended up several thousand light years off course.  One of the physicists on board believes there may be an serious flaw in the design of the navigation system.  I have asked him to keep his theories to himself until we can run some diagnostics.  We are going to run a series of diagnostics on the system before we re-enter FTL. 

“This system has no planets capable of sustaining life, so we can’t even try to replenish any supplies.  We discussed stricter rationing of food and water as a precaution, but tomorrow is Christmas and I still plan to allow holiday parties for those who wish to participate.  Captain Matthew Morris, commanding officer.”

Chapter 3 Log Entry:

“Prometheus log, December 31, 2104.  We re-entered the FTL corridor at 0900 hours, ship time.  I don’t know if I’ll ever get used to that transition.  With all the bickering going on between the crew and colony scientists about what went wrong, it’s a miracle I didn’t have to call security to separate them.  As much as I respect and appreciate the colonists’ input, their expertise is still theoretical.  This ship is a working machine even if it is a prototype.  Hopefully the worst is behind us though.  Best estimates place our new arrival time at three months from now.  Hopefully it will be springtime at our new home.”

“Captain Matthew Morris, Commanding Officer.”

Feel free to express your opinions and

Write On

Work, trips, writing, and critiquing

Going through lots of changes at work and, for the first time in about a year, I'm going out on a business trip.  Personally, I'd rather stay at home.  However, as I tell people, first priority is to pay the bills and the paycheck writers say off to Lexington for the week.

The one advantage is that I should have almost every evening free to work on my writing and editing.  I was also recently contacted by someone else writing a story of a similar length and genre, so we are discussing an exchange of manuscripts for critiquing.  It never hurts to get another person to review your story. 

Most critiquing groups send one chapter at a time, so it can take over a year to complete a novel.  But, is we can agree to send entire manuscripts we could not only complete them quicker, but better.  Why better?  When you read one chapter every 2 weeks or every month, you tend to forget what happened earlier.  Exchanges of this nature could lead to more consistent critiques and better critiques of the story as a whole.

Check back soon.  I'll be posting some "deleted" sections of the story.  Comments and questions will be welcome.