14 year-old me
14 year-old me (R, w/fangs)

For the last month, I’ve been looking through a lot of old family pictures to get good Halloween stuff to post on Twitter. I got plenty of that, but I also found lots of pictures of myself as a teenager that set me thinking about some things.

What struck me was how, in certain ways, I’m a lot like that younger version of me. He wanted to be a writer, he was interested in politics, he loved Halloween and ghost stories… If someone met 14-year-old me, and then was transported instantly through time to meet present-day me, they would recognize a lot of commonalities.

At least, in terms of raw interests, there are a lot similarities. The differences come in terms of things like skill-level. (I’m a much better poet now than when I was 14, for example.) And, I now have a lot more first-hand knowledge about how the world actually works, as opposed to teen-aged me, who just had a theoretical model based on stuff he’d read or seen on TV.

What bothers me, looking back, is all the stuff teenage me should have taken advantage of, if he had only been willing to. But he didn’t know what would happen, and so just sort of kept his head down, reading books and writing stuff that only he read.

Basically, he wasted a lot of time. And it occurs to me that somewhere out there, there are probably lots of other teenagers and young adults now in the same boat as I was, who vaguely know they want to be writers, but don’t know how to go about doing it.

My hope is that they’ll read this, and maybe it will help them avoid wasting time like I did.

If you’re interested in writing, do lots of it.

Teenage me thought the key to being a great writer was to read a lot of books, and then the idea for a great novel/essay/poem would eventually come to him. Not really. Reading is great and important, but if you want to be a writer, you have to write what you want, not what you think you should write based on some books you read.

The easiest way to do this is figure out what kind of book you’d like to read, and then go write it. (That’s a cliche, I know.)

Bottom line: if you have read enough to decide you’d like to be a writer (and let’s face it, few people who don’t like to read want to be writers), then it’s time to start writing.

Don’t be afraid to publish.

In the old days, before the internet, it was hard to get anything published. But now, anyone can do it. And it’s been that way since I was a teenager. But for a long time, I still was hesitant to publish anything for other people to read.

Why? I was scared. Of what? I’m not even sure. That people would sue me, or make fun of me, or that my ideas or stories would seem stupid.

Basically, I was afraid people would laugh at me. Looking back, this was a hugely irrational fear. The big problem I face is not ridicule or lack of privacy, but getting people to read anything I write. Getting an audience is the hard part–it takes years of publishing your work before it starts to happen. So the sooner you start, the better.

When you’re a kid, you assume that the world is full of bullies who will mock your work, like the ones in school. And sure, the internet has lots of that, although good publishing platforms provide safeguards against it. But the point is, unless you publish it, no one will see your work. And who is hurt by that? Well, you, for starters. But also the people all across the world who have similar interests to yours, for whom you have written the perfect thing, but who don’t get to read it because you didn’t publish it.

It doesn’t matter if what you write is bad

In the beginning, I was worried that my blogs on politics were facile, that my poems were awkward and pretentious, that my stories were incoherent and vague. In short, I worried that my work was bad.

I don’t worry about that any more. I know when I’m doing good work or not.

How do I know? Well, simply put, I wrote a lot of stuff that was in fact awful. I wince when I read some of my old blog posts from 2009 or ’10. What was I thinking?, I ask myself.

What’s funny is that at the time, I was so concerned with not writing bad stuff, and yet I managed to do it anyway.

Writing is like anything; you get better at it by doing more of it. What I know now is that I’ve written a lot of stuff that’s pretty bad–but I’ve also written a few things I’m very proud of. And I couldn’t have done the latter without doing a lot of the former. As such, I’m not even really ashamed of lousy poems or blog posts from my past–I look at them as a cost of doing business.

Remember: if you manage to write one really great essay, or novel, or poem, it will more than offset however many failed drafts and ill-advised scribblings you had to generate in order to do it. And there will be a lot of those.

lorem ipsum
Need extra words? Here are some random ones!

If you follow me on Twitter, you probably know that I’ve been working on a new novel for the last two months. My goal at the outset was 100,000 words, and I’ve been keeping a running update of my progress. Here’s my latest:

I re-read it, and I think the story has a pretty decent pace overall. It may be a little too brisk (it turns out these things seem much faster when you’re reading them than when you’re writing them), but I think I have the central plot arc in place. And there’s just no way to pad it out to 100,000 words, which is bad, because it’s a sci-fi novel, and those are generally “supposed” to be at least 80,000 words.

I can and probably will throw in some additional world-building detail and “local flavor”, tie up a few minor loose ends in the plot, and add some more description of scenes and characters. (Description, as long-time readers know, has always been my weak point.) But even all that will probably bring it to around 60,000 words, at the maximum.

Personally, I have never been a fan of arbitrary word counts for a genre. A story should be told in the number of words that make it most powerful for the reader–no more, no less. Too many words, and they get bored. Too few, and they won’t get drawn into it.

But of course, the publishers don’t see it that way. They have certain rules for word count by genre. In my opinion, this “quantity over quality” approach encourages overly-long books, but then again, when you have to review thousands of manuscripts, it helps to have some rules that let you automatically eliminate some of them. (This article summarizes it well.)

The key question here is; what do readers like? Assuming the two books are equal in price, does the typical reader prefer to have a longer one to a shorter one? Do they want to maximize the number of words they get for their money? Or do other considerations take precedence?

For myself, I generally make decisions based on other factors. I read the synopsis to see if it sounds like an interesting premise, then I flip through the book a little and see if I like the author’s style. Cover art also makes a difference to me, even though we all know we shouldn’t judge a book by its cover.

What about you? What factors most heavily influence your book-buying decisions? How much do you care about the length of a book?

[You can make a case for any of these characters being “Mary Sues”. From left: Robert Pattinson as Edward from Twilight, Miranda Lawson from Mass Effect 2, Sean Connery as James Bond, and Daisy Ridley as Rey in Star Wars: The Force Awakens. All images via respective Wiki pages and re-used under ‘fair use”]

First, let me begin by defining terms. Or more accurately, letting Wikipedia do it for me:

A Mary Sue (if female) or Marty Stu (if male) is an idealized and seemingly perfect fictional character…

The term “Mary Sue” comes from the name of a character created by Paula Smith in 1973… The story starred Lieutenant Mary Sue (“the youngest Lieutenant in the fleet — only fifteen and a half years old”), and satirized unrealistic characters in Star Trek fan fiction.

“Mary Sue” is now a shorthand for an unrealistically capable character, with no flaws or foibles. It’s the mark of an amateurish writer, too lazy to flesh out their characters.

Naturally, there’s a discussion to be had here about the use of the term’s sexist connotations, and whether the pejorative “Mary Sue” is now used by lazy critics to put down any female protagonist. It’s a very interesting issue, but it’s not the thing about Mary Sues I want to discuss here.

What I want to address is the motivation for creating such characters in the first place. Often, critics assume that the reason is wish-fulfillment; that authors imagine themselves to be these characters, and make them perfect as a result. (Critics usually assume that everyone is as conceited as they are.)

But perfect–or at least, incredibly highly-skilled–characters are actually very tempting for reasons of plot, especially in a science-fiction or fantasy setting. Simply put; when your plot takes place in a big, complicated universe, you want your character to be able to participate in every aspect of that universe.

If I’m writing a sprawling epic with, say, a league of heroic knights who go around fighting dragons, it’s a bit of a letdown if I say “But sadly, Bob the protagonist was an archer who knew nothing about horsemanship or swordsmanship, and so could never be a knight.” By the same token, if Bob is a knight, then it’s a real shame if he can’t be in any archery attacks.

When you’re writing a story, you generally want your protagonist to be able to participate in most of the action. Having them figure out and solve the central conflict makes a better story than: “Bob found out a lot of interesting information about dragons. So he gave it to the experts who handle that sort of thing. 8 months later, he read in the newspaper about how the dragon issue had been solved. ‘Huh,’ he said. ‘So that’s how that all played out.’ The End.”

Now sure, you can have lots of characters with different skill sets, and still have the protagonist be involved in every step. This is relatively easy to do if your setting is the present day or recent past. For example, in a mystery novel, Ted the Brooding Detective With The Dark Past can take the evidence to Jill the Wisecracking Forensics Expert With The Rebellious Streak. (And if they fall in love, then you’ve almost got all the characterization you need.)

But this gets harder to do the more exotic your setting is, because then you have to make up a bunch of skill sets for people This is especially true in science fiction. So, there’s the girl who flies the ships, there’s the guy who fixes the ships, there’s the other guy who fixes the robots, there’s some alien who mines the raw materials for building both the ships and the robots…

It can be done, don’t get me wrong. But it’s tough to do it, and very, very tempting to the novice writer to just say, “We need to get this plot moving! We haven’t got time to meet the guy who waxes the floors. It’s faster to just make the protagonist do it.”

i can do better

I’m working on a new novel. It’s an idea I’ve had for a while, but I just recently started writing it down. (I’ve hinted about it a few times already on Twitter.)

I’m about 19,000 words in, and I recently wrote a scene that bothered me a little because it reminded me of a passage in my novella The Start of the Majestic World.

There’s a scene in Majestic World where Agent Maynard has a verbal confrontation with the main villain, Colonel Preston, a handsome army colonel who tries to intimidate her into following his orders even though she’s not under his command.

Here’s a bit of it:

The Colonel stood up, and walked around the desk so that he was very close to Maynard—so close, and in such a posture, that Maynard felt he was trying to brush aside the barriers of rank and agency, and underscore primarily the difference in sex between them. 

I don’t want to give away too much about the new book, but the scene in it has some very similar elements. The female protagonist is in a meeting with a handsome male colonel, and he is trying to get her to do something that may violate protocol. (It’s deliberately ambiguous in the scene, but she feels uneasy about it.) And there’s some uncomfortable sexual tension–it’s less overt than in the above, but there’s some suggestion he might be trying to seduce her.

Now, there are also some big differences, involving both the setting and the characters. But as I was sketching out the scene in my mind, I was thinking, Gosh that’s awfully similar to the Maynard/Preston scene.

So, right now you’re thinking: “Well, dummy; you’re the writer–don’t write it that way, then!”

True, that’s one option. But there are a couple reasons I hate to remove or alter the scene. First, it’s a very natural way for things to play out in the story–it works well in context, both in terms of plot pacing and characterization. I hate to lose scenes like that.

And second, it’s a much better execution of the concept than in Majestic World. The dialogue is more natural, the characters are more nuanced and less caricatured. This is encouraging to me–it’s good to know I’ve improved as a writer since writing the Maynard/Preston scene over three years ago.

The great film director John Huston once said about movie remakes: “There is a wilful, lemming-like persistence in remaking past successes time after time… Why don’t we remake some of our bad pictures… and make them good?” That’s sort of how I feel about this–sure, I tried this basic concept once, but now that I’ve improved as a writer, why not prove that I can do it better?

At the same time, I could see somebody who read Majestic World reading the new book and saying “Yawn! Another Colonel behaving inappropriately towards the protagonist. Give us something new, Berthold!”

But I can guarantee it won’t be the same thing over again. Trust me.

What do you think? Should an author revisit a concept similar to one they’ve written before, if they feel like they can write it better this time, or is it best to try to break new ground?

I’ve heard lots of criticisms of video games over the years, but Jeff Vogel’s critique that they have too many words is a new one. He makes a strong case against one particular game–Obsidian Entertainment’s Pillars of Eternity. After reading his article, it’s hard to argue against the claim that Pillars is too verbose. The character creation and menu screens are packed with tons of text for the player to wade through.

I’m less sure about whether this is really a trend in gaming generally. After all, Pillars was explicitly designed as a throwback to the beloved text- and lore-heavy Black Isle RPGs. For example, Planescape: Torment has over a million words. Even I tended to ignore some of the esoteric descriptions in Planescape, and I love that game.

Scene from “Planescape: Torment”

Some players really do seem to enjoy the atmosphere of a game rich with background material. It may be true that much of the information is irrelevant to the game’s mechanics, but this is High Fantasy, and one of the things High Fantasy fans look for is a sprawling world filled with many interesting details that don’t all fit into the main narrative.

Using lots of words is indeed a problem, as Vogel says, but not just in games. The High Fantasy trope of giving tons of background information can be traced back to J.R.R. Tolkien. The Pillars of Eternity intro is nothing next to the dense opening chapters of The Fellowship of the Ring. In general, when writing in a genre, you will try to emulate the most successful authors in that genre, so it’s hard to blame Obsidian for looking to the work of Tolkien and his successors for ideas.

I myself have never been a fan of this style. And that’s despite the fact that some of my influences favored verbosity. Take H.P. Lovecraft for example–he was a pioneer in writing horror, but he tended to go overboard with some of his descriptions. I think some of that crept into my own early attempts at writing horror.

It’s much easier to use too many words than to use just the right number. The old line about “writing a long letter because I didn’t have time to write a short one” applies.  It’s easy to waste words, and that dilutes their intended effect.

The economy of any piece of writing is a very important consideration, but few people ever think about it. It wasn’t until I saw the movie Lawrence of Arabia that I really learned to appreciate it.

Think of it this way: whenever you write something, eventually you will have to stop. You only have so many words before you have to hit send, or mail it to the publisher, or whatever. While the supply of words is theoretically infinite, in practice it’s severely limited–by the reader’s attention span if nothing else.

So, you want to maximize the value you get per word. What do I mean by “value”? Well, it’s whatever idea or feeling you are trying to communicate in your writing. If it’s an informational document or a bit of technical description, then you want to be as clear and concise as possible. If you are writing a character who prefers to communicate non-verbally or who is just mysterious, you use few words, and you make them vague and open to interpretation.

Sometimes there is value in deliberately using too many words. The dramatist W.S. Gilbert (another of my favorites) would often have characters say things in as complicated and lengthy a way as possible for comic effect. “Quantity has a quality all its own,” as they say in big organizations.

Vogel is right that the Pillars opening screens are bad at conveying information. They could have communicated the same points more succinctly. But the problem is that in addition to giving the player some information, they are also supposed to be atmospheric. And you usually need more–or at least different–words to create an atmosphere than to just convey information.

It’s a difficult balancing act–the writer(s) must both communicate technical detail about how to actually play the game while also keeping the player immersed in the virtual world in which the story is set. (For an example of a character creation intro that is more integrated with the game and doesn’t bore the player, I recommend Fallout: New Vegas-also by Obsidian.)

The “optimal” number of words is dependent on what the writer is trying to convey, as well as on the medium they are using. Obviously, a screenwriter is going to use fewer words than a novelist to describe the exact same scene, because the screenwriter knows they will have actors and sets that will communicate certain things visually.

To summarize, all writers, regardless of their subject, style or genre, should follow Einstein’s advice: “Everything should be as simple as possible–but no simpler.”

standing-color-cropped
Carrie Rubin, author of “Eating Bull” and “The Seneca Scourge”

[I recently read the book Eating Bull, by Carrie Rubin. I loved it, and contacted the author.  She very kindly agreed to be interviewed about her work.  Enjoy!]

BG: I’ll start at the beginning: how did you get the idea for “Eating Bull”? Did the idea just come to you one day, did some specific incident suggest it, or…?

CR: A little bit of both. Overweight/obesity is a professional interest of mine. I’ve dealt with it in both a clinical and research setting. Many people assume a large BMI means a lack of willpower, but that’s both inaccurate and unfair. Many other factors come into play, especially our disastrous food environment where processed food, mega-sizes, and sugar-laden junk bombard us wherever we go.

Through fiction, I wanted to bring the issue of the food industry’s role in obesity to light. Plenty of nonfiction books exist on the topic, but with fiction you get an emotional element as well.

As for a specific incident, several years ago a tearful, severely overweight adolescent sat on my exam table and said: “Not a day goes by I don’t know I’m fat, because no one will let me forget it.” That was the catalyst for my teenage protagonist.

BG: The book has three “starring” characters, each of whom represents a different view on the roles of the individual and society in causing obesity. Can you discuss these viewpoints a little, and also how you balanced the amount of page time devoted to each?  Was it difficult to strike that balance?

CR: I wanted to represent three viewpoints, from one extreme to the other, all of which exist in our society:

My secondary protagonist, a social-justice-seeking public health nurse, represents the viewpoint that society plays a huge role in our weight gain and must take responsibility.

My villain, an obsessive-compulsive fitness fanatic, believes obesity is entirely the individual’s fault and takes it upon himself to rid the world of “undisciplined sheep” … in a very bloody way.

My primary hero, an overweight teenager, falls somewhere in between, representing the viewpoint that both the individual and society play a role, but that society must make changes so that it’s easier for the individual to change too.

As for the number of pages devoted to each, I simply shifted to a new viewpoint with each chapter, rotating the characters on a regular basis, each carrying the story forward according to his or her point-of-view.

BG: Regarding the villain of the story, Darwin: He’s really a repulsive and terrifying character, but you also show just enough of a glimpse of his past to make the reader feel a little sorry for him at the same time. He seems genuinely mentally ill, rather than just a caricature of a psycho killer–I loved that. Any observations (or advice) on writing plausible, well-rounded villains?

CR: Villains are tricky to write. They can easily become one-dimensional. Rounding them out into full-fledged characters with likable—or at least relatable—traits is difficult, and I have a ways to go before I master that skill.

Darwin’s pretty despicable, but I tried to create backstory that would explain how he got that way. This proved even trickier considering I hid his identity until the climax. I had to flesh out his character without giving away who he was. That adds an element of mystery to the thriller and hopefully keeps the reader guessing until the end.

BG: I could go on forever about how much I liked the characters in “Eating Bull”. Expanding from just Darwin, what are your techniques on writing characters generally? Apart from the three starring characters, did you also write the supporting cast to reflect the central theme of the novel?

CR: Before I even start my outline, I define my main characters: their likes, dislikes, dreams, goals, mannerisms, etc. Characters drive the plot, so I like to have a firm grasp on them before I start much story planning.

As for the supporting cast, I usually have them in mind before I begin, but they tend to blossom as I go along. In Eating Bull I did indeed write some minor characters to reflect the central theme: the bullying grandfather and classmate, the unsupportive boyfriend who dislikes overweight people, the dietician and fitness coach who guide my main character toward his goal.

Some of the supportive characters heap a world of hurt on my teenage protagonist, but I wanted to reflect real life. In my research for the book, I attended a seminar in which the focus was to highlight the frequent fat-shaming that goes on in our society—including from the healthcare industry—and to shift the onus from weight loss to size acceptance. The tales the speakers told of the shaming they experience on a regular basis, from acquaintances and strangers alike, horrified me. I knew I needed to have my character experience the same thing if I wanted to be honest to the theme.

BG: What is the central message you want readers to take away from “Eating Bull”?

CR: I’ve already touched on that somewhat, but the main takeaway is: weight gain and loss isn’t as simple as calories in minus calories out. There are many other factors in the equation, including hormones, biological determinants, neurochemicals associated with addiction, socialization of food, poverty, food environment, built environments (poor walkability of a city, food deserts, etc.), and yada yada yada.

I could go on and on, but the point is, changes need to be made at all of these levels if we want to see real progress. Expecting the individual to do it alone hasn’t worked too well for us so far. It’s time to up our game.

BG: So, not to spoil anything, but you’ve mentioned you are working on another book. Any hints as to what to expect from it?

CR: I’m often reluctant to discuss my unpublished works (worried I’ll jinx things, perhaps?), but I can tell you my latest completed manuscript is a medical thriller with supernatural elements. There is no shortage of medical thrillers out there, so I like to change things up a bit. It’s pretty much ready to go, and I’ve just completed the first draft of the second in the series. I’d like to write at least three novels with the same recurring characters—maybe more—but each book will be a complete stand-alone.

BG: What other authors have influenced you, either in writing style or in genre/subject matter?

CR: I always get nervous with this question, because I worry I should list a number of literary greats, but that’s not how it is for me. I’m all about the storyteller.

In my teen years, Stephen King was a huge influence on me. More than just be a writer, I wanted to be a storyteller, and to me he’s one of the best. JK Rowling is in that category too—a gifted storyteller—and if I can match a fraction of their skill I’ll be happy.

In terms of writing medical thrillers, Robin Cook was my first influencer, and while his writing might sometimes get panned, he knows how to weave a good tale. I’m easy to please and can overlook a lot. Give me a story I can get lost in and you’ve got me as a fan forever.

Before I go, Berthold, I want to thank you for your support of my novel and for interviewing me on your blog. It’s a pleasure to be here and I enjoyed answering your questions!

BG: My pleasure. Thank you for your thoughtful and informative answers!

[Carrie Rubin is a physician, public health advocate and the author of medical thrillers Eating Bull and The Seneca Scourge. You can find her books here, and also be sure to check out her website and social media pages.]

Via Paul Graham, a WSJ article on teaching kids to write by banning them from using certain “boring” words, such as “good” “bad”, “fun” and “said”.  To quote from the article:

“There are so many more sophisticated, rich words to use,” said (or affirmed) Ms. Shelton, whose manual “Banish Boring Words” has sold nearly 80,000 copies since 2009.

Her pupils know better than to use a boring word like “said.” As Ms. Shelton put it, “ ‘Said’ doesn’t have any emotion. You might use barked. Maybe howled. Demanded. Cackled. I have a list.”

This reminded me of novelist Elmore Leonard’s rules for writing, one of which was: “Never use a verb other than ”said” to carry dialogue.”

And people wonder why kids have trouble learning to write.

So then, who is right: the teacher or the novelist? My answer: it depends.

There are times when using something other than “said” is appropriate.  This is especially true with humor–saying “burbled” is so much better than “said” if you want people to laugh.

That said, you can go too far with it.  And since Leonard’s goal was to make the writer “invisible”, I would say in that case sticking with “said” is usually a good idea.

My rule of thumb: if it sounds right, use it.  If “said” doesn’t sound right, but “called” does, use “called”.  But don’t spend your time trying to find some other bizarre word if “said” will do.

Take this exchange from my novella, The Start of the Majestic World:

Maynard and Brett sat outside on the steps that led into the headquarters.  Brett was studying schematics of a sniper rifle on his tablet.  Maynard stared straight ahead, deep in thought.

“I’ve received no communication of any kind from anybody at the Bureau,” muttered Brett. “It doesn’t make sense.”

“Yeah, it does;” said Maynard slowly. “This is a Dead Zone.  They are blocking any signal they don’t want getting in.”

Brett nodded.  “And most likely any they don’t want getting out, too.”

“Yes.”

“But D.C. would know it was being blocked.  Any decent Intel machine would—”

“They want it blocked,” she said. “They don’t want to know, and he doesn’t want to tell them.  It’s better for everyone that way.  I’ve seen it a million times—I’ve just never been on the wrong end of plausible deniability before.”

The two agents sat in silence for a minute.

“They have to be listening to us,” said Brett.

“Probably,” said Maynard. “But they don’t give a damn what we say.  They figure there’s nothing we can do.”

The first time Brett speaks, I used “muttered” to indicate he was still looking at the rifle schematic, and not thinking fully about talking.  When Maynard responds, it becomes “said” because now they are just having a conversation.  And I dropped “said” or any variants after that, and left it to the reader to follow.

Leonard had some other interesting rules.  I took particular note of these two:

8. Avoid detailed descriptions of characters.

9. Don’t go into great detail describing places and things.

As I wrote recently, I used to believe this too.  Then I wrote a collection of short stories that contained very little description, and my readers complained that there wasn’t enough description.

I thought there must be some other problem.  So I wrote a novella that contained very little description, and my readers complained that there wasn’t enough description.

Was Leonard just wrong? Seems unlikely–he was an award-winning novelist. I am guessing it’s more that once you are a really good writer, it doesn’t take much effort to describe someone or something.  It barely feels like you are doing anything when you know exactly what words to use.  There have been great authors (John Steinbeck, F. Scott Fitzgerald) who could take things that were not very interesting in themselves, and write gorgeous descriptive passages about them.

One of the most common criticisms of my fiction has been that there is not enough description. I’ve heard this from both P.M. Prescott and Jonnah Z Kennedy, as well as other readers who don’t have websites I can link to.  It was not an accident that there is so little description.  I had a hypothesis that most fiction contains too much description, and that this was particularly a problem in horror fiction, when describing things detracts from the horror.

I think my aversion to description goes back to when I read the following in Paul Graham’s essay “Taste for Makers”:

Good design is suggestive. Jane Austen’s novels contain almost no description; instead of telling you how everything looks, she tells her story so well that you envision the scene for yourself.

That sounded good to me.  And hell, I thought,  it’s even more important to avoid description when you’re writing psychological horror than when you’re writing a comedy of manners.  Horror, I’ve always said, is all about the unknown, and nothing screws up the unknown like describing it.  So I made a conscious effort to not describe stuff; the idea being that people would fill in the details for themselves.

Based on the feedback I’ve received, this was a mistake.  Keeping description to a minimum was not a formula for success, at least not in my stories. Now, maybe there are other issues as well–maybe I didn’t tell the story well enough that readers could fill in the blanks.  But all  I know for sure is people specifically complained about the lack of description.

Fair enough.  So, how is it best to describe stuff?  Should I say:

The pale blue Autumn moon shone its faint light on the cemetery.  A passing cloud would now and again cast the ancient graveyard into darkness.  A howling of some distant animal echoed through the surrounding wood, and the bewitching southern wind wafted the leaves over the long-forgotten tombstones.

Or:

It was a dark cemetery.  The moon was occasionally obscured by clouds. It was windy, and a dog was howling far away.

The former is poetic, but it takes forever to convey a fairly simple scene.  The latter communicates the same information more quickly, but it seems boring and dry.

“Well, it depends what you’re writing!”, you say.  Ok, but in the above example, it’s the same basic point both times: to show the reader that we are in a graveyard at night.  And it’s creepy.  But what’s the best way of doing that?  Normally, one would think conveying that in as few words as possible is best.  And yet, writing: “They were in a graveyard at night” seems a little bare, doesn’t it?