<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>To Be - Tag - In a past life…</title>
        <link>https://archive.jtimothyking.com/tags/to-be/</link>
        <description>To Be - Tag - In a past life…</description>
        <generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 07 Mar 2011 19:00:06 &#43;0000</lastBuildDate><atom:link href="https://archive.jtimothyking.com/tags/to-be/" rel="self" type="application/rss+xml" /><item>
    <title>7 Ways to Eradicate the Copulative (How to Get Rid of the Verb &#34;To Be&#34;)</title>
    <link>https://archive.jtimothyking.com/2011/03/07/7-ways-to-eradicate-the-copulative/</link>
    <pubDate>Mon, 07 Mar 2011 19:00:06 &#43;0000</pubDate>
    <author>J. Timothy King</author>
    <guid>https://archive.jtimothyking.com/2011/03/07/7-ways-to-eradicate-the-copulative/</guid>
    <description><![CDATA[<div style="float: right; margin: 0 0 1em 1em"><figure class="alignright size-medium"><a class="lightgallery" href="/2011/03/07/7-ways-to-eradicate-the-copulative/ToBeOrNotToBe-JorgeEl%C3%ADas-enhanced.jpg" title="To Be or Not To Be" data-thumbnail="/2011/03/07/7-ways-to-eradicate-the-copulative/ToBeOrNotToBe-JorgeEl%C3%ADas-enhanced.jpg" data-sub-html="<h2>Photo © 2009 Jorge Elías CC BY 2.0 (source)</h2><p>To Be or Not To Be</p>">
        
    </a><figcaption class="image-caption">Photo © 2009 Jorge Elías CC BY 2.0 <a href="http://www.flickr.com/photos/italintheheart/3647813528/">(source)</a></figcaption></figure></div>
<p>&ldquo;To be, or not to be?&rdquo; <strong><em>Not</em></strong> is usually the answer.</p>
<p>Eliminate the verb &ldquo;to be.&rdquo; This basic writing and revision tip you&rsquo;ll hear all over the place, although much of the advice I&rsquo;ve read is missing important points—or at least points that I consider important.</p>
<p>What do we mean by &ldquo;to be&rdquo; verbs? We mean <em>copulative verbs</em>, also known as &ldquo;linking verbs,&rdquo; that is, verbs that join two different things in the sentence and tie them together. Besides <em>be</em>, look for the words <em>am</em>, <em>are</em>, <em>is</em>, <em>was</em>, <em>were</em>, <em>been</em>, and <em>being</em>.</p>
<p>Why get rid of these words? Because (1) the verb is the most powerful word in your sentence, and (2) these verbs add nothing, nada, zippo, zilch, zero meaning to the sentence. A copulative merely connects other words of the sentence together, foisting on them all of the responsibility that the verb itself ought to take.</p>
<p>But that&rsquo;s not the end of the story! Other words can also be copulatives, words like <em>become</em>, <em>get</em>, <em>feel</em>, and <em>seem</em>. For example: &ldquo;She became a little girl. She got depressed. She felt sad. She seemed unable to go on.&rdquo; If you&rsquo;re going to write that, just be honest and say, &ldquo;She <strong>was</strong> a little girl. She <strong>was</strong> depressed. She <strong>was</strong> sad. She <strong>was</strong> unable to go on.&rdquo; It&rsquo;ll be just as boring.</p>
<p>So what do you do when you discover a &ldquo;to be&rdquo; verb? Here are 7 things you can look at to deal with them.</p>]]></description>
</item>
<item>
    <title>Should You Always Avoid the Verb &#34;To Be&#34;?</title>
    <link>https://archive.jtimothyking.com/2009/12/28/should-you-always-avoid-the-verb-to-be/</link>
    <pubDate>Mon, 28 Dec 2009 18:00:53 &#43;0000</pubDate>
    <author>J. Timothy King</author>
    <guid>https://archive.jtimothyking.com/2009/12/28/should-you-always-avoid-the-verb-to-be/</guid>
    <description><![CDATA[<div style="float: right; margin: 0 0 1em 1em"><figure class="alignright size-medium"><a class="lightgallery" href="/2009/12/28/should-you-always-avoid-the-verb-to-be/ToBeOrNotToBe-JorgeEl%C3%ADas-enhanced.jpg" title="To Be or Not To Be, by Jorge Elías" data-thumbnail="/2009/12/28/should-you-always-avoid-the-verb-to-be/ToBeOrNotToBe-JorgeEl%C3%ADas-enhanced.jpg" data-sub-html="<h2>Photo © 2009 Jorge Elías CC BY 2.0 (source)</h2><p>To Be or Not To Be, by Jorge Elías</p>">
        
    </a><figcaption class="image-caption">Photo © 2009 Jorge Elías CC BY 2.0 <a href="http://www.flickr.com/photos/italintheheart/3647813528/">(source)</a></figcaption></figure></div>
<p>A fundamental rule of style is that you should avoid the verb &ldquo;to be,&rdquo; preferring instead strong, descriptive verbs that show, rather than tell.</p>
<p>As an example, instead of writing, &ldquo;The light was bright,&rdquo; you should prefer, &ldquo;The light blinded her as a hot-white flame,&rdquo; or some such. So every time you use <em>am</em>, <em>is</em>, <em>are</em>, <em>was</em>, <em>were</em>, <em>be</em>, <em>been</em>, or <em>being</em>, that&rsquo;s a signal that you need to rephrase&hellip;</p>
<h3>EXCEPT...</h3>
<p>As it turns out, this common rule of thumb oversimplifies the issue, sometimes to the point that confusion can result.</p>
<p>No less a writer than Holly Lisle gives a misleading example, on her web page about <a href="http://hollylisle.com/fm/Workshops/one-pass-revision.html">one-pass manuscript revision</a>:</p>
<blockquote>
<p>Is your scene full of weak words? How many times have you used is, was, or were?&hellip; Eliminate forms of the verb “to be” wherever you find them, rewriting the sentence with a stronger verb. “It was raining,” becomes “The rain slashed down, tearing up the gardens and ripping leaves from the trees.”</p>
</blockquote>
<p>But the verb in that sentence is <strong>not</strong> the verb &ldquo;to be&rdquo;!</p>]]></description>
</item>
</channel>
</rss>
