<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The New Writer: Writing Advice from Your Past You Should Ignore</title>
	<atom:link href="http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 05:49:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: LynCat</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89356</link>
		<dc:creator><![CDATA[LynCat]]></dc:creator>
		<pubDate>Tue, 17 Nov 2009 14:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89356</guid>
		<description><![CDATA[Oh please, please, please, write with a Brit accent! I&#039;ve craved those expressions for decades...one&#039;s such as &quot;on your bike&quot;, &quot;put a sock in it&quot;, &quot;how about a leg over, luv?&quot;. They bring back memories from the &#039;70s when I worked as an entertainer on a British cruise ship (the Spirit of London, later to become TV&#039;s Love Boat - for the full story of this particular train wreck (ship wreck?) see http://pimpmycruise.com/mod/customindex/ourstory.php). - LC]]></description>
		<content:encoded><![CDATA[<p>Oh please, please, please, write with a Brit accent! I&#8217;ve craved those expressions for decades&#8230;one&#8217;s such as &#8220;on your bike&#8221;, &#8220;put a sock in it&#8221;, &#8220;how about a leg over, luv?&#8221;. They bring back memories from the &#8217;70s when I worked as an entertainer on a British cruise ship (the Spirit of London, later to become TV&#8217;s Love Boat &#8211; for the full story of this particular train wreck (ship wreck?) see <a href="http://pimpmycruise.com/mod/customindex/ourstory.php" rel="nofollow">http://pimpmycruise.com/mod/customindex/ourstory.php</a>). &#8211; LC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jennifer</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89355</link>
		<dc:creator><![CDATA[Jennifer]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 16:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89355</guid>
		<description><![CDATA[Just this weekend I gave a talk about communicating effectively online. One of my main points was &quot;Don&#039;t let perfect grammar get in the way of an effective message and a consistent voice.&quot; Nobody adheres to strict rules of grammar when they speak, and the web is (usually) an informal and conversational medium for communications.

And I also agree with the spirit behind point #1. I write for a large variety of different clients, and there is often a huge learning curve when it comes to writing content in a new subject area. As a professional, it&#039;s my job to do the work of learning what I need to know. So I agree--Know what you write!]]></description>
		<content:encoded><![CDATA[<p>Just this weekend I gave a talk about communicating effectively online. One of my main points was &#8220;Don&#8217;t let perfect grammar get in the way of an effective message and a consistent voice.&#8221; Nobody adheres to strict rules of grammar when they speak, and the web is (usually) an informal and conversational medium for communications.</p>
<p>And I also agree with the spirit behind point #1. I write for a large variety of different clients, and there is often a huge learning curve when it comes to writing content in a new subject area. As a professional, it&#8217;s my job to do the work of learning what I need to know. So I agree&#8211;Know what you write!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kaye</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89353</link>
		<dc:creator><![CDATA[David Kaye]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 15:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89353</guid>
		<description><![CDATA[Like Dennis, I disagree with where you went on point 1. But it does seem to describe journalism. Great stories here. Facts and understanding? Not so much.

Speaking of journalism... You wrote a good op-ed zinger to create controversy and feedback! (You win! Here are the replies!) You advertised it nicely by juxtaposing &quot;Honestly&quot; and &quot;to fool&quot; in the same sentence.

You don&#039;t have to be an expert to write about a subject; you have to be a writer. You can research quickly and efficiently to gain a comfortable grasp of your subject. Then write about it. If you are not sure of your facts and assertions, get your piece checked by an expert before publishing.]]></description>
		<content:encoded><![CDATA[<p>Like Dennis, I disagree with where you went on point 1. But it does seem to describe journalism. Great stories here. Facts and understanding? Not so much.</p>
<p>Speaking of journalism&#8230; You wrote a good op-ed zinger to create controversy and feedback! (You win! Here are the replies!) You advertised it nicely by juxtaposing &#8220;Honestly&#8221; and &#8220;to fool&#8221; in the same sentence.</p>
<p>You don&#8217;t have to be an expert to write about a subject; you have to be a writer. You can research quickly and efficiently to gain a comfortable grasp of your subject. Then write about it. If you are not sure of your facts and assertions, get your piece checked by an expert before publishing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FreelanceWise</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89354</link>
		<dc:creator><![CDATA[FreelanceWise]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 15:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89354</guid>
		<description><![CDATA[Hi

I&#039;m very loose when it comes to following grammar rules. Sometimes doing it the &quot;proper&quot; way simply doesn&#039;t seem to give the correct feeling to a sentence.

Juliet]]></description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>I&#8217;m very loose when it comes to following grammar rules. Sometimes doing it the &#8220;proper&#8221; way simply doesn&#8217;t seem to give the correct feeling to a sentence.</p>
<p>Juliet</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TonyCurtis</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89352</link>
		<dc:creator><![CDATA[TonyCurtis]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 14:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89352</guid>
		<description><![CDATA[Oops, forgot one other thing:

When I was more active on Twitter, I sure learned how to speak as efficiently as possible. Abbreviating words for that is one thing, but writing a succint and direct sentence that grabs attention is another. Try to spend a day replying to any work emails like it&#039;s a twitter feed, and you&#039;ll get a lot of action items done!!!]]></description>
		<content:encoded><![CDATA[<p>Oops, forgot one other thing:</p>
<p>When I was more active on Twitter, I sure learned how to speak as efficiently as possible. Abbreviating words for that is one thing, but writing a succint and direct sentence that grabs attention is another. Try to spend a day replying to any work emails like it&#8217;s a twitter feed, and you&#8217;ll get a lot of action items done!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TonyCurtis</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89351</link>
		<dc:creator><![CDATA[TonyCurtis]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 14:25:54 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89351</guid>
		<description><![CDATA[I am very much against the current downward spiral in online writing skills. I&#039;m (see what I did there?) by no means an English major, but there are some very simple and terrible mistakes I see over and over in online writing, and sometimes the conversational tone can be so casual that it makes for an overly wordy and confusing article. In some cases, a story is casual to the point that I can&#039;t take the validity of the argument seriously.

As the world gets &quot;closer&quot; because of the internet, we also have an olbigation to make things easier to digest if we are trying to do international business or working with people who do not have strong English or technical language skills.

Rule of thumb: I always write tech like I&#039;m writing to explain it to my grandmother. Conversation, but to the point, and avoiding too many inside references/slang.

Nice article, though. I enjoy Webworkerdaily.]]></description>
		<content:encoded><![CDATA[<p>I am very much against the current downward spiral in online writing skills. I&#8217;m (see what I did there?) by no means an English major, but there are some very simple and terrible mistakes I see over and over in online writing, and sometimes the conversational tone can be so casual that it makes for an overly wordy and confusing article. In some cases, a story is casual to the point that I can&#8217;t take the validity of the argument seriously.</p>
<p>As the world gets &#8220;closer&#8221; because of the internet, we also have an olbigation to make things easier to digest if we are trying to do international business or working with people who do not have strong English or technical language skills.</p>
<p>Rule of thumb: I always write tech like I&#8217;m writing to explain it to my grandmother. Conversation, but to the point, and avoiding too many inside references/slang.</p>
<p>Nice article, though. I enjoy Webworkerdaily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ileaneb</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89350</link>
		<dc:creator><![CDATA[ileaneb]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 14:20:28 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89350</guid>
		<description><![CDATA[I read a post the other day about over usage of the word &quot;that&quot;. Perhaps it&#039;s true that I use it too much, but there are so many instances that I can&#039;t do without it. lol

Love, love, love, using contractions. Mostly because of the 140 character thingy that I resort to several times a day (better known as Twitter).

Thanks for the post!
@Ileane]]></description>
		<content:encoded><![CDATA[<p>I read a post the other day about over usage of the word &#8220;that&#8221;. Perhaps it&#8217;s true that I use it too much, but there are so many instances that I can&#8217;t do without it. lol</p>
<p>Love, love, love, using contractions. Mostly because of the 140 character thingy that I resort to several times a day (better known as Twitter).</p>
<p>Thanks for the post!<br />
@Ileane</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internet Cafe Solution &#187; Blog Archive &#187; The New Writer: Writing Advice from Your Past You Should Ignore</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89349</link>
		<dc:creator><![CDATA[Internet Cafe Solution &#187; Blog Archive &#187; The New Writer: Writing Advice from Your Past You Should Ignore]]></dc:creator>
		<pubDate>Mon, 16 Nov 2009 14:18:19 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89349</guid>
		<description><![CDATA[[...] more here:  The New Writer: Writing Advice from Your Past You Should Ignore  This entry was posted on Saturday, November 14th, 2009 at 8:00 am and is filed under Writing. You [...]]]></description>
		<content:encoded><![CDATA[<p>[...] more here:  The New Writer: Writing Advice from Your Past You Should Ignore  This entry was posted on Saturday, November 14th, 2009 at 8:00 am and is filed under Writing. You [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89348</link>
		<dc:creator><![CDATA[Matthew]]></dc:creator>
		<pubDate>Sun, 15 Nov 2009 23:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89348</guid>
		<description><![CDATA[As someone who writes several articles a day online the main rule I break is spelling as I live in the UK but write for a U.S. audience. Organize not organise, color not colour, and a few quirky ones such as not using &quot;straight away&quot; in a sentence.

I agree that writing regularly does help a lot and you get to a point where you can switch your style/s on and off depending on the subject matter.]]></description>
		<content:encoded><![CDATA[<p>As someone who writes several articles a day online the main rule I break is spelling as I live in the UK but write for a U.S. audience. Organize not organise, color not colour, and a few quirky ones such as not using &#8220;straight away&#8221; in a sentence.</p>
<p>I agree that writing regularly does help a lot and you get to a point where you can switch your style/s on and off depending on the subject matter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Mackie</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89347</link>
		<dc:creator><![CDATA[Simon Mackie]]></dc:creator>
		<pubDate>Sun, 15 Nov 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89347</guid>
		<description><![CDATA[As the editor, that&#039;s my fault, not Darrell&#039;s -- I should have spotted those. Now fixed, thanks, Alan.

However, I don&#039;t think a couple of minor typos invalidate Darrell&#039;s point, which is that getting your material out there is often better than sitting on it, endlessly revising.]]></description>
		<content:encoded><![CDATA[<p>As the editor, that&#8217;s my fault, not Darrell&#8217;s &#8212; I should have spotted those. Now fixed, thanks, Alan.</p>
<p>However, I don&#8217;t think a couple of minor typos invalidate Darrell&#8217;s point, which is that getting your material out there is often better than sitting on it, endlessly revising.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89346</link>
		<dc:creator><![CDATA[Alan]]></dc:creator>
		<pubDate>Sun, 15 Nov 2009 13:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89346</guid>
		<description><![CDATA[&quot;if if&quot; and &quot;with with&quot;.  Your own writing disproved #3.]]></description>
		<content:encoded><![CDATA[<p>&#8220;if if&#8221; and &#8220;with with&#8221;.  Your own writing disproved #3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vijay</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89345</link>
		<dc:creator><![CDATA[Vijay]]></dc:creator>
		<pubDate>Sat, 14 Nov 2009 23:34:48 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89345</guid>
		<description><![CDATA[I believe both Dennis and Darrell are right, hence both are wrong - that is, the truth lies somewhere between the two approaches of &#039;knowing what your write&#039; and &#039;learning as you go on writing&#039;. I&#039;m talking from my experience alone, of course.
When I wrote the business dictionary Infotool (the largest lexicon of its kind in English with over 20,000 definitions) I tried to be as comprehensive as possible while being as concise and clear as possible. That meant learning at least the basics of some 100 subjects associated with the world of business in one way or the other. These subjects range from Accounting to Workplace Safety and practically everything in between including Economics, Law, IT, Psychology, Sociology ... you name it. In the beginning I knew only a few of them but immersed myself in every topic to learn it so well that I could explain it in everyday language. Thus the endeavor was a combination of both approaches, as the situation required. Did I succeed in achieving my objectives? Well, judge it for yourself by checking the terms at www.businessdictionary.com!]]></description>
		<content:encoded><![CDATA[<p>I believe both Dennis and Darrell are right, hence both are wrong &#8211; that is, the truth lies somewhere between the two approaches of &#8216;knowing what your write&#8217; and &#8216;learning as you go on writing&#8217;. I&#8217;m talking from my experience alone, of course.<br />
When I wrote the business dictionary Infotool (the largest lexicon of its kind in English with over 20,000 definitions) I tried to be as comprehensive as possible while being as concise and clear as possible. That meant learning at least the basics of some 100 subjects associated with the world of business in one way or the other. These subjects range from Accounting to Workplace Safety and practically everything in between including Economics, Law, IT, Psychology, Sociology &#8230; you name it. In the beginning I knew only a few of them but immersed myself in every topic to learn it so well that I could explain it in everyday language. Thus the endeavor was a combination of both approaches, as the situation required. Did I succeed in achieving my objectives? Well, judge it for yourself by checking the terms at <a href="http://www.businessdictionary.com" rel="nofollow">http://www.businessdictionary.com</a>!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://gigaom.com/collaboration/the-new-writer-writing-advice-from-your-past-you-should-ignore/#comment-89344</link>
		<dc:creator><![CDATA[Dennis]]></dc:creator>
		<pubDate>Sat, 14 Nov 2009 17:27:15 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/?p=22751#comment-89344</guid>
		<description><![CDATA[I&#039;ll certainly go along with #2 on your list (see what I just did there? ;-), as it really does contribute to a conversational style that can be quicker and easier for the reader to digest. And since we&#039;re all deluged with too much stuff to read as it is, anything that can contribute to a quicker read is probably a good thing. And I would probably throw out a few of the grammatical rules, also; such as not starting sentences with conjunctions or prepositions. But as for the other two...

&quot;Revise, revise, revise&quot; - I would perhaps change this to just &quot;revise&quot;. Excessive revision, as you point out, can certainly detract from the immediacy of the information and lead to &#039;analysis paralysis&#039;. But a good one-time-over proofreading can certainly help in catching glaring deficiencies. And I certainly wouldn&#039;t hold the drivel that passes for Twitter up as a reason to pass up a good single-pass revision.

As for &quot;write what you know&quot;, I would have to disagree. Trying to pass for being knowledgeable in an area where you are not is only self-serving, providing the writer a means of sharing their ignorance with others. The real danger here is that you are often doing a disservice to your readers by providing them with bad information. I think this especially holds true in the arena of so-called &quot;consumer advice&quot;. In particular, having been involved in a wide variety of real estate practice for 30 years, it has been appalling to me to see some of the ill considered and downright wrong articles written by &quot;journalists&quot; about this subject. And someone who truly is knowledgeable in the field that you are writing about will see right through you. If you&#039;re not knowledgeable about a certain subject, and still choose to write about it, then at least admit that fact to your audience. Any other approach is just downright deceptive and constitutes outright lying and cheating.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ll certainly go along with #2 on your list (see what I just did there? ;-), as it really does contribute to a conversational style that can be quicker and easier for the reader to digest. And since we&#8217;re all deluged with too much stuff to read as it is, anything that can contribute to a quicker read is probably a good thing. And I would probably throw out a few of the grammatical rules, also; such as not starting sentences with conjunctions or prepositions. But as for the other two&#8230;</p>
<p>&#8220;Revise, revise, revise&#8221; &#8211; I would perhaps change this to just &#8220;revise&#8221;. Excessive revision, as you point out, can certainly detract from the immediacy of the information and lead to &#8216;analysis paralysis&#8217;. But a good one-time-over proofreading can certainly help in catching glaring deficiencies. And I certainly wouldn&#8217;t hold the drivel that passes for Twitter up as a reason to pass up a good single-pass revision.</p>
<p>As for &#8220;write what you know&#8221;, I would have to disagree. Trying to pass for being knowledgeable in an area where you are not is only self-serving, providing the writer a means of sharing their ignorance with others. The real danger here is that you are often doing a disservice to your readers by providing them with bad information. I think this especially holds true in the arena of so-called &#8220;consumer advice&#8221;. In particular, having been involved in a wide variety of real estate practice for 30 years, it has been appalling to me to see some of the ill considered and downright wrong articles written by &#8220;journalists&#8221; about this subject. And someone who truly is knowledgeable in the field that you are writing about will see right through you. If you&#8217;re not knowledgeable about a certain subject, and still choose to write about it, then at least admit that fact to your audience. Any other approach is just downright deceptive and constitutes outright lying and cheating.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

