<?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/"
		>
<channel>
	<title>Comments on: How do You Know When You&#8217;ve Finished a Post?</title>
	<atom:link href="http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/</link>
	<description>Make Money Online</description>
	<lastBuildDate>Sun, 22 Nov 2009 08:03:36 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cris Cuthbertson</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3611029</link>
		<dc:creator>Cris Cuthbertson</dc:creator>
		<pubDate>Mon, 16 Jun 2008 23:38:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3611029</guid>
		<description>Yeah, I will change spelling and bad grammer, but not whole ideas.  

I think it is better to write a new post to expand anything you wanted to change, and it is appropriate to do that to continue the conversation.  If the change is not worth a new post, then it is probably not worth the change.

I proof my posts in a browser window to give myself a different perspective which helps pick up errors.  I also now batch write when I can, so that I have a second proofread immediately before posting.

Cris</description>
		<content:encoded><![CDATA[<p>Yeah, I will change spelling and bad grammer, but not whole ideas.  </p>
<p>I think it is better to write a new post to expand anything you wanted to change, and it is appropriate to do that to continue the conversation.  If the change is not worth a new post, then it is probably not worth the change.</p>
<p>I proof my posts in a browser window to give myself a different perspective which helps pick up errors.  I also now batch write when I can, so that I have a second proofread immediately before posting.</p>
<p>Cris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marek</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3229488</link>
		<dc:creator>Marek</dc:creator>
		<pubDate>Tue, 22 Apr 2008 13:25:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3229488</guid>
		<description>I write for a Dutch blog about cars. This is my opinion on the questions asked by Richard:

- I think rewriting might come across as not totally supporting your own statement. By rewriting it, I feel you take the impact away.

- Should you rewrite (for instance, when it&#039;s a news article and the news has been updated), don&#039;t touch what you&#039;ve already published, but add a section with the new information. Put &quot;&lt;b&gt;Update :&lt;/b&gt;&quot; above the paragraph, so readers can tell that is the piece they haven&#039;t read yet. Also, I put &quot;(Update)&quot; behind the title of the article, so readers know that there has been an update.

- Same answer as the first. Except for when you spot a spelling or grammatical error or a typo, you should always correct those immediately when spotting them, no matter how old the article is.

- If the article which the new idea relates to is still at the top, then you can put it in that article as an update in the way I&#039;ve pointed out in the second answer. If not, post the idea as a new article, but refer to the old article by hyper linking to it in your new article.

- You can use SEO tactics, but I think that blogs will generate traffic if they&#039;re good and genuinely sincere. If you write about something you care for, people will notice it and you will get your deserved attention.

Hope this advice pleases you!

Marek</description>
		<content:encoded><![CDATA[<p>I write for a Dutch blog about cars. This is my opinion on the questions asked by Richard:</p>
<p>- I think rewriting might come across as not totally supporting your own statement. By rewriting it, I feel you take the impact away.</p>
<p>- Should you rewrite (for instance, when it&#8217;s a news article and the news has been updated), don&#8217;t touch what you&#8217;ve already published, but add a section with the new information. Put &#8220;<b>Update :</b>&#8221; above the paragraph, so readers can tell that is the piece they haven&#8217;t read yet. Also, I put &#8220;(Update)&#8221; behind the title of the article, so readers know that there has been an update.</p>
<p>- Same answer as the first. Except for when you spot a spelling or grammatical error or a typo, you should always correct those immediately when spotting them, no matter how old the article is.</p>
<p>- If the article which the new idea relates to is still at the top, then you can put it in that article as an update in the way I&#8217;ve pointed out in the second answer. If not, post the idea as a new article, but refer to the old article by hyper linking to it in your new article.</p>
<p>- You can use SEO tactics, but I think that blogs will generate traffic if they&#8217;re good and genuinely sincere. If you write about something you care for, people will notice it and you will get your deserved attention.</p>
<p>Hope this advice pleases you!</p>
<p>Marek</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren Rowse</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3229113</link>
		<dc:creator>Darren Rowse</dc:creator>
		<pubDate>Tue, 22 Apr 2008 10:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3229113</guid>
		<description>Hope you got some answers here Richard.

My only advice is to try giving yourself a time limit. ie set a deadline when the post will go live and then go with it.</description>
		<content:encoded><![CDATA[<p>Hope you got some answers here Richard.</p>
<p>My only advice is to try giving yourself a time limit. ie set a deadline when the post will go live and then go with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WereBear</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3226065</link>
		<dc:creator>WereBear</dc:creator>
		<pubDate>Mon, 21 Apr 2008 21:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3226065</guid>
		<description>If you find yourself continually tweaking a post, it&#039;s a sign. You either have more to say, and should consider a subsequent post on the same topic, or the ideas are still forming and you should not publish right away.

If your problems are in proofreading, you have gotten some great tips already. But if it&#039;s in the elusive pursuit of perfection; that&#039;s a fool&#039;s game.

Perfection is not given to us. We should strive for excellence... and leave it at that.</description>
		<content:encoded><![CDATA[<p>If you find yourself continually tweaking a post, it&#8217;s a sign. You either have more to say, and should consider a subsequent post on the same topic, or the ideas are still forming and you should not publish right away.</p>
<p>If your problems are in proofreading, you have gotten some great tips already. But if it&#8217;s in the elusive pursuit of perfection; that&#8217;s a fool&#8217;s game.</p>
<p>Perfection is not given to us. We should strive for excellence&#8230; and leave it at that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob O.</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3224272</link>
		<dc:creator>Rob O.</dc:creator>
		<pubDate>Mon, 21 Apr 2008 15:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3224272</guid>
		<description>Sheesh, I got off on a tangent and kinda sidestepped the real question...

I&#039;ve had the problem of not knowing when to say &quot;when&quot; a number of times.  I typically compose my posts off-line over the course of a few hours or even several days - it&#039;s rare that I have time to whip out an entry in a single sitting - so I have plenty of chances to tweak &amp; tune.  Which can easily lead to overthinking or overworking a post...

Sometimes I&#039;ve found that a blog post that I can&#039;t seem to call &quot;finished&quot; is a good opportunity for a series.  Just look for breakpoints and simply spread your article across a short series of posts.  This gives you ample chances to revisit the topic and offers your readers several easy-to-digest, bite-sized goodies.

And of course, leaving a post kinda unfinished or open-ended can often spur responses from your readers...</description>
		<content:encoded><![CDATA[<p>Sheesh, I got off on a tangent and kinda sidestepped the real question&#8230;</p>
<p>I&#8217;ve had the problem of not knowing when to say &#8220;when&#8221; a number of times.  I typically compose my posts off-line over the course of a few hours or even several days &#8211; it&#8217;s rare that I have time to whip out an entry in a single sitting &#8211; so I have plenty of chances to tweak &amp; tune.  Which can easily lead to overthinking or overworking a post&#8230;</p>
<p>Sometimes I&#8217;ve found that a blog post that I can&#8217;t seem to call &#8220;finished&#8221; is a good opportunity for a series.  Just look for breakpoints and simply spread your article across a short series of posts.  This gives you ample chances to revisit the topic and offers your readers several easy-to-digest, bite-sized goodies.</p>
<p>And of course, leaving a post kinda unfinished or open-ended can often spur responses from your readers&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob O.</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3224196</link>
		<dc:creator>Rob O.</dc:creator>
		<pubDate>Mon, 21 Apr 2008 15:45:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3224196</guid>
		<description>For quicky typos or grammatical blunders, I never hesitate to tweak a post.

I think it&#039;s completely legit to edit an older post to provide additional info, a correction, or a link forward from it to a newer, related entry.  I&#039;m not talking about doing a George Lucas-style overhaul, just a minor tweak.  On posts where I do this, I indicate it with a little red &quot;Update&quot; notation, so it&#039;s more apparent.  (You can take a look at my &lt;a href=&quot;http://www.2dolphins.com/2007/06/me-metrosexual.html&quot; title=&quot;Click here to read my &quot;Me, Metrosexual?&quot; blog post on 2Dolphins.com&quot; rel=&quot;nofollow&quot;&gt;Me, Metrosexual?&lt;/a&gt; article for an example.</description>
		<content:encoded><![CDATA[<p>For quicky typos or grammatical blunders, I never hesitate to tweak a post.</p>
<p>I think it&#8217;s completely legit to edit an older post to provide additional info, a correction, or a link forward from it to a newer, related entry.  I&#8217;m not talking about doing a George Lucas-style overhaul, just a minor tweak.  On posts where I do this, I indicate it with a little red &#8220;Update&#8221; notation, so it&#8217;s more apparent.  (You can take a look at my <a href="http://www.2dolphins.com/2007/06/me-metrosexual.html" title="Click here to read my &quot;Me, Metrosexual?&quot; blog post on 2Dolphins.com" rel="nofollow">Me, Metrosexual?</a> article for an example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T.C.</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3220359</link>
		<dc:creator>T.C.</dc:creator>
		<pubDate>Mon, 21 Apr 2008 00:37:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3220359</guid>
		<description>I&#039;m still pretty new at blogging, but so far, I write my posts, edit, and publish in one sitting.  

Once I decide on a topic, I pretty much know what points I want to cover and experiences I want to share.  When I get it all in, I throw in a quick conclusion and start editing.  As I&#039;m writing though, I am constantly re-reading and making sure it flows and make small changes here and there.  As many of the commentors have suggested, once finished I re-read my post out loud to find any errors I&#039;ve missed.

Having a partner is also a good idea.  My blog has two authors anyway, so we constantly bounce ideas off one another and help edit each other&#039;s posts.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still pretty new at blogging, but so far, I write my posts, edit, and publish in one sitting.  </p>
<p>Once I decide on a topic, I pretty much know what points I want to cover and experiences I want to share.  When I get it all in, I throw in a quick conclusion and start editing.  As I&#8217;m writing though, I am constantly re-reading and making sure it flows and make small changes here and there.  As many of the commentors have suggested, once finished I re-read my post out loud to find any errors I&#8217;ve missed.</p>
<p>Having a partner is also a good idea.  My blog has two authors anyway, so we constantly bounce ideas off one another and help edit each other&#8217;s posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slobu</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3220176</link>
		<dc:creator>slobu</dc:creator>
		<pubDate>Sun, 20 Apr 2008 23:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3220176</guid>
		<description>Make a post.  Read it.  Edit it.  Read it.  Edit it.  Read it.  Edit it.  Post and forget (unless new information becomes immediately available.)

It&#039;s easy to obsess over ones one work.  Take the mistakes and comments as lessons for the next post.</description>
		<content:encoded><![CDATA[<p>Make a post.  Read it.  Edit it.  Read it.  Edit it.  Read it.  Edit it.  Post and forget (unless new information becomes immediately available.)</p>
<p>It&#8217;s easy to obsess over ones one work.  Take the mistakes and comments as lessons for the next post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Lierman</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3214382</link>
		<dc:creator>Mike Lierman</dc:creator>
		<pubDate>Sun, 20 Apr 2008 00:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3214382</guid>
		<description>When I start writing an article rarely do I ever have to stop and and reword or move things around (except when I am doing reviews on security software).

I will admit (and I saw this in some above comments) that sometimes (not often though) I will come up with an idea and about half way through I can&#039;t go any farther because I&#039;m missing an important part or it&#039;s not the write time to post it because I posted something like it not too long ago or it&#039;s not the write time to read something like it. Or I will start a post and decide I want to do a different post(s) first.

For the most part though I start writing and the flow just picks right up and I know what to say. In the past I have had problems with that when I didn&#039;t thoroughly re-read and just published it and later found that I had incomplete sentences or thoughts.

See what happen (at least to me) is that once you get in that groove and you are able to just write it, often ideas are mostly there but some sentences are messed up (not just typos). So I have found that I need to re-read at least 2-3 times for a pilliar post and at least 1 good through read. Sometimes if the Pillar post and a crucial part to my blog that I can reference other posts to then I have my friends read it first.


Here is the order I do things:
- Think of the idea and what message I want to get across (this usually works well but don&#039;t spend too much time doing this)

- Type out the article (this is where the groove comes in, I am able to just write it)

- About half way through I check the beginning of the article to the point I am now at and keep the message going (kinda like a Linksys Wireless Extender)

- I usually make my recommendation at the end if the article is a pillar

- I proof read/spell-check and check the layout of the paragraphs 

-I read thoroughly as if I was a reader on my site

-Change anything I need to and post


If anyone wants to see how I write and how I layout my paragraphs (it may or may not help you) feel free to check out my posts on my site: www.techdata.phinxfx.com


Hope my comments help those who don&#039;t know where to begin!
-Michael L.</description>
		<content:encoded><![CDATA[<p>When I start writing an article rarely do I ever have to stop and and reword or move things around (except when I am doing reviews on security software).</p>
<p>I will admit (and I saw this in some above comments) that sometimes (not often though) I will come up with an idea and about half way through I can&#8217;t go any farther because I&#8217;m missing an important part or it&#8217;s not the write time to post it because I posted something like it not too long ago or it&#8217;s not the write time to read something like it. Or I will start a post and decide I want to do a different post(s) first.</p>
<p>For the most part though I start writing and the flow just picks right up and I know what to say. In the past I have had problems with that when I didn&#8217;t thoroughly re-read and just published it and later found that I had incomplete sentences or thoughts.</p>
<p>See what happen (at least to me) is that once you get in that groove and you are able to just write it, often ideas are mostly there but some sentences are messed up (not just typos). So I have found that I need to re-read at least 2-3 times for a pilliar post and at least 1 good through read. Sometimes if the Pillar post and a crucial part to my blog that I can reference other posts to then I have my friends read it first.</p>
<p>Here is the order I do things:<br />
- Think of the idea and what message I want to get across (this usually works well but don&#8217;t spend too much time doing this)</p>
<p>- Type out the article (this is where the groove comes in, I am able to just write it)</p>
<p>- About half way through I check the beginning of the article to the point I am now at and keep the message going (kinda like a Linksys Wireless Extender)</p>
<p>- I usually make my recommendation at the end if the article is a pillar</p>
<p>- I proof read/spell-check and check the layout of the paragraphs </p>
<p>-I read thoroughly as if I was a reader on my site</p>
<p>-Change anything I need to and post</p>
<p>If anyone wants to see how I write and how I layout my paragraphs (it may or may not help you) feel free to check out my posts on my site: <a href="http://www.techdata.phinxfx.com" rel="nofollow">http://www.techdata.phinxfx.com</a></p>
<p>Hope my comments help those who don&#8217;t know where to begin!<br />
-Michael L.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad V.</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3213778</link>
		<dc:creator>Brad V.</dc:creator>
		<pubDate>Sat, 19 Apr 2008 20:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3213778</guid>
		<description>I often write my posts offline, in advance and continue to edit and tweak them before hitting that &quot;Publish&quot; button. Ironically, it&#039;s usually after I publish a post that I end up finding most mistakes and stuff I want to change.

I&#039;m not sure if there&#039;s ever a point where I say &quot;This post is finished&quot; because in theory I could edit and tweak forever. The &quot;endless edit&quot; is almost worst than never editing at all because your post will never get published.</description>
		<content:encoded><![CDATA[<p>I often write my posts offline, in advance and continue to edit and tweak them before hitting that &#8220;Publish&#8221; button. Ironically, it&#8217;s usually after I publish a post that I end up finding most mistakes and stuff I want to change.</p>
<p>I&#8217;m not sure if there&#8217;s ever a point where I say &#8220;This post is finished&#8221; because in theory I could edit and tweak forever. The &#8220;endless edit&#8221; is almost worst than never editing at all because your post will never get published.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3213225</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Sat, 19 Apr 2008 18:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3213225</guid>
		<description>Case in point: I fired off the last post and only read through once before submitting. Now that it&#039;s up, I see that I used the wrong tense &quot;check&quot; when I should have used &quot;checked.&quot; Since this is a comment section, I don&#039;t have the option to go back and fix it, so if I want to make the correction, it will have to be through a new comment. Wonder if that should be the default? That path could lead to endless self-correcting posts...and we&#039;re again left with the question--how do I know when I&#039;m finished? LOL</description>
		<content:encoded><![CDATA[<p>Case in point: I fired off the last post and only read through once before submitting. Now that it&#8217;s up, I see that I used the wrong tense &#8220;check&#8221; when I should have used &#8220;checked.&#8221; Since this is a comment section, I don&#8217;t have the option to go back and fix it, so if I want to make the correction, it will have to be through a new comment. Wonder if that should be the default? That path could lead to endless self-correcting posts&#8230;and we&#8217;re again left with the question&#8211;how do I know when I&#8217;m finished? LOL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3213198</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Sat, 19 Apr 2008 17:57:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3213198</guid>
		<description>Hi, all,

Been following your blog for months, Darren, and consistently find excellent information.

I agree with Doyle and mr.eims about keeping several drafts around to play with. As far as proofreading goes, when you can&#039;t find anyone at 1 a.m. to look at your post, try opening a new draft, copying your original content, then changing the font and size and reading through again. Frequently that will ameliorate &quot;blog blindness&quot; long enough to find errors. 

Another trick, although not as kind to trees, is to print it out and re-read. Sleeping on it is perhaps the best method, but simply walking away from your post and participating in some other activity, preferably healthy, can give you a new perspective and bring you back to the topic refreshed, with new eyes. 

Richard, your question &quot;when am I finished,&quot; reminds me of my favorite dog, Sabine. She was not allowed to beg at the table, but would sit quietly. At some point I would put down my fork, and she would intuitively know that I was finished, even if I didn&#039;t know it myself. 

There comes a time in every piece when you have put all the components together, shuffled paras, added or subtracted modifiers, check for grammar/spelling/punct errors, and that sense of satisfaction and completion is achieved. We are frequently our own worst critics, and if we wrestle and craft our words long enough, we will intuitively know when it is time to either fish or cut bait (which usually means creating a lot of drafts).</description>
		<content:encoded><![CDATA[<p>Hi, all,</p>
<p>Been following your blog for months, Darren, and consistently find excellent information.</p>
<p>I agree with Doyle and mr.eims about keeping several drafts around to play with. As far as proofreading goes, when you can&#8217;t find anyone at 1 a.m. to look at your post, try opening a new draft, copying your original content, then changing the font and size and reading through again. Frequently that will ameliorate &#8220;blog blindness&#8221; long enough to find errors. </p>
<p>Another trick, although not as kind to trees, is to print it out and re-read. Sleeping on it is perhaps the best method, but simply walking away from your post and participating in some other activity, preferably healthy, can give you a new perspective and bring you back to the topic refreshed, with new eyes. </p>
<p>Richard, your question &#8220;when am I finished,&#8221; reminds me of my favorite dog, Sabine. She was not allowed to beg at the table, but would sit quietly. At some point I would put down my fork, and she would intuitively know that I was finished, even if I didn&#8217;t know it myself. </p>
<p>There comes a time in every piece when you have put all the components together, shuffled paras, added or subtracted modifiers, check for grammar/spelling/punct errors, and that sense of satisfaction and completion is achieved. We are frequently our own worst critics, and if we wrestle and craft our words long enough, we will intuitively know when it is time to either fish or cut bait (which usually means creating a lot of drafts).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-2/#comment-3212727</link>
		<dc:creator>Kelly</dc:creator>
		<pubDate>Sat, 19 Apr 2008 15:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3212727</guid>
		<description>Darren, Richard,

Proofread carefully first, but what you missed, you can change. One interesting tip I have heard is that if you discover a typo and leave it, you may get more people commenting, and since people don&#039;t like to leave anything too negative (&quot;You spelled bananana wrong&quot;) all by itself, you&#039;ll probably catch some real thought, too. I am too much of a perfectionist to test this theory.

No to content editing. You liked the wording when you hit publish, move on with no regrets. As many others have said, sit on it a bit longer so you&#039;re sure first, if needed. Blog readers move on fast to your next post and they do not sit and analyze your sentence structure, so don&#039;t you do it either.

New related ideas should *always* go in new posts (linking back is very good), &lt;b&gt;unless&lt;/b&gt; the update truly is an error or something that has changed about what you said and it makes the story different: for instance, if you linked to a company and they no longer offer the product/ service you mentioned, a later reader will be confused or worse, think you don&#039;t know what you&#039;re talking about.

In that case you write at the end of the post or the end of the offending sentence, &quot;UPDATE:&quot; then very briefly explain the change.

Think of it the way newspapers do retractions: is it a material difference to what you wrote or obviously incorrect? Those are updates. Everything else belongs in a new article.

Regards,

Kelly</description>
		<content:encoded><![CDATA[<p>Darren, Richard,</p>
<p>Proofread carefully first, but what you missed, you can change. One interesting tip I have heard is that if you discover a typo and leave it, you may get more people commenting, and since people don&#8217;t like to leave anything too negative (&#8221;You spelled bananana wrong&#8221;) all by itself, you&#8217;ll probably catch some real thought, too. I am too much of a perfectionist to test this theory.</p>
<p>No to content editing. You liked the wording when you hit publish, move on with no regrets. As many others have said, sit on it a bit longer so you&#8217;re sure first, if needed. Blog readers move on fast to your next post and they do not sit and analyze your sentence structure, so don&#8217;t you do it either.</p>
<p>New related ideas should *always* go in new posts (linking back is very good), <b>unless</b> the update truly is an error or something that has changed about what you said and it makes the story different: for instance, if you linked to a company and they no longer offer the product/ service you mentioned, a later reader will be confused or worse, think you don&#8217;t know what you&#8217;re talking about.</p>
<p>In that case you write at the end of the post or the end of the offending sentence, &#8220;UPDATE:&#8221; then very briefly explain the change.</p>
<p>Think of it the way newspapers do retractions: is it a material difference to what you wrote or obviously incorrect? Those are updates. Everything else belongs in a new article.</p>
<p>Regards,</p>
<p>Kelly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Verstraete</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-1/#comment-3212642</link>
		<dc:creator>Chris Verstraete</dc:creator>
		<pubDate>Sat, 19 Apr 2008 14:41:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3212642</guid>
		<description>How do you know when you&#039;re done writing a post?

The main thing is to keep your market/readers in mind: explain the topic thoroughly, but avoid over-explaining. 

Writing for newspapers is good training in writing to length - that &quot;inner editor&quot; teaches you when to stop. Explain your points and avoid adding extras that aren&#039;t relevant. Add those to another post or ask yourself what they&#039;d add? Chances are you don&#039;t even need them. 

Christine Verstraete - http://cverstraete.com
 Coming May &#039;08: &quot;Searching For A Starry Night&quot; - A nosy Dachshund,  a family curse... Can Sam find the missing miniature Van Gogh in time? - Quake/Echelon Press, www.quakeme.com - Blog: http://candidcanine.blogspot.com</description>
		<content:encoded><![CDATA[<p>How do you know when you&#8217;re done writing a post?</p>
<p>The main thing is to keep your market/readers in mind: explain the topic thoroughly, but avoid over-explaining. </p>
<p>Writing for newspapers is good training in writing to length &#8211; that &#8220;inner editor&#8221; teaches you when to stop. Explain your points and avoid adding extras that aren&#8217;t relevant. Add those to another post or ask yourself what they&#8217;d add? Chances are you don&#8217;t even need them. </p>
<p>Christine Verstraete &#8211; <a href="http://cverstraete.com" rel="nofollow">http://cverstraete.com</a><br />
 Coming May &#8216;08: &#8220;Searching For A Starry Night&#8221; &#8211; A nosy Dachshund,  a family curse&#8230; Can Sam find the missing miniature Van Gogh in time? &#8211; Quake/Echelon Press, <a href="http://www.quakeme.com" rel="nofollow">http://www.quakeme.com</a> &#8211; Blog: <a href="http://candidcanine.blogspot.com" rel="nofollow">http://candidcanine.blogspot.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darla</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-1/#comment-3212470</link>
		<dc:creator>Darla</dc:creator>
		<pubDate>Sat, 19 Apr 2008 13:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3212470</guid>
		<description>I usually write it, do a quick read of it, find a mistake, fix mistake, publish.

Once it&#039;s published and live, I do another quick read of the post, usually find another little error, fix it, and republish.

For updates more than 6-12 hours from the time of the original post, I will usually type at the very bottom:

UPDATE

and I make the word UPDATE bold, then type the update after that. 

Hope this helps!</description>
		<content:encoded><![CDATA[<p>I usually write it, do a quick read of it, find a mistake, fix mistake, publish.</p>
<p>Once it&#8217;s published and live, I do another quick read of the post, usually find another little error, fix it, and republish.</p>
<p>For updates more than 6-12 hours from the time of the original post, I will usually type at the very bottom:</p>
<p>UPDATE</p>
<p>and I make the word UPDATE bold, then type the update after that. </p>
<p>Hope this helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tiggy</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-1/#comment-3212392</link>
		<dc:creator>Tiggy</dc:creator>
		<pubDate>Sat, 19 Apr 2008 12:45:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3212392</guid>
		<description>One thing I have discovered - nomatter how many times you proofread and check, after the post has gone live you will *always* find one error!

Also, if you read a post and realize you&#039;ve missed a good point or two, write it down and save it for another post - you may be able to find a different angle for it in time.</description>
		<content:encoded><![CDATA[<p>One thing I have discovered &#8211; nomatter how many times you proofread and check, after the post has gone live you will *always* find one error!</p>
<p>Also, if you read a post and realize you&#8217;ve missed a good point or two, write it down and save it for another post &#8211; you may be able to find a different angle for it in time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mobile blog</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-1/#comment-3212374</link>
		<dc:creator>mobile blog</dc:creator>
		<pubDate>Sat, 19 Apr 2008 12:37:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3212374</guid>
		<description>when i fell tired....and need rest to get new idea</description>
		<content:encoded><![CDATA[<p>when i fell tired&#8230;.and need rest to get new idea</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doyle Slayton</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-1/#comment-3212364</link>
		<dc:creator>Doyle Slayton</dc:creator>
		<pubDate>Sat, 19 Apr 2008 12:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3212364</guid>
		<description>Anytime I have an idea, I create draft.  As the idea builds, I add to the draft.  I normally post a new entry three times a week, so when it comes time to post, I simply go to my drafts and decide which one I want to publish next.  I&#039;ll spend an hour or two tweaking and developing the content.  I double and triple check for spelling and grammar... and then I publish it!

The thing I love most about blogging is the ability to go back and add, subtract, edit, etc.  If I published an article in a magazine... that&#039;s it... I&#039;m stuck with it... but the real power of my blog is that I can always make it better!  I think that what life is all about...  Continuous improvement!

Doyle Slayton
Executive Director &amp; Sales Strategist
www.SalesBlogcast.com</description>
		<content:encoded><![CDATA[<p>Anytime I have an idea, I create draft.  As the idea builds, I add to the draft.  I normally post a new entry three times a week, so when it comes time to post, I simply go to my drafts and decide which one I want to publish next.  I&#8217;ll spend an hour or two tweaking and developing the content.  I double and triple check for spelling and grammar&#8230; and then I publish it!</p>
<p>The thing I love most about blogging is the ability to go back and add, subtract, edit, etc.  If I published an article in a magazine&#8230; that&#8217;s it&#8230; I&#8217;m stuck with it&#8230; but the real power of my blog is that I can always make it better!  I think that what life is all about&#8230;  Continuous improvement!</p>
<p>Doyle Slayton<br />
Executive Director &amp; Sales Strategist<br />
<a href="http://www.SalesBlogcast.com" rel="nofollow">http://www.SalesBlogcast.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Perfect.Blogging</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-1/#comment-3212063</link>
		<dc:creator>Perfect.Blogging</dc:creator>
		<pubDate>Sat, 19 Apr 2008 10:28:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3212063</guid>
		<description>I think you can modify the post after publishing. I don&#039;t see any problems. Everyone makes mistakes so there shouldn&#039;t be any problem.</description>
		<content:encoded><![CDATA[<p>I think you can modify the post after publishing. I don&#8217;t see any problems. Everyone makes mistakes so there shouldn&#8217;t be any problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mr.eims</title>
		<link>http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/comment-page-1/#comment-3211901</link>
		<dc:creator>mr.eims</dc:creator>
		<pubDate>Sat, 19 Apr 2008 09:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.problogger.net/archives/2008/04/19/how-do-you-know-when-youve-finished-a-post/#comment-3211901</guid>
		<description>Drafting the article.. Hurm..maybe you&#039;ll have a few draft which was firstly edited a few days ago. this means you have few days to write the article and inprove the article before become an output.

erm..what I mean is..i call it buffer of articles..hehe..can i use that word..?</description>
		<content:encoded><![CDATA[<p>Drafting the article.. Hurm..maybe you&#8217;ll have a few draft which was firstly edited a few days ago. this means you have few days to write the article and inprove the article before become an output.</p>
<p>erm..what I mean is..i call it buffer of articles..hehe..can i use that word..?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
