Sunday, October 16, 2011
The Order of the Benevolent Souls
Friday, January 21, 2011
Sunday, August 1, 2010
Living in the Third Draft Editing Stage - Dialogue
I have long known that I am a lousy editor. I dread the third draft stage of any of my projects because I know that this is the stage in which I have to turn off more of the creative process and put on the editors hat. I will often read a sentence, make several grammatical or stylistic changes. Then come back the next day, only to read it and change it back to the way it was.
I’ve done a lot of research, and during the third draft editing stage of The Fenian Avenger I am summarizing some of those topics in my blog. My goal is that by summarizing it, it will cement the concept in my mind and make it more a part of my writing during draft one and two, and less of an edit chore in draft three. But, perhaps if I can present some of my research that can help another writer, then that is a great thing.
Dialogue
I’m starting with dialogue because my writing professor in college said that this was the strongest area of my writing. Now, let’s preface that, because it sounds warm and supportive, like the professor was a mentor and taking me by the hand and leading towards the oasis of being a published author.
I took a fiction writing course in college that was taught by a respected semi-best selling author. I had aspirations of learning from him. I was very transparent about my weaknesses as a writer, as teacher in high school really didn’t teach grammar or how to really write. But I had good ideas and a passion to make them come to life.
The professor’s assessment of my writing was quite simple, written in red ink at the bottom of page: A festering pile of s---. Poor characters. Bad descriptions. Unbelievable plot. Poor pacing. Dangling modifiers. Average dialogue. I wouldn’t read past the first paragraph.
Anyway, that professor ticked me off enough to fuel me for years to prove him wrong.
Average dialogue! Wow – that was almost a compliment.
Dialogue in a story is often mistaken for conversation. When writing dialogue, it’s not about catching every word that is said between two or more people. It’s about catching the essence of the conversation. That may be what is communicated. That may be what is not communicated.
Dialogue may be used to set characters apart from one another. The only distinguishing characteristics may be the way they speak. Following the scathing remarks from my professor about my writing, my stories became almost entirely dialogue, and thus characters had to be recognizable by their mannerisms in the words they choose, their cadence of their words, and such. Much of the sitcoms on television today are still based almost exclusively on dialogue.
If the story submitted to a busy screen contains a lot of dialogue. And that dialogue is snappy, confrontational, and intelligent. Then that screener may be more inclined to read more pages than they may have read if the text contained heavy block paragraphs of prose. However, if that dialogue proves to be clichéd or sounds dead, then screener will bury the manuscript very quickly. So, dialogue can help a story quickly, but bad dialogue can bury it quickly also.
Again, the dialogue in a chapter must have a purpose. Once again, it is not there for conversational reasons. Every chapter must have an agenda, whether it is one of four signposts that all stories are built on, or the journeys from one signpost to the next, each chapter has a purpose or an agenda. And the dialogue in that chapter must fit within that agenda or purpose.
For example, in Chapter 18 of The Fenian Avenger Reverend Fitzpatrick accompanies Eamon Malone to the funeral of his parents at Glasnevin Cemetary in North Dublin. Eamon is in agony, not just over the loss of his parents, but because of the fact that the man responsible was reading from Psalm 23 “The Lord is my shepherd…” Fitzpatrick offers Eamon comfort in their dialogue, and in Eamon’s dialogue he shows that despite his incredible gifts, he is still a seventeen year-old and has a lot of growing up to do. That is a lot to convey in dialogue, but I didn’t include the entire conversation, because it would not have advanced the agenda of the chapter. It would not have served any purpose for Fitzpatrick to thank the usher for showing them to their seats.
Tags are another item in dialogue that separate amateurs and professionals. Tags are the “he said” and “she said” after someone says something.
The rule that I was taught was that there is really nothing wrong with the word “said.” Whereas with other words it is said to avoid repeating words too often, with “said” this is not the case. It is a sign of an amateur when a writer finds different ways to say this.
All of these are signs of an amateur, and can be replaced with the word “said”:
…he whispered.
…he spoke.
…he retorted.
…he chuckled.
…he wondered.
…he thought aloud.
…he pontificated.
There are instances where you can skip the tag. If there are two participants in the dialogue, and their voices are distinct enough to tell them apart (which should always be the case with all your characters), you can hold a conversation without always adding the tag. When you do this, every once in a while, you will want to drop the tag in there just so your reader can re-acquaint themselves with where the conversation is.
Probably the best author I’ve ever read when it comes to dialogue was Gregory McDonald. McDonald wrote the Fletch and Flynn series, and if you’ve never read the books and only know the Fletch movies, you’re missing some great dialogue. The books are almost exclusively dialogue and are sharply written.
Sunday, January 17, 2010
Working Towards Fenian Avenger Second Draft in New Year

The last few months of 2009 were very active for me. In September, I set out with an ambitious goal. I wanted to come up with a completely new concept for a novel, one that didn’t involve an additional book in a series or calling upon my stable of characters and storylines. I wanted to complete the story treatment and outline by November 1st and participate in NANOWRIMO (National Novel Writing Month). For those not familiar with NANOWRIMO is a non-profit group that encourages writers to set a goal of starting and completing a first draft during the month of November.
That was quite a lofty goal. Assuming that I had a treatment and outline to work with, finishing a first draft is not out of the question. Finishing a draft is historically a very quick process for me. The time consuming (and probably most enjoyable) is the process of developing the treatment and outline. Some concepts of mine take years to get through this process. An idea hits me, and I take months just thinking about it, playing out scenarios in my head, and sometimes having conversations with potential characters in my head Yes, I spend a lot of time talking to myself (people who work with me are more than likely nodding their heads at this).
To do all of this in that short period of September 1st through November 30th would be an accomplishment.
To be fair, I did not allow myself to use any ideas I was already working on and I could not use any character that I have ever used before in another book or story.
I wanted to do some kind of adventure story. Something relatively light. I had just finished a story treatment that for In the Mind of Declan Murphy, which is a story about an autistic man who, in his altered vision, can clearly see the devil taking souls in his small Irish town, but he can’t communicate with anyone to warn them. This concept was very deep, spiritual, and abstract. And was quite a downer. I wanted this new story to have energy of its own, as that would help me get through this task.
I came up with the idea of an Irish super-hero, fighting corruption in a fictional depression-ridden
It was a fun story to plot. Coming up with an origin that had a mysteriously exceptional boy name Eamon Malone who is part of a new direction in child development and education (and potentially turning him into a weapon). After his parents are killed in an apartment fire after an altercation with the executives at the foundation in charge of educating Eamon, he finds himself alone on the street with only revenge on his mind. After an incident in St. Stephen’s Green where Garda officers are shaking down a woman, Eamon takes on the guise of the Fenian Avenger and dispatches them. He soon is taken in by his friend Angus to live in his subterranean home underneath the streets of
I was very pleased that going into the last week of October I had a working story treatment and outline. I was ready to go.
On November 1st I was off an running. With a detailed treatment and an outline that details signposts and journeys of protagonists, antagonists, and impact characters – the hard part was done. It was just a matter of making time to write. The story took a life of it’s own. I thought of many directions the characters could go, and tightening up the original treatment as I fully worked through some of the scenarios.
Some 63,000 words and thirty days later, I had my goal completed. I had finished the first draft up until the last five chapters. I never do the last five chapters in a first draft. I always like to re-read the draft after a period of time to make sure that the ending I intended to use is still feasible.
It’s a waste of time to set goals to write during the holidays. It just doesn’t lend itself to consistency. And consistency is the key to writing. Writing has to become a habit, and for it to become a habit, it has to be something that you do every day. It’s not enough to be a good writing; you have to practice being a good writer and pushing yourself to better yourself.
So, for the new year I plan to get back into the habit of writing. And events so far in the new year have a way of trying to get in the way of that. In addition to my wonderful weekly gift of chemotherapy to dislodge any momentum I had, I’ve had a flare of my painful conditions that require the chemo, and a case of strep throat that causes me to stop taking my chemo that makes my symptoms get worse.
For the second draft, my goals are: tighten up the plot, flesh out the locations and make them pop, try to get inside the head of a confused sheltered eighteen year old super hero, and adjust the story to get rid of the prologue (a certain publication killer), and a hole in the middle where a plot point didn’t pan out.
Second drafts are my least favorite thing about writing. I’m a lousy editor of my own work and have a habit of thinking my writing is either too good or too bad.
Wednesday, November 4, 2009
Happy Birthday - Ava Mae


Today is my daughter Ava Mae’s fifth birthday. She’s the youngest of our three children, the second surprise for us (with Lexi being the first surprise).
When we had our first ultrasound, they told us that Ava was going to be a boy. The second ultrasound told us she was a girl. Even though they promised us that they were pretty sure she was going to be a girl, I still wondered. But, they were right and Ava was a girl.
Now, here are a few facts about Ava Mae:
• She has, without a doubt, the loudest voice I have ever heard. Even when’s she’s whining, it’s loud. How can such a little thing be so loud.
• She will be featured someday on the TLC’s Hoarders. I thought I was bad, oh no, I’m just an amateur compared to her. Ava Mae has saved every scrap of paper that fluttered through her attention. I found old post-it notes that I had written on years ago stowed away in her room.
• Without an effort, she can be the life of the party, or…
• When she’s in a bad mood, she’s not content to just state her displeasure, no, she plans to take you and everybody else down with her.
• Ava Mae is the most likely to get Daddy in trouble. Sometimes its entirely accidental (accidentally telling Mommy that Daddy let her drink Diet Coke). But, there are those times where she gets me in trouble just to show me that she can. It’s as if she wants to make sure that I have no misgivings about who really runs this house.
• She is very much a hybrid of her brother and sister. Devin is analytical and will make a great engineer, scientist, doctor, or mathematician. Lexi is the head-in-the-clouds dreamer, very creative, life of the party, with her very own entourage of fans in tow. Ava is equal parts both of those.
• Ava loves ballet. She is obsessed with it.
• Ava is very anxious to start learning the piano. She can find middle-C faster than her brother and sister can.
• One of her favorite television shows was the episode of Arrested Development where Tobias paints himself blue to join the Blue Man Group. She always asks me to see the Blue Man episode. In fact, she has suggested that I write a story about Blue Man. I’ll get back to you on that one.
• On night, Ava stood up at dinner and recited the qualities that make you a leader. I tried to write them down – they were pure Ava-isms.
Being a leader is … someone who is nice to everyone
Being a leader is … someone who helps his or her friends
Being a leader is … brushing your teeth like the dentist says
Being a leader is … making sure have a fancy pony birthday party for each of your WebKinz
Being a leader is … singing songs about Jesus
Being a leader is … dancing to all the High School Musical songs
Being a leader is … being stylish
Being a leader is … going on the potty
Being a leader is … not pushing girls off the playground swings
Being a leader is … being a good line leader
Being a leader is … is being a leader
Being a leader is … going to Jacob’s house
Being a leader is … Lexi not letting me play hide and go seek
Being a leader is … not letting the aliens come into our house and take our faces off
Words to live by.
Monday, September 28, 2009
Happy Birthday Lexi - 7 Years Old




Sunday, September 27, 2009
The Code of the Eight - Chapter 1
Chapter 1
"In a few minutes a computer can make a mistake so greatthat it would take many men many months to equal it."
Merle L. Meacham
October 17, 1990
Washington DC
The early morning sun filtered rays of light through the partially opened blinds. The sunlight illuminated the office above a storefront in the Georgetown section of Washington DC. The office was decorated in ornate cherry wood, with dark hunter green wallpaper accented by cherry wainscoting. Matthew Barber held the phone to his ear, leaned on the sill of the window, and looked out over the streets of old Georgetown. The shops across the square were already active. On the corner, a shop called the Banana Republic had a steady stream of traffic in and out. Several tourists wearing khaki hats and coats exited the store. Across the street, a fight had broken out between several artsy people with shaved heads and pierced body parts and a man dressed in black leather.
Matthew Barber barely noticed the commotion below as he waited impatiently for someone to answer the phone. Barber was in his early fifties and wore a conservative dark blue suit that looked as if he slept in it. Indeed, the suit had been slept in for several days in a row.
Simon LeBaron sat at a computer terminal. He was furiously tapping away at the keys. Simon was a tall, thin man in his early forties. His hair was curly brown, with just a hint of baldness. He had spent several days staring at this computer monitor, his eyes were straining to see the screen. The green letters on the black background of the mainframe emulation were becoming a blur now. He rubbed his weary eyes.
"Return code of 00," Simon said as he read the TSO environment processing messages on the computer screen. "It passed to the CPU."
"Damn it," Barber said. "Did we even slow it down?"
"No," Simon said. "It's too sophisticated for me to stop with an ad hoc COBOL routine. Whoever created this knew what they were doing. We're talking about a JCL running a proc with an imbedded routine running an encrypted COBOL program. I can't even read the code the encryption is so damn complicated."
"Damn it," Barber said again.
"What about the hardware infiltration?" Simon asked.
"No answer yet," Barber said. "I don't know what the hell is..."
Barber stopped in mid sentence, spun away from Simon, and listened intensely to the telephone receiver. "You've done it? You've got it? Good job. Now get the hell out of there."
Barber hung up the phone. "They removed the hardware from the unit. Try the program again," Barber said to Simon.
Simon pulled up a screen filled with cryptic green letters. Simon typed over several of the variables to modify the “run parameters” for the change in hardware. When he completed the necessary changes to the edit screen he typed the word "SUB" at the command line at the top of the screen. The two men impatiently leaned over the terminal, waiting for the results.
"How long should this take?" Barber asked.
"It shouldn't be too long. I adjusted the params to zero in on an anomaly that I already know will happen."
"When this is all finished, I'll ask you what that meant," Barber said.
Simon typed at the command line on the top of the screen.
=S.DA OJOB G711UC1*
The computer screen changed to display the statistics of the program Simon had just submitted. Simon continued to hit the enter key to check the progress of the program. The top of the screen displayed the total amount of the CPU utilized. "I'm at an exception count of 619. It should end around 800. My program is chewing up the CPU usage. We're at 94% right now. It shouldn't be that high. I don't think that's a good sign. That could mean the encrypted code is multiplying exponentially."
"How long will that be before it's done?"
Simon hit enter one more time and the screen went blank. A message in red text appeared at the top left hand corner of the screen:
JESLIB JOB 9483 COMPLETED WITH CONDITION CODE 00
"It's still going," Simon said.
"It can't be, the hardware is no longer in place," Barber said.
"I should have thought of that."
"What?"
"It doesn't matter in this situation that the hardware has is gone. The host system has the program in resident memory in its CPU. It doesn't matter that the hardware has been removed. Nothing has happened to clear that program out of memory," Simon paused. "Because of its encryption, I can't touch the source code, nor can I touch the extract files it creates."
"Why can't you?"
"It's a production based job, that's our protection against anything in our standard jobs. We used to have problems with programmers changing programs in the IRS system to give them a lessened chance of a random audit."
"They really did that?"
"You bet, and they were getting tens of thousands of dollars back in refunds."
"Is there any other way to clear it out?" Barber asked.
"There is the way we talked about before," Simon said.
"That's dangerous."
"Yes it is," Simon said. "But so is allowing this to continue."
"Shutting down the entire system is the only solution?"
"Yes," Simon said. "Otherwise, the program will always stay resident in memory, because these CPU boxes are always running. They never get turned off. This system is unlike most others in our government main frame network. Because the banks and investment institutions rely on information from this system at all hours of the day, it never shuts completely down for daily maintenance. It simply shifts off certain modules for a few minutes at a time while it runs maintenance. It's a process that takes most of the day on and off."
"You realize the fallout, don't you," Barber said.
"I can imagine worse if we don't shut it down," Simon said.
"I can't even begin to imagine all the ramifications, the iterations, or the permutations that could result because of this. It would be chaos," Barber said.
"We have to," Simon said. "But, it's your call, Director Barber."
Barber sighed and shook his head. "Do it," he said. "Shut down the Federal Reserve System."
New York Times
Headline
October 18, 1990
Stock Market Crashes
Bloody Monday
New York (UPI) - The New York Stock Exchange plummeted to new lows yesterday. An inexplicable series of events sent investors and brokerage houses scrambling to sell stock as prices plummeted to new lows.
Not since the great depression or the market crash of 1987 has the market suffered so much in such a short time. Analysts and technicians are uncertain exactly what happened. It appears there was a glitch in some computer systems early yesterday morning. Computer systems in the large brokerage houses are set automatically to buy or sell based on certain events, such as low prices, or lack of funds within a customer's bank account. The systems had trouble accessing any of their customers account information within the Federal Reserve System. This action triggered computer systems of many brokerage house's immediately to initiate selling stock short. When all the brokerage house's system began selling, the entire stock market and other financial markets went into disarray. Stock prices began to plummet to lows seldom seen in this century, even for ultrastable stocks such as IBM, Intel, and Microsoft. All the time this was happening, the brokerage house's computer systems were still trying to sell, thus driving the prices deeper because of the surplus in the supply of stock...
Washington Post
October 18, 1990
Two Men Found Murdered in Georgetown Office
Washington, DC (UPI) - Two men were found murdered in a Georgetown Office Monday night. Both men shot at point-blank range to the throat with a .22 caliber weapon. The two men are unidentified. Authorities do not have any clues about the identities of the two men.
Police Detective Robinson said in a statement. "Fingerprints, dental records, personal belongings in the office, none of them give us a clue about whom these men were." The names in which the men used to rent the office space have also proven to be false and a dead-end. The company name that rented the office was Sarah Douglas Services, who took possession only the previous week, paying cash. There is no record anywhere of any such company. It appears that nothing was stolen from the office. The only damage noted was a destroyed personal computer.
Authorities currently do not have any suspects or motive in the killing...







