<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Big Bad Book Blog &#187; how to write</title>
	<atom:link href="http://www.bigbadbookblog.com/tag/how-to-write/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bigbadbookblog.com</link>
	<description></description>
	<lastBuildDate>Thu, 29 Jul 2010 16:32:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Seven Types, Infinite Stories: Writing the &#8220;High Concept&#8221; Idea</title>
		<link>http://www.bigbadbookblog.com/2009/03/12/seven-types-infinite-stories-writing-the-high-concept-idea/</link>
		<comments>http://www.bigbadbookblog.com/2009/03/12/seven-types-infinite-stories-writing-the-high-concept-idea/#comments</comments>
		<pubDate>Thu, 12 Mar 2009 22:59:08 +0000</pubDate>
		<dc:creator>Greenleaf Book Group</dc:creator>
				<category><![CDATA[article]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[writing & editing]]></category>
		<category><![CDATA[help with story ideas]]></category>
		<category><![CDATA[high concept]]></category>
		<category><![CDATA[how to write]]></category>
		<category><![CDATA[publishers weekly]]></category>
		<category><![CDATA[seven story ideas]]></category>
		<category><![CDATA[water for elephants]]></category>
		<category><![CDATA[what is plot]]></category>
		<category><![CDATA[what is theme]]></category>
		<category><![CDATA[writer's block]]></category>

		<guid isPermaLink="false">http://www.bigbadbookblog.com/?p=1344</guid>
		<description><![CDATA[Fingers poised with painful precision above the keyboard. Eyes squinting, lines furrowing between arched eyebrows. Mouth pursed. Head cocked. The occasional twitch, fingers buried in hair and the frustrated sigh.
Writer’s block.
It’s not that I don’t have ideas, because Lord knows I have ideas. A plethora of squirming ideas wriggling about, waiting to be plucked and [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright" title="Water for Elephants" src="http://upload.wikimedia.org/wikipedia/en/e/e7/Water_for_elephants.jpg" alt="" width="153" height="232" />Fingers poised with painful precision above the keyboard. Eyes squinting, lines furrowing between arched eyebrows. Mouth pursed. Head cocked. The occasional twitch, fingers buried in hair and the frustrated sigh.</p>
<p><a href="http://www.newyorker.com/archive/2004/06/14/040614fa_fact" target="_blank">Writer’s block</a>.</p>
<p>It’s not that I don’t have ideas, because Lord knows I have ideas. A plethora of squirming ideas wriggling about, waiting to be plucked and put to the hook, bait for a story to swallow it whole. (Gruesome but truthful.) The problem is their lack of substance. I might have a few scribbles in my notebook after an hour of brainstorming and they all mostly come down to a story about a so-and-so, who faces so-and-so challenge to reach so-and-so goal. It’s formulaic, stale, overdone, and about as gripping as watching a dying earthworm crawl along the sidewalk. I want to cultivate my ideas because they’re precious to me, but in truth, so few of them move beyond that first, stagnant concept.</p>
<p>A professor of mine once said that when you are writing, you should jot down the first four ideas that come into your head for your story. And then you should immediately cross out the first three, because they’re clichéd, hackneyed crap. What you want to create is beyond the surface. You don’t want a “concept,” you want a <strong>high concept</strong>. Something universal but fresh, an interesting twist, a compelling new confection. Which some might argue is difficult, given that many scholars, critics etc. have decided there are only seven story ideas in the whole world.</p>
<p>Except that there are fourteen. Depending on whose side you’re on…<span id="more-1344"></span></p>
<p>Here are the seven (via the <a href="http://www.ipl.org/div/farq/plotFARQ.html" target="_blank">Internet Public Library</a>):</p>
<ol>
<li>[wo]man vs. nature</li>
<li>[wo]man vs. man</li>
<li>[wo]man vs. the environment</li>
<li>[wo]man vs. machines/technology</li>
<li>[wo]man vs. the supernatural</li>
<li>[wo]man vs. self</li>
<li>[wo]man vs. god/religion</li>
</ol>
<p>Or, alternatively, here are the seven (as found on <a href="http://writingforstagescreen.suite101.com/article.cfm/the_seven_basic_plots" target="_blank">suite101</a>):</p>
<ol>
<li>the quest</li>
<li>voyage and return</li>
<li>rebirth</li>
<li>comedy</li>
<li>tragedy</li>
<li>overcoming the monster</li>
<li>rags to riches</li>
</ol>
<p>I’ve found that melding the two is best: From the first list you choose your <strong>theme</strong>, from the second list you decide your <strong>plot</strong>. And when you combine both together, you create your high concept.</p>
<p>Examples:<br />
-    During the Great Depression, a young man leaves school and becomes a member of a traveling circus, falls in love with a star performer, and takes care of an eccentric elephant. (Sara Gruen’s <em>Water for Elephants</em>)<br />
o    Theme: man vs. the environment<br />
o    Plot: voyage and return</p>
<p>-    A family narrative of sex, love and secrets as recounted by the youngest generation’s child, an intersexual who metamorphoses over the course of the story from woman into man. (Jeffrey Eugenides’ <em>Middlesex</em>)<br />
o    Theme: [wo]man vs. self<br />
o    Plot: rebirth</p>
<p>-    When a teenage girl is displaced to a dreary town, she becomes fascinated with a local boy who seems almost supernatural, only to discover that she is falling in love with a vampire and putting both of their lives at stake. No pun intended. (Stephenie Meyers’ <em>Twilight</em>).<br />
o    Theme: woman vs. the supernatural<br />
o    Plot: overcoming the monster</p>
<p>Brenda Janowitz’s <a href="http://www.publishersweekly.com/article/CA6628065.html?q=brenda+janowitz" target="_blank">article</a> in PW toys with the notion of the “high concept” idea—stories like <a href="http://news.bbc.co.uk/2/hi/entertainment/3935561.stm" target="_blank">Good versus evil</a>, <a href="http://www.washingtonpost.com/wp-dyn/content/article/2006/11/27/AR2006112701397.html" target="_blank">man plays God</a>, <a href="http://www.nationalreview.com/comment/comment-goldblatt061003.asp" target="_blank">New York fashion</a>—and its significance in today’s market. Janowitz notes, “It&#8217;s hard to describe what exactly makes an idea high concept—it&#8217;s almost the opposite of what it sounds. But simply put, it&#8217;s an idea that is easily explainable and can be sold in one sentence.” But as her agent friend said, it may seem simple, but if you don’t have a high concept, you won’t get your book published. But publishers don’t want a formula, they want chemistry. And though I’m not a science professor, I can offer this thought: high concepts may hold untold depth, but they all begin with simple formulas that, through your own creativity and inspiration, become said chemistry. Your idea + theme + plot = your story.</p>
<p>Brenda’s final conclusion is to keep writing, and the high concept will emerge.</p>
<p>But remember, scratch out the first few ideas.</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fwww.bigbadbookblog.com%2F2009%2F03%2F12%2Fseven-types-infinite-stories-writing-the-high-concept-idea%2F';
  addthis_title  = 'Seven+Types%2C+Infinite+Stories%3A+Writing+the+%26%238220%3BHigh+Concept%26%238221%3B+Idea';
  addthis_pub    = '';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://www.bigbadbookblog.com/2009/03/12/seven-types-infinite-stories-writing-the-high-concept-idea/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Common v. Correct</title>
		<link>http://www.bigbadbookblog.com/2006/05/17/common-v-correct/</link>
		<comments>http://www.bigbadbookblog.com/2006/05/17/common-v-correct/#comments</comments>
		<pubDate>Wed, 17 May 2006 17:35:23 +0000</pubDate>
		<dc:creator>Lari Bishop</dc:creator>
				<category><![CDATA[article]]></category>
		<category><![CDATA[writing & editing]]></category>
		<category><![CDATA[chicago manual of style]]></category>
		<category><![CDATA[common usage]]></category>
		<category><![CDATA[correct grammar usage]]></category>
		<category><![CDATA[editors]]></category>
		<category><![CDATA[how to write]]></category>
		<category><![CDATA[linguists]]></category>
		<category><![CDATA[Webster's Dictionary]]></category>
		<category><![CDATA[written language]]></category>

		<guid isPermaLink="false">http://www.bigbadbookblog.com/2006/05/17/common-v-correct/</guid>
		<description><![CDATA[<p><img id="image88" alt="common-v-correct.jpg" src="http://www.bigbadbookblog.com/wp-content/uploads/common-v-correct.thumbnail.jpg" /><em>Decided May 17, 2006</em></p>
<p>Cases before the court:</p>
<div style="margin-left: 116px;"><em>Bring </em>   &#160;  v.  &#160;&#160;  <em>Take</em><br />
<em>Like  </em>   &#160;&#160;  v.   &#160;&#160;  <em>Such as</em><br />
<em>Over   </em> &#160;&#160;  v.   &#160;&#160;  <em>More than/Greater than</em><br />
</div>
<p><em>Big Bad Book Blog</em> delivered the opinion. <em>Merriam-Webster's Collegiate Dictionary</em> occasionally dissenting. <em>Chicago Manual of Style</em> occasionally dissenting.</p>
<p>Common usage has invaded the domain of correct usage. The two parties constantly battle for dominance in the written language. Over time, correct usage eventually accepts certain elements of common usage, blurring the lines for writers and editors. And of course, multiple parties take sides in the dispute—editors, linguists, publishers of dictionaries and style manuals.</p>]]></description>
			<content:encoded><![CDATA[<p><em>Decided May 17, 2006</em></p>
<p>Cases before the court:</p>
<blockquote><p><em>Bring </em>v. <em>Take</em><br />
<em>Like </em>v. <em>Such as</em><br />
<em>Over </em>v. <em>More than/Greater than</em></p></blockquote>
<p><em>Big Bad Book Blog</em> delivered the opinion. <em>Merriam-Webster&#8217;s Collegiate Dictionary</em> occasionally dissenting. <em>Chicago Manual of Style</em> occasionally dissenting.</p>
<p>Common usage has invaded the domain of correct usage. The two parties constantly battle for dominance in the written language. Over time, correct usage eventually accepts certain elements of common usage, blurring the lines for writers and editors. And of course, multiple parties take sides in the dispute—editors, linguists, publishers of dictionaries and style manuals. In the end, the true victim is the writer. How is the writer to determine when common usage is acceptable?<span id="more-87"></span></p>
<p>It is the opinion of this blog that it is always better to be more specific than less specific when writing. That rule, as well as solid knowledge of the exact meanings of words, should guide writers and editors. Of course, there are always exceptions, instances when common usage, though not correct, is more appropriate. Dialogue is a good example, as is use of slang to make a point or set a tone. And since the tone and writing style of most blogs is very casual, you will no doubt find some examples of common usage here, too.</p>
<p>Keep in mind that it is possible to be correct and specific without sounding pompous or stiff. Following are a few cases that can easily be decided by the writer and will generally not change the tone of a sentence.</p>
<p><span style="font-style: italic">bring</span> v. <span style="font-style: italic">take</span>: People often use <span style="font-style: italic">bring</span> when <span style="font-style: italic">take</span> is more correct. For example, “Don’t forget to bring the book with you on your trip.” The difference between <span style="font-style: italic">bring</span> and <span style="font-style: italic">take</span> is all about location. When you are asking someone to deliver something to your current location, you should use bring: “Please bring me a glass of water.” When you are asking someone to carry something to another location, you should use take: “Don’t forget to take the book with you on your trip.”</p>
<p><span style="font-style: italic">like</span> v. <span style="font-style: italic">such as</span>: <span style="font-style: italic">Like</span> is used in so many different ways in our language; it’s not surprising that it rapidly takes the place of a variety of other words and phrases. However, it is important to keep in mind that <span style="font-style: italic">like</span> really means <span style="font-style: italic">similar to</span>. In writing, it’s best to use <span style="font-style: italic">like</span> when <span style="font-style: italic">similar to</span> could be used instead. If a better replacement phrase is <span style="font-style: italic">such as</span>, use <span style="font-style: italic">such as</span>. For example, “Sheila enjoys period films, such as <span style="font-style: italic">Sense and Sensibility</span>” (meaning Sheila enjoys <span style="font-style: italic">Sense and Sensibility</span> and other period films), and “I often go to family dining restaurants like Denny’s, but I never go to Denny’s.” When speaking, you might say “films like <span style="font-style: italic">Sense and Sensibility</span>” (meaning Sheila enjoys films similar to <span style="font-style: italic">Sense and Sensibility</span>, but not <span style="font-style: italic">Sense and Sensibility</span>) and it wouldn’t sound strange or incorrect. But when you write, you should try to be more specific.</p>
<p><span style="font-style: italic">over</span> v. <span style="font-style: italic">more than/greater than</span>: This is a classic example of being specific and a classic example of common usage becoming correct usage. <span style="font-style: italic">Merriam Webster’s</span> and <span style="font-style: italic">Chicago Manual of Style</span> will tell you that it is just fine to write, “He makes over thirty thousand dollars a year.” But don’t be surprised if your editor changes that “over” to “more than.” For a long time, it was not correct to use <span style="font-style: italic">over</span> (a term for direction or placement) when you meant <span style="font-style: italic">more than </span>or <span style="font-style: italic">greater than</span>, and <span style="font-style: italic">more than</span> is still more specific.</p>
<p>In the case of <span style="font-style: italic">Common</span> v. <span style="font-style: italic">Correct</span>, the Big Bad Book Blog awards the defendant the point of specificity, but acknowledges the plaintiff’s right to assert itself within the language. It is not our intent to deny the natural evolution of acceptable usage. However, it is best for a writer to err on the side of specificity.</p>
<p>It is so ordered.</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fwww.bigbadbookblog.com%2F2006%2F05%2F17%2Fcommon-v-correct%2F';
  addthis_title  = 'Common+v.+Correct';
  addthis_pub    = '';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://www.bigbadbookblog.com/2006/05/17/common-v-correct/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
