All posts by David Todd

Book Review: DUNE

Dune by Frank Herbert, 1965, The Berkeley Publishing Group, Special markets Hardcover September 2005, ISBN 0-441-01405-4

How does one go about writing a review of Dune? It’s a massive job. I shall need three days to say most of what’s in my head. Imagine, therefore, how much more difficult it was to write the book in the first place. The achievement of Frank Herbert is immense. To create the planet Arrakis, with all its culture based on physical characteristics, and the worlds beyond Arrakis is a staggering work, easily rivaling the achievement of J.R.R. Tolkien.

I began reading Dune on June 15 this year, and finished July 19. As I said in previous posts (here and here), I found the beginning very hard reading. Herbert did not spoon-feed his readers. We have to figure it out from the barest of clues. On the first page I was confronted with the term Kwisatz Haderach, planets Caladan and Arrakis, the Atriedes family, and the curious term “suspensor lamp”. Strange words, strange concepts, hard going. I didn’t realize I had a “Terminology of the Imperium” section in the back. I assumed I had to figure these out from context or later illumination.

The second page presented the gom jabbar, Bene Gesserit, CHOAM, Landsraad, etc. The first five pages, even the first fifty pages, threw up one difficulty toward full understanding after another. I like to understand what I read. If I can’t figure out something from the context or internal explanation, I consult a dictionary, or even on occasion an encyclopedia. But where to go to understand Bene Gesserit? Nothing to do but read on and hope to figure it all out from accumulated context. I did, eventually, stumble on the glossary, and made frequent flips there. It wasn’t the most helpful, but consistent with Herbert’s aversion to spoon-feeding. I read fairly slowly, trying to maximize my understanding. Possibly the need to understand caused me not to focus on some plot elements, or the depth of character development.

Once I was past the first fifty pages, the extent of new terms diminished. Some others started to become familiar. I consulted the glossary less, and enjoyed the book more. The mind fog over Arrakis started to clear (and in so doing, I hope, provided something for the dew harvesters to collect), and the plot stood front and center. About the time Jessica and Paul had to escape from their Harkonnen captors (or were they Sardukuar?) was when I began to see the big picture.

On the next two days–I think; it could take longer–I’m going to cover what I liked and didn’t like about Dune. Today I’ll simply mention that I like the fact the book had no swearing, no overt sex scenes, and little violence. Oh, there were wars, battles, and knife fights, but the covering of this was superbly done by Herbert, such that you almost didn’t know it was a violent scene. The violence was not gratuitous, and the book did not rise or fall on the violence. This, I feel, is a mark of good writing.

So I conclude today by saying put me in the camp of fans of Dune. Some day I will re-read this, and I don’t re-read many books. Thanks to my son for this gift, which has enriched me. More later.

Book Review: The Dark Side of Camelot

I finished Dune yesterday, but I’ll need a few days to write my review; it will probably extend over two or three days. So today I will review a book I finished shortly before starting this blog: The Dark Side of Camelot by Seymour M. Hersh; 1997; Little, Brown and Company; ISBN 0316359556.

I have read much about the Kennedy family: the assassinations, the presidency, the ancestors, and the descendants. There is no shortage of books in this subject, for the Kennedy saga combines much of what made America great: immigration, entrepreneuism, politics. However, as Seymour Hersh reports, a dark side also existed. Past books have touched on this to varying degrees, and most people today who dig just a little bit into the Kennedy story know it is not always pretty.

Hersh set out to focus on John F. Kennedy’s run for the presidency and his time in that office. He begins with recounting events from November 22, 1963. He focuses on what Bobby Kennedy did, how he immediately moved to hide JFK’s private files, put them under lock and key. He hid the president’s medical records, to keep the world from learning just what a physical basket case JFK was. As he says, “But it was the man closest to John F. Kennedy who needed to put aside his grief and begin immediately to hide all evidence of Kennedy’s secret life from the nation–as well as from the new president….” And, “The brothers understood, as the public did not, that they were just one news story away from cataclysmic political scandal.”

Kennedy’s legacy is one of liberal strength, of diplomatic successes, of great speeches and hard work, etc. Hersh is able to pull the mask off the true JFK and unravel some of this unjustified legacy. Most people have heard about his womanizing, but the extent of moral depravity in our 35th president is astounding. After a late start in the Oval office most mornings, Kennedy would eat lunch there when Jacqui was away, then would go to the White House pool for a naked swimming party with some of his aids and White House secretaries. Hersh explain how when Kennedy was on the road, his aide David Powers was responsible for procuring the hookers who would fill the evening for JKF and others. As a consequence, JFK had round after round of venereal disease, and took massive doses of antibiotics, as well as steroids for other ailments.

Hersh does not confine himself to Kennedy’s personal life, however. Clearly documented are: the purchasing of the Democratic nomination in 1960 with the help of the Mafia and Daddy Kennedy’s money; the probable stealing of the election in November of that year; the bumbling approach to State issues, where every action was couched, not so much by what was best for America, but by what was politically expedient; the cavalier attitude to the Bay of Pigs invasion by Kennedy and those around him; the way they (JFK and RFK) almost threw away victory in the Cuban missile crisis; and Kennedy’s true plans for Vietnam. It is all an incredible revelation.

Hersh wrote his book at exactly the right time. The 1990s were thirty years removed from the presidency that the media called Camelot. Many of the people–the little people no one ever heard of, and the aides to aides–who played a part in the presidency were still alive, and enough years had passed that they were ready to talk. Secret service men spoke freely about how they felt about having to stand outside hotel suite doors while the president was consorting with prostitutes. Those involved in various diplomatic “successes” talked about the truth of the crisis and what the Kennedys knew.

The book has some flaws. It is not documented with rigorous footnotes to sources. The end of the book has “Chapter Notes”, wherein Hersh tells of his sources, who he talked with for each chapter, and the nature of what he learned. The way the book is written leads me to conclude it is accurate; I’d just wish he’d have done more footnotes. Then, there is Hersh’s habit of saying, “In an interview for this book in…”. After the first half dozen times we get the picture that he conducted extensive interviews. After 100 times it was annoying. After 500 times….

This is an excellent read. I encourage all to read it, especially if you still believe JFK was a great president.

Sidelines Syndrome

I first encountered Sidelines Syndrome when I was in junior high, a skinny lad who loved both academics and sports but who excelled only at the former and struggled with the latter. I didn’t know what to call it then.

I experienced it mainly on Sundays, in the fall, and it continued strongly all the way through high school. We went to mass at 9:00 AM, and got home around 10:30 AM or a little later. Cereal and toast were consumed, Dad fell asleep either on the dining room floor or in his bedroom, and it was time to read, do homework, or watch whatever pre-game football shows they had on in the 1960s. Eventually the game itself would start. How great it was to watch the New York football Giants, with Y.A. Tittle and later Fran Tarkenton at quarterback, Homer Jones at flanker, and…others whose names I can’t remember. I think Frank Gifford may have already retired. But I prate.

However, by the end of the first quarter, I was tired of watching and wanted to be doing. So I turned off the television, went outside, and started playing basketball alone. Not sure what my younger brother was doing; perhaps he sometimes joined me in the wide part of the driveway, next to the detached, two-car garage, where Dad had put up the hoop and backboard. Within a half-hour, certainly before the end of the first half, my neighbor Bobby, same grade as me, would come out and we’d have a friendly competition. An hour later and we were throwing the football in the street. Other neighborhood kids would join us, and we started a pick-up game in the street. The “field” stretched three telephone poles, the middle pole being the first down. It was always Bobby and me against all the others, all much younger than us. Bobby was Fran Tarkenton and I was Homer Jones. The ten or fifteen kids we played against didn’t stand a chance. But again I prate.

Sidelines Syndrome, as I define it now, is the physical or psychological reaction of body, soul, and spirit to being on the sidelines rather than being in the game. As teenagers, SS caused us to have an overwhelming urge of needing to be in the game, not watching others play the game on television even if they were quantum leaps ahead of us in skill and ability. We had to be out playing, not watching. I’ve noticed that SS has the exact opposite effect on us as we age. Instead of wanting to be in the game, we are glad to be on the sidelines; it lulls us to complacency, tiredness, and an overwhelming desire to sleep through half the game. At least it does me.

Last night, I experienced my first case of teenager SS in years. After working late, I went to Barnes & Noble to read, relax, research, and drink that large house blend that I mentioned in yesterday’s post. I began reading Noah Lukeman’s The First Five Pages. I read about ten pages, then felt an overwhelming urge to be writing instead of reading about writing. I couldn’t concentrate. So I put that down and began reading in The Complete Idiot’s Guide to Writing Poetry. I managed to research one minor topic, then SS interrupted the neurotransmitters and I had to lay it aside. Next was a book about fifty skills a writer should have, or something like that. I couldn’t get past the table of contents. The same was true with “Poets and Writers” and “Writers Journal” magazines. Concentration was impossible. I had to be writing.

So I went home, fixed dinner, went to my reading chair, and began planning out what I think will be my next book, a Bible study, and doing some research on it. SS was satisfied, my brain fully engaged, and productive words and concepts flowed. As the evening progressed and way led on to way, I quit about 1:15 AM, a blog post made and three sell-sheets drafted for three future books. I was satisfied; my brain was satisfied, a teen-age type attack of SS fully suppressed, and a 5:55 AM alarm setting turned on. Hey, maybe I’m getting younger!

Don’t bother to look up Sidelines Syndrome in a medical book, or Google it, or check it in Wikipedia. It doesn’t exist as a clinically defined medical or psychological phenomenon. I assure you it exists, however, and needs to be dealt with in the right way. Maybe this post will spur those professions to get off their duffs and figure this out—quickly. I can’t take many more nights of less than five hours sleep.

Something New

Today I gave the beginning six chapters, thirty-four pages, of In Front of Fifty Thousand Screaming People to my key beta reader. He is not a writer, or a critique group partner, but rather a rabid baseball fan. He read the first two chapters a couple of years ago, and loved it. From time to time he’s pestered me about where the book stood, if I was writing any more. I had to keep telling him no, so far life and other writing projects were in the way. We’ll see what he says about it. I thought of another man I could give these chapters to and see what he thinks about it. I may e-mail them to him tomorrow.

Meanwhile, I worked late tonight (till 6:30 PM) due to having taken time off during the day to run an errand, then went to Barnes & Noble to browse the writing books and magazines. I sat for two blessed hours with three books, two magazines, and a large house blend, and had a wonderful time. I took a few notes from two books of references I will use in an on-line poetry workshop I’ll be facilitating in a month’s time.

But about a week ago, as if I didn’t have enough writing related stuff to do, I began a new project, a new Bible study. I just finished teaching “The Dynamic Duo: Lessons From the Lives of Elijah and Elisha”. This is one of the projects I pitched to an editor at the Blue Ridge conference, and for which he wants a proposal. I have a lot of work to do converting my weekly handouts into passable sample chapters and writing the proposal, but my mind cannot focus on that right now, not until I have the FTSP proposal out the door.

However, I needed a project–something mainly for the future–to fill in the odd half hour when I don’t feel there is enough time to work on one of my major, current projects. Since I co-teach an adult Sunday school class, and it will at some time be my turn to teach again, and since I enjoy developing and teaching my own material rather than something prepared, I’ve been exploring what I will teach next. And, since preparing these studies seems to be something I can do, and something that editors might be interested in, I am approaching this new study with the idea that I will write the whole book before I teach the study, rather than just have handouts and expand them into a book later.

So, I have begun planning a study with the tentative title “From Slavery to Nationhood: How God Used the Forty Years of Wandering”. It will come from Exodus, maybe Leviticus, Numbers, Deuteronomy, and perhaps a wrap-up lesson from Joshua. I’m planning a study that could be taught in from about eight to about sixteen weeks, depending on how a given class wanted to do it. So I’ve read selected chapters in Exodus and Leviticus, and most of the first twenty-one chapters in Numbers. Based on my reading, I already have sixteen potential lessons. I think, by the time I finish, I’ll have about twenty. Then I’ll have to cull out the weaker ones, and begin the actual lesson prep. That’s really the fun part. I get to combine detailed Bible study, research, and writing into one package.

I will probably teach this beginning in January, so I’ve got some time, but not much. Meanwhile, ideas for another umpteen Bible studies are beginning to compete with novels and non-fiction books and historical-political newspaper columns for space between my ears. At least I know ideas are not a problem.

A Productive Evening

My wife is gone again, with our daughter and son-in-law in the big OKC, tending to our grandchild. When she’s gone, I try to maintain our normal routines. I found out I sleep much better that way. So last night, I fixed and ate supper first thing, but instead of then going into the living room to read (as we normally do), I went straight to the computer in the “Dungeon”, as we call our computer room, intending to do some personal business stuff. I found out I couldn’t do the task due to lack of the necessary papers, wasted a bit of time on computer games, and headed back upstairs to read. Twenty pages later in Dune, and I was ready for the Dungeon again.

The project: make some more progress on In Front of Fifty Thousand Screaming People. I had hoped to have the proposal ready to send last Thursday, so I’m obviously behind on my intentions. The actual proposal document is done, subject to tweaking and expansion of the competition section. What I lacked was about five pages of text. I’m supposed to have the first thirty with the proposal, and I only had twenty-five.

Even though I have outlined the book, so that I know the major events that must take place to put my main character into the cross-fire at the World Series (more on that someday, perhaps), I have not outlined it to the point where I know each scene. Those are coming as I get the inspiration, still switching gears from non-fiction to fiction. I have two scenes out of sequence, later in the book, mostly finished, but I needed that next chapter, that next scene, to have the full thirty pages to send. Plus editing, of course.

Last night I couldn’t seem to concentrate on the task at hand. I got some other things done, such as filing, organization, reading writing blogs, re-read the last chapter in sequence and did a few edits. But what to do with that elusive scene wouldn’t materialize. Should I switch to one of the Mafia Dons, and have them going through the routines of business? Should I do a scene at the farm in Kansas, how the family was reacting to Ronnie’s success? Or should I do another baseball scene? None of these seemed right at that point in the story. I thought of scenes later in the book I could work on, but that wouldn’t get me where I needed to be as soon as possible. Was this my first case of writer’s block? Computer games became a diversion.

Then, about 10 PM, the perfect next scene hit me. I’ve been intending to have Ronnie, the main character, interact with a reporter for the Chicago Tribune, a man I’d introduced briefly in the second chapter. Why not have their first one-on-one interview now. I was immediately taken to the Tribune newsroom, to the sports desk, where John Lind was trying to figure out how to interview the farm boy cum pitching sensation, and pounding keys.

At midnight, I had an almost finished Chapter 6, and was up to thirty-one or thirty-two pages at the start of the book. That put me way, way out of routine, for I don’t normally go to bed that late. When I went upstairs and to bed, my mind was full of plot and dialog, and no way could I sleep. Twenty minutes later I got up and went to my reading chair. I couldn’t face another chapter of Dune, so I wrote some in my journal, then picked up my Bible and read in Numbers, deciding on the next two possible lessons in my desert wandering Bible study. The words on the printed page were big and bold, the way they always are when my mind is sharpest. How could this be, a sharp mind at 1:30 in the morning? Nevertheless, I had a great time until tiredness came over me in waves about 2:00 AM.

I used to think my most creative time was between 10 PM and 2 AM. Years ago this manifested itself in solving all kinds of engineering problems I took home with me. Then the routines of life crept in, and I no longer worked on creative things at those hours. Is a change coming? Stay tuned.

When friends fall out

In my continuing (and slow) reading of John Wesley’s letters, I came today to his April 27, 1741 letter to George Whitefield. Whitefield was in Georgia, America, and has written Wesley on December 24, 1740, a letter that appears to have been critical of a number of things Wesley was doing: handling money, deeds for properties, ‘adornment’ of sanctuaries. Most important, however, seems to have been the growing rift between the two over doctrinal issues. Wesley was an Arminian and Whitefield a Calvinist concerning the issue of the permanency of salvation.

This difference must have been under the surface, or seemed unimportant, as the two began the great work of the revival. Certainly, it is hard to imagine Whitefield begging Wesley to come to Bristol to substitute for him in a revival that was breaking out there (Whitefield having to be elsewhere) if he thought Wesley to be in error in his doctrine. I just now found Whitefield’s letter on line, but have not yet read it. It contains five main points spread out over twelve pages of twelve point font, so it looks like I have lots of interesting reading in the days ahead. I will likely add this to the Wesley letters book, so that I have the full impact for when I read these again, perhaps in a decade or two. Apparently, Whitefield had the letter published in London, with a wide distribution.

Whatever their differences, and whoever was at fault, I’m saddened to see these two giants of the faith have a falling out. Somehow we have to make room in our hearts for those who interpret the gospel differently than we do. For Whitefield to have said Wesley preached a different gospel, and so they could have no fellowship together, seems extreme.

When Paul and Barnabas had their famous falling out, the result was the work was multiplied: two missionary teams went out, with more workers, than would have happened had they stayed together. Later in life, these two giants of the apostolic church were reconciled in friendship. Their dispute was over administrative issues, not doctrine, but still, could not Whitefield and Wesley have looked to their example? Well, maybe they did, sort of, for they divided their efforts.

I have much more to read on this, and possibly will come back and modify this post or make another.

20 More Pages in DUNE

I didn’t read any in Dune last night or the night before, but I did tonight, after returning home from writers critique group; twenty pages, bringing me up to page 316. My edition has 515 pages of book, plus about 30 of appendixes. Tonight I read when Paul and Jessica are accosted by a group of forty Fremen, but are able to work their way out of it and to gain the protection of this desert community. These were two nicely written chapters (found one typo; just a missing close quote). Paul quickly becomes enamored with a Fremen girl his age, and his mother seems to have an opening for a romantic relationship with the leader of this group.

In the next to last scene, Jessica takes advantage of the superstitions planted around the universe by the Bene Gessirit, and as a result we see a Fremen religious ceremony. I found this scene hard to follow. My mind drifted off twice, and I had to re-read to get it; even on the re-read I found it tough. I don’t know if that was the writing or just a normal (for me) aversion to pagan religious stuff.

Despite that one difficulty, the book continues enjoyable. Hopefully I can cover the remaining 200 pages in not more than 20 days, and come back to give a full report.

DUNE: the half-way report

Yesterday I reached, and today I passed, the halfway point in Dune, Frank Herbert’s 1965 science fiction novel. My son gave this to me for Christmas (or birthday; they’re pretty close together), and about three weeks ago it finally came to the top of the pile. My son gave it a good endorsement, saying it helped to define, or maybe it was change, the science fiction genre. I’m not much of a science fiction or fantasy person, but with that endorsement, and trying to please him, when it came to the top and it was time to read fiction, I plunged.

The first fifty pages were very hard reading. So many terms to learn, so many flips to the glossary. So much going back to re-read paragraphs that didn’t seem to make sense. Actually, this went on for closer to a hundred pages (my version is 540 pages, including appendixes). I found myself unable to read more than five to ten pages a day.

After a while, though, I fell into a rhythm, and began to find the work enjoyable. Some terms started to become familiar; others could be deciphered from context. The main plot line became clear, and the characters became real. The writing is stellar, and this book has one thing I really like in a book: omniscient narrator point of view. In all my writing instruction sources, they say omniscient is out of favor, and new writers should avoid it. As a reader, however, I prefer it, so why wouldn’t I write in it? Tonight I finished a chapter where Paul and his mother are the only characters in the scene. In one paragraph we are in Paul’s head; in the next one in Jessica’s. And I say, “Hallelujah!” What an exciting way to write. The caution against head hopping is, IMHO, way over stated.

Back to Dune, I can’t imagine how much time it took Herbert to create this. It seems more fantasy to me than science fiction. Possibly these two genres frequently merge when the science fiction is so far out there to make Earth invisible. His creation of the desert situations–the sand worms and the Fremen and stillsuits and the whole concept about water conservation is outstanding. The empire, with the tripartite arrangement between the royal house and the guild and the leading families, which has barely come out, is an interesting foundation of the plot. Back story is worked in expertly by Herbert.

I’m on a roll now, reading twenty pages a day or a few more. I’m anxious to learn how Paul and Jessica return to civilization; how Thufir Hawat learns who the real traitor is; what the emperor’s gambit is; etc. A few things I question, but imagine they will be explained later. For example, the last chapter I read this evening told of the death of Kynes, the Fremen planetologist who served as the judge of the change. Given that he died, and will have no more part in the story (unless he really didn’t die; we don’t have a corpus delecti yet, and I always maintain until you have the corpus delecti you don’t have a death), why did Herbert spend so much time on the death? Was it just to work in some of Arrakis’ physical characteristics, which Paul will pick up on later in this (or a subsequent) volume? The weeks ahead will tell.

Worked a Plan

Yesterday, before making made my late afternoon post, I made a writing to-do list. This included a couple of e-mails not strictly writing related, a couple of over-due replies to old friends. I did those, then tackled the list. As I completed each one, I recorded them in my writing diary with the time. Actually, making a post to this blog was one of the early items on the list, working on In Front of Fifty Thousand Screaming People one of the last. By the end of the evening, all but one item on my to do list was done, and FTSP was more than 2,000 words further along. My dreams last night were of a completed novel.

I’m not a big fan of to do lists. Oh, I write them, not so much to guide me in what I have to do but to help me to realize all that I must do, to help not slack off before I have enough done. That was the purpose of yesterday’s to do list–although I did tackle it in the approximate order I wrote it down.

Today I faced a different problem of work, another time of shifting gears. Returning to work after a weekend for me is always difficult. Not that I don’t like returning to work; rather, that the weekend away from work causes me to be inefficient when I return, doubly so after a holiday weekend. I have one main project I need to complete ASAP, a flood study that refuses to cooperate with me. Consequently I’m looking for any excuse not to work on it. But, knowing I should work on it, I bring it to the table and try, but find myself allowing distractions to enter in. I’ll waste time on the Internet, even writing stuff or Christian studies stuff, I’ll read technical magazines I don’t have to read, I’ll organize over and over, etc–anything to not work on the difficult task.

I knew I should work on it today, but also knew I would be terribly inefficient if I did. I needed something to work on that would allow me to work efficiently and stick to my work during the time my employer pays me. As I made the 24 minute commute this morning, the perfect task came to mind: write a construction specification section from scratch. This is part of my self-start stuff I always have trouble starting, to keep up with standards. Yet, I love writing specs. It’s about the most favorite part of my job. I’d rather be writing a spec for a specific project, but there’s a certain satisfaction from taking a blank sheet and creating ex nihilo something the company really needs. So, after my devotionals, my reading in Wesley’s letters, and checking a few web sites (all of which happen before I’m “on the clock”), I began writing a guide specification for underground storm water detention systems, something we’ve been needing for a long time. In two hours I had the basic structure done, and about 80 percent of the writing for one of the eleven manufacturers that will be included in the specification.

Other scheduled activities got in the way, along with people needing assistance–always a welcome diversion, but I had a concrete task to come back to during the day as thirty minutes free came up. By 5:15 PM I had the one manufacturer fully specified and proof-read. Since much of what I wrote for that one manufacturer will work for the others, I’m really pretty far along for about a half day’s work. And I didn’t waste my employer’s time today, praise the Lord.

Of course, my brain is fried tonight. After reading twenty-some pages in Dune, and after an evening walk of about a mile, my brain is as tired as it’s been in a long time, and I’ve barely been able to complete this post. I feel a good sleep coming on. Will my dreams be of completed novels, Bible studies in the planning stage, or underground storm water detention structures?

Shifting Gears

The month of June, what time I could spend on writing, was mostly on miscellaneous tasks that had fallen by the wayside for a while, and on pulling together the proposal for Screwtape’s Good Advice. With that in the mail last Wednesday, I turned my attention to the proposal for In Front of Fifty-Thousand Screaming People, my baseball thriller. I first started on the proposal, and tidied up the synopsis and wrote the sell sheet. Actually, I did some of this overlapping the SGA proposal, while waiting on my beta readers to respond. I did some market research, and figured out what books out now would be reasonably like mine.

Then I turned to, or rather returned to, writing the book. I began FTSP in June 2004, after pitching the idea to an editor at a conference. At that time all I had was a concept with some plot outline. He liked the idea, and said to send him a few chapters. So I quickly pounded out a prologue an two chapters and sent them. He still liked the concept, but wasn’t as thrilled with the writing as I would have liked. I set the book aside, partly not knowing what to do, and partly from the busyness of life.

Over the next three years I pulled it out and worked on it from time to time. I ditched the prologue, as the editor suggested, and polished the writing of the first two chapters. I added a third and polished it. I began a fourth. An idea came to me for a scene well into the book, which I thought would be about 2/3 the way through, and I wrote that. I worked on a plot outline and character development, writing page-long essays in the words of the four main characters, stating in their own words what their motivations were for the events in the book. But I did not do any serious writing, continuous writing for days in a row, as I had done with Doctor Luke’s Assistant.

Friday night I decided I’d better get back to this. The agent wants the first thirty pages with the proposal, and when I merged chapters 1, 2, 3, and the partial 4 I had only twenty pages. I figured out what to do with Chapter 4, and finished it as a short chapter. The plot analysis I had done as part of writing the synopsis told me I had to move the scene I thought would be 2/3 the way through to become the first plot point, meaning it needs to be 1/4 to 1/3 the way through. I did that, and made a couple of related changes. Then I sat down on Friday, Independence Day, to write the fifth chapter, intending to do serious writing.

Lo and behold, I couldn’t write it! I wrote “Chapter 5” at the top of a re-use page, then sat there, not sure what to do. My plotting did not get down to the level where I had to plan what the next chapter would be about. Yesterday (Saturday), I went back to it and managed to write about half a page. That was a start, but not the type of progress I needed to make. Was this a case of writer’s block, my first? I have had times when I was not motivated to write for various reasons, usually the whirlwind of life causing my brain to shut down for a while, but never have the words not come to me when I wanted them to.

After a while the reason for this inability to add this chapter became clear. For the last seven months I have been concentrating on non-fiction as a probable easier way to break into publishing, and purposely laid fiction aside. I brainstormed the SGA book and began it. I turned my Elijah and Elisha study into a potential book and brainstormed it. I thought about ten other Bible/small group studies I could write as follow-ups. A fruitful career as a writer of Bible and small group studies danced before my eyes in waking moments, and through the subconscious in sleeping moments. I had done no fiction writing at all, until after the Blue Ridge conference, with the interest of an agent staring me in the face, I at least read my manuscript and made some edits. I shared chapters 1 and 2 with my new critique group, and received feedback. Now that I’m ready to return to fiction, I can’t get my mind around it.

It’s hard to change gears between fiction and non-fiction–at least it is for me, this first time to do so. What will the future hold? If my career goes the way I want it to (at this stage of my “career”), I will be switching regularly between fiction and non-fiction. I’d better learn to shift those gears effortlessly, on a day to day basis if necessary. This will be especially true if I follow-through with plans to market and publish the Documenting America newspaper column.

Help! I’m a prisoner of a career that hasn’t even started yet.

The good news is that, as I fell asleep Saturday night, a scene late in the book came to me. I wrote it mentally lying in bed, then wrote it on paper Saturday morning. Today, while eating lunch, the way to write chapter 5 came to me, and I’ll be hitting the keys for that after I finish this post. So maybe the gears shifted over the last couple of days. May it be so.