S. Evan Townsend's Blog, page 110

April 29, 2014

Writer's Don't Wanna

Yesterday I wrote about overcoming writer's block.  And then, later that day, I ran smack dab head on into writer's don't wanna.

What, you ask, is "writer's don't wanna"?  Let me explain.  I was working on my Work in Progress (WIP) which would be a fantasy/western mashup in the Adept Series universe.  After a bout of writer's block about the work, I had an idea to move forward, a great little plot twist and an explanation of why certain things happened in the novel I'd sort of not had a good explanation for, yet.  Then I decided I'd better go back and read what I'd written, all approximately 33,000 words, to ensure that nothing conflicted with my plot twist.

I got half-way through chapter two and just went "yuck."  I didn't want to do it anymore.  I didn't want to read anymore, I didn't want to edit anymore (which I was doing as I read it), I just didn't want to write.

This isn't writer's block, this is "writer's don't wanna."  And at the moment I have no words of wisdom for getting out of it.  And I'm a bit worried that if I don't want to read my work, no one else will either.  Maybe this whole fantasy/western mashup is just a bad idea and I should quit it and write something else.  Maybe I'm a lousy hack of a writer.

You see, it's fear and self-doubts again.  This is a form of writer's block.  The fear that it's NOT GOOD ENOUGH.

The only thing I can think to do is take a break and go back and read it some more.  Keep working.  Just keep writing (as I say over and over again).  Writing requires discipline (I've said that before, too).  Your first draft will be crap, get over it and write the damn thing.

So, obviously, I need to keep writing.  And not on this blog.

Later.
 •  0 comments  •  flag
Share on Twitter
Published on April 29, 2014 06:00

April 28, 2014

Overcoming Writer's Block

I once had writer's block for two years.

Now, admittedly I was working more than full time, I was busy with other stuff so I wasn't staring at a blinking cursor for two years.  But I could not finish Hammer of Thor , my first Adept Series book for two stinking years.  I had written almost up to the climax and could not force myself to write more.  I had the climax sort of planned out (as much as I plan out any writing in advance) but could not bring myself to write it.  For two long years.

Then one day it suddenly occurred to me: my plans sucked.  I realized I had plotted out a climax that was pretty anticlimactic.  My main character, who had just spent over 100,000 words getting to this place, was going to sit back and watch it happen.  I needed to get him into the action.  And when I got that figured out, I wrote the climax and denouement in a about a week of spare time (I was still working at my day job).

Now that was a special and I think unusual case of writer's block.  My subconscious was telling me "it sucks" so I never wrote it.  And it did suck so it was good that I never wrote it.

However, I think a great deal of writer's block is caused by our fear that what we are about to write will suck.  We let the perfect be the enemy of the good.  I've said over and over on this blog: your first draft will suck, get over it and write the damn thing.  Then you can fix it in edits but you can't fix it in edits if you don't write it.

As John Rogers said, "You can’t think yourself out of a writing block; you have to write yourself out of a thinking block."  Which is good advise, but sometime I think you can't even write yourself out of it.  If I'd gone ahead and written the climax of Hammer of Thor as I'd plotted it out, it would not be as good as it is now.

I have two methods of overcoming writer's block.  One is: just keep writing.  It might suck, but at least you're writing.  And if it does suck, fix it in edits (you do edit, don't you?).

The other method is to stop writing.  This is different from writers block.  Writer's block is when you don't write when you want to.  If you stop writing, you just stop because you don't want to write.  What good does that do?  It frees the mind from the pressure of producing.  It lets your mind wander and think about other stuff other than YOU'RE NOT WRITING.  And often this will after a short time, produce an idea that will get me past the writer's block (okay, two years was not a short time).

Last week suffering a bit from writer's block.  I am about half-way through a novel and I suddenly had no idea where to take it from where it was at.  So I stopped writing and let my thoughts wander and didn't think about it and didn't worry about it.  As I was driving on Friday on a 360-mile round trip, I had an idea.  This got me thinking.  Then I went to my writers' group Friday night.  It was a "writing writers' group" where you are expected to produce.  I sat there staring at the cursor not getting anywhere.  So I backed up a few pages and read what I'd written right up until I got stuck.  And I had an idea that built upon the idea I had while driving.  If I changed the villain from who it seem to be to a minor character, that would be a great plot twist, would solve so many problems I was having with the plot, and would let me continue.  I wrote down some notes on my thoughts so I could do a little thinking about where the plot should go from here (and I need to do a bit of research).  But I no longer feel as if I have writers block because I used both methods: I backed off from the writing, and then I was in a situation where I was forced to write.

The same thing happened in God of Strife , the fourth Adept Series novel coming out May 15th.  I was about half-way through it when I realized my planned plot for the rest of the novel was weak.  So I took a break, and a few days later had the idea that went on to complete the novel.

The more you worry about that fact you're not writing, the more you'll not write.  So either write and admit it might be crap that you need to fix later, or stop writing, stop worrying, and let the ideas flow.  One or the other method (or a combination of the two) should let you overcome writer's block.
 •  0 comments  •  flag
Share on Twitter
Published on April 28, 2014 05:00

April 23, 2014

All of the Empirical Data

It's raining today.

So what? you say.  You live in Washington State and it rains a lot.  Well, yes and no.  The western side of the state (west of the Cascade Mountain range) it rains a lot.  But I happen to live in the rain shadow of those mountains and we average 8 inches of rain per year.  Seattle got more than that last month!

So it's raining today and my thoughts hearken back to my 9th grade "Earth Science" class.  The teacher (who was a PE major in college) decided to demonstrate the scientific method using rain as an example.  He ask the class to pretend we didn't know rain came from and what facts could we observe to form a theory of where rain comes from.  One student said, "It gets cloudy."  Another offered, "It gets cooler."  Now this is empirical data, i.e., data that is observed.

So I said, very seriously, "It falls out of the sky."  And everyone laughed.  No, this is not about childhood trauma.  I am very used to, and was even then, being laughed at or ridiculed when I know I'm right.  Even in the face of authoritative opposition because the PE major laughed, too.

But here's the thing.  If it got cloudy and cooler and the water came out of the ground, you'd need a different theory than you'd have if it came from the sky.  That was an important empirical datum.  But to everyone else in that classroom, rain fell from the sky by definition.

This is why science is difficult.  You have to look at all the data.  And there might be data you're not aware of that you're not seeing because you're assuming rain always falls from the sky.  People often miss what is right in front of their eyes because it doesn't fit their pattern of thinking.  Or they see patterns where they aren't because of prejudice.

For instance, if you think people with green eyes are all idiots, anytime you see a person with green eyes being an idiot, it reinforces your prejudice.  If you see a green-eyed person acting smart, you dismiss it and often forget about it because it doesn't fit the patterns of your prejudice.  This is why scientists have developed many tools to eliminate prejudice and preconception and other facts of human nature.

So when you're looking at a phenomena, try to gather all the empirical data, even that you don't agree with.
 •  0 comments  •  flag
Share on Twitter
Published on April 23, 2014 08:00

April 22, 2014

Supersonic Molten Sulfur

Io with a volcano on the left side of the picture.For the Work in Progress (WIP) I'm just finishing up (I'm waiting on two more beta reads) I decided to describe the moon of Jupiter, Io, in greater detail than I had.  In The Treasure of the Black Hole my main character is talking about learning to pilot a spaceship around Jupiter and how difficult landing on Io was.

Io (pronounced eye-oh) is the inner-most Galilean moon, that is, one of the four moons discovered by Galileo in 1610.  Due to its proximity with Jupiter, tidal forces keep the moon's core molten and there are numerous volcanoes on the moon spewing molten sulfur.  Some of the volcanoes shoot the sulfur 200 miles above the surface.

So I decided I wanted to say in my WIP how fast that sulfur was moving.  This is an easy calculations and according to my college physics book (yes, I still have it), the formula is:


Where v0 is the initial velocity as it leaves the surface, h = the height it reaches, and g is the acceleration of gravity.  In computerese we write that: v0=sqrt(2hg)

For example, if you throw a ball straight up (ignoring air resistance) and it went up 5 meters (about 17 feet) you would have to throw it with an initial velocity of 10 meters per second (about 22 mph).  That's because the acceleration of gravity on Earth's surface is about 9.8 meters per second per second so plugging those number is v0=sqrt(2*5*9.8) = 9.9 meters per second.

So let's do this math for the molten sulfur on Io.  Again, ignoring air resistance (because there is no air).  In this calculation h = 200 miles = 322,000 meters and the acceleration of gravity at Io's surface is (at the equator) is 1.796 meters per second per second.  Now, everything is in the units of meters and seconds (don't try to multiply miles by meters, it doesn't work) so you plug those numbers in and v0=sqrt(2*322,000*1.796) = 1,075 meters per second.  Which is 2,405 mph.  Wow!  That just doesn't seem possible.  The speed of sound is 767 mph.  So that molten sulfur is going three times the speed of sound or Mach 3. (Yes, I know there's no air on Io and thus on sound.)

Anyone out there see a math error, let me know!
 •  0 comments  •  flag
Share on Twitter
Published on April 22, 2014 10:16

April 21, 2014

Write, then Edit, then Edit Some More . . .

I'm getting beta reads back on a science fiction novel I wrote called The Treasure of the Black Hole.  Getting the beta reads done is the last step (almost) before submitting or publishing a novel.  At least, that's my opinion.

This is April.  That novel was a NaNoWriMo project.  That's five months almost since I finished the first draft to it being almost done.  I say "almost" because I want to read through it one last time.

Why haven't I stuck a fork in it and called it done?  Well, I'm about to, but, to paraphrase Orson Wells: I will submit nor publish no novel before its time.

In this blog I once said: "Your first draft will suck.  Get over it and write the damn thing."  And I stick by that.  Write your first draft either as a NaNoWriMo project or just sit down and write.  Just keep writing.

But when the first draft is finished, there is still a lot of work to do: months of work.  The manuscript needs to be edited by you at least twice, three times is better.  But before you edit it, you have to let it sit and the longer the better.  I call this process "festering."  The errors and bad writing become more blatant the longer it sits.  I have a writer friend who says she won't go back to a manuscript until she's started working on something else.  "I have to fall in love with something else so I can see it objectively."  I'm not that extreme but I do wait a minimum of a week but, as I said, the longer the better.

Then I have my wife and (if she's willing) a friend proofread it.  Proofreading is a different function from editing.  If I were doing a venn diagram, proofreading would be inside of editing.  But proofreading is more concentrating on typos, spelling errors, and punctuation while not looking at sentence structure or writing.  Proofreading has its place in the editing process.

Then I have someone read it out loud to me.  When I hear it and don't see it I pick up on things I don't when reading.  I hear word repetitions, clunky construction, stilted dialogue, and writing that just isn't up to my standards.  It works very well.

Then I let it sit again, and edit it again.  Then I do beta reads with as many people as I can get (this is where your writers' group comes in handy; you are part of a writers' group, aren't you?).  You want to get all the feedback you can because people see things you don't see.  Or they have questions that make you realize you didn't explain something well enough.

Then, read though it one last time, and stick a fork in.  There's a balance there.  You don't want to tweak a manuscript for ten years.  You have to, at some point, realize that it's good enough.  Or great enough.  You need to publish or submit it as is.  Will there be a typo in it?  Probably.  Will there be a sentence that isn't absolutely beautifully written. Very likely.  But you need, now, to submit or publish it.

Then start writing that next first draft (which I actually hope you started sometime during the editing process of the last manuscript).  Because you need to just keep writing.
 •  0 comments  •  flag
Share on Twitter
Published on April 21, 2014 05:00

April 18, 2014

Book Trailer: The Adept Series

The book trailer for the Adept Series is now live:


Learn more about the magical Adept Series on my webpage.
 •  0 comments  •  flag
Share on Twitter
Published on April 18, 2014 10:10

April 15, 2014

Movie Review: 12 Years a Slave

I watched 12 Years a Slave last week and have spent the time since thinking about this powerful movie.  There is probably no one in what is commonly referred to as "The West" (i.e., Western Europe, Canada, and the U.S.) who needs to be convinced that slavery is a very very bad thing.  But, not 300 years ago, it was ubiquitous and the victims weren't all from Africa (the word "slave" comes from "Slavic" as in the peoples of south-eastern Europe, where for a long time Europeans got a lot of their slaves).  For about the last 100 years that there was slavery in the West, it coincided with a building consensus that it was very wrong.  The barbarity of slavery collided with the idea that "all men are created equal."

The movie, 12 Years a Slave, is based on an autobiographical novel about a free black man who was sold into slavery unjustly and accused of being a run-away slave.  In his twelve years as a slave he had owners who were reasonably good to their slaves.  But his last owner was a man who took out his insecurities on his slaves, including one beautiful female slave he regularly raped.

Like owners, overseers (the white plantation employees who supervised the slaves) were both good to the slaves or cruel.  Imagine all the bad bosses you had having the power of life and death over you.

The movie is bookmarked by a brutal beginning when Solomon Northup, the free black man, is punished for being a run-away, and an even more brutal climax.  This movie is well made, has many fine actors and performances, and shows that, in the words of Roy Batty from Blade Runner, "Quite an experience to live in fear, isn't it? That's what it is to be a slave."  You can see the fear every slave feels: fear of saying or doing the wrong thing which will bring them a flogging, whipping, or lynching.

12 Years a Slave does a better job than any other movie I've seen about what it was like to be a slave in the antebellum South.  And when you realize you need to look away from the screen at the reality of it, you realize just how bad slavery was.  And is, as there are still places where it is practiced, ironically, mostly in Africa.
 •  0 comments  •  flag
Share on Twitter
Published on April 15, 2014 12:32

April 14, 2014

Depression: An Insider's Perspective.

I am type-2 bipolar with dysthymia.  I don't make a secret about it and I am not ashamed of it (I'll get into reasons why in a bit).  I am on three medications to control both the bi-polar and the dysthymia (because lithium didn't work for me; or rather, it worked too well).

Dysthymia a type of depression defined as depression that lasts two or more years.  It can be slightly depressed with episodes of major depression, or very depressed.  With my bipolar my dysthymia was major depression occasionally interrupted by mania.

Today I want to talk about depression because I think it is very misunderstood by a lot of people.  And if you are a writer and your character is depressed, you'll want to understand that character.  So today I shall bare my soul.  Well, sort of.

Everyone get's a little "blue" every now and then.  Your girlfriend breaks up with you.  Your job sucks.  But it passes after a few weeks or even a couple of months.  This is "situational depression" where you are depressed for some good reason.  There is a slight risk of it turning into major depression, especially if it lasts longer than two months.  But mostly people get over it and get on with their lives.  It's a natural response to a sad situation.

Then there are people such as me.  I'm depressed nearly all the time (without meds).  I called it "floating depression" because it seemed there was this dark cloud hovering over me ready to rain on my parade at any time.   I could be in a happy, joyous occasion and feel sad.  This is not due to a character fault, a personality weakness.  It's due to the chemistry in my brain.  I probably inherited this chemistry judging by the mental illness in my family history.

This is like being type-I diabetic or having epilepsy.  It is nothing to be ashamed of.  It is not the fault of the person that they are depressed.  Telling them not to be depressed is like telling a diabetic to not be diabetic.  It won't happen.  Like the diabetic needs treatment, so does the person who is depressed.  Someone once asked me with horror in their voice, "Aren't you dependent on your drugs?" and I said "Yes, very much so, just like a diabetic is dependent on insulin."  Should the diabetic feel guilty about taking insulin?  They why should I feel shame for being "dependent" or my psychotropic drugs?

But what does depression feel like?  It ranges from feeling "blue" constantly to feeling life is completely not worth it and you might as well end it.  I used to wake up every morning contemplating killing myself.  And the side benefit was, I wouldn't have to go to work.  I'm not sure this is because I was depressed, but I would cry at movies.  Forrest Gump made me ball like a baby at the end.

I guess to know how depression feels, imagine being your saddest for not minutes, hours, or even days, but years.  No matter what nice or wonderful things happen to you, you are still sad underneath.  It's as if you live in the sunshine but shadowy hands are constantly dragging you down into a river of sadness.  And there seems to be no escape.

Depression is a serious mental disorder that you need to treat if you experience it for more than a couple of weeks.  I'm not a doctor nor a psychiatrist, just a guy who knows what it likes to be depressed constantly.  I am so happy I got the meds that keep me from being depressed and keep me from having manic episodes.  Maybe later I'll write about what being manic is like.
 •  0 comments  •  flag
Share on Twitter
Published on April 14, 2014 05:00

April 11, 2014

Clean Cars

Years ago I was in Anchorage Alaska.  It was a beautiful July day with blue sky and nary a cloud.  You could see the amazing mountains that surround this city almost as if they were close enough to touch.  And every single car I saw was filthy dirty.  Not a little dusty, not a few bugs on it, but filthy.  And I thought, "I should introduce these people to the concept of the car wash."  Then, as we drove through the streets, I saw a car wash.  It looked new and modern.  Well, except for the weeds growing between the crack in the concrete and that the building was empty.  It was obviously out of business.
So I asked my Alaska-born cousin, "Don't people wash their cars around here?"  And she said with a laugh, "Alaskans don't care about clean cars."  This much was obvious.
I do care about clean cars.  I like to keep my cars clean.  But where I live this is nearly impossible.  In the winter there's mud from the dirt on the road mixing with snow mixing with the sand the county dumps to improve traction.  Then the state sprays this brown goo deicer on the interstate.  It's supposed to be better for the environment than road salt.  I consider car washing to be part of car maintenance because you don't want those deicing chemicals eating your vehicle's skin.  So I try to wash the car on a semi-regular basis in the winter.
In the summer we have bugs and dust.  I tend to buy light-colored cars so the dust isn't immediately prevalent.  But I did own a dark blue Camaro.  I would wash it, drive it, wash it, drive it, etc.
But the biggest issue we have around here in the summer is bugs.  For instance, on Wednesday I drove my car about 110 miles from Spokane to my house.  When I left Spokane the car was pristine.  There wasn't a speck of dirt on it.  When I got home, the front was covered in bugs.  And that's not the worst.  Look at the picture at right.  This was taken in August a few years ago.  I left home with a clean car and drove 140 miles (round trip) and when I got home this is what the front of my car looked like.  And most of those bugs were in the last 50 miles or so.  The bugs were so thick at first I thought it was raining.
So, you wash your car, drive it a bit, wash it, drive it a bit, etc.  You can't keep a car clean here in central Washington State.
But I try.  And for the three minutes it's clean and beautiful, it's worth it.
 •  0 comments  •  flag
Share on Twitter
Published on April 11, 2014 08:00

April 10, 2014

Car Review: 2015 Audi A3 Sedan

Yesterday I had to take my car into the dealer for some warranty work.  They said they would need the car all day and since it was a 110 mile drive to the dealer I said I wanted a courtesy car so I could at least go do something.  They agreed.

I'd like to state that the auto dealer did a very good job on the work and I am very happy with their response.

But the courtesy car they gave me was a 2015 Audi A3 sedan.  Yes, a 2015 model, just introduced into the US.  According to Car and Driver (my source for all things automotive), Audi is hoping to use this car to attract younger buyers who, they hope, will get in the habit of buying Audis and then when they are older and have the means, move up to an A4 or A6 rather then a BMW or Mercedes-Benz.

But if this is the car that is suppose to lure young people to stick with Audi, I don't think they will be successful.

First of all, I could barely get into it.  Now, yes, I am a big guy.  But it wasn't my size that seemed to be the issue but my height.  I put the seat all the way down and still my head hit the top of the door frame.  I had to sort of wedge myself in, making sure my head was as close to the B-pillar (the pillar between the front and back doors) as possible, and still it seemed with each entry and exit I was scraping off hair I could not spare.  But that could have just been me.  Once inside the car I had plenty of room and was comfortable.

Driving the car was not what I would expect from a near $30,000 "near-luxury" vehicle.  The 1.8L turbocharged 4-cylinder engine ran so rough I wondered if was a diesel (it wasn't, I checked the filler cap).  It seriously sounded as if there was gravel in the cylinders grinding away.  Engines are supposed to sound good, not like concrete mixers.

The throttle response was nothing nothing nothing OMG TOO FAST!  It seemed the first few inches of throttle travel gave no response then the car leapt forward as if goosed by a cattle prod.  I was sure people behind me at red lights thought I was sleeping when the light turned green but I was slowly pushing down the gas pedal so the car wouldn't rear-end the car in front of me.

The Continental tires were noisy, especially on concrete pavement.  The trunk was small (it couldn't hold all of our Costco purchases) but, as I said, the interior was comfortable at least in the front seats.

I didn't get a chance to test its handling very much due to driving mostly on crowded city streets and the engine seemed capable to pull the car to speed on the freeway if you could stand the noise it made.  But if someone asked me if they should buy this car, I'd say "no" simply for the engine noise and the throttle response.
 •  0 comments  •  flag
Share on Twitter
Published on April 10, 2014 11:11