<?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: My status updates &#8211; what can I improve?</title>
	<atom:link href="http://theunfocused.net/2010/02/24/my-status-updates-improving/feed/" rel="self" type="application/rss+xml" />
	<link>http://theunfocused.net/2010/02/24/my-status-updates-improving/</link>
	<description>And Other Unfocused Things</description>
	<lastBuildDate>Fri, 13 Jan 2012 10:12:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Robert Accettura</title>
		<link>http://theunfocused.net/2010/02/24/my-status-updates-improving/#comment-6525</link>
		<dc:creator>Robert Accettura</dc:creator>
		<pubDate>Wed, 24 Feb 2010 14:48:07 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=407#comment-6525</guid>
		<description>We (the planet team) should really put together a &quot;tips&quot; blog post or something on what we&#039;ve seen works best for folks who want to use a blog as part of their communication.

Some things I&#039;ve personally noted over the years:

1. Repetitive titles stink as noted by other comments.  Theming titles, or prefixing with &quot;status update:&quot; work better. Mention what it&#039;s about in the title.  People scan those to decide if they will read or skip in their feed reader or on planet.
2.  Include links to bugs, wiki&#039;s, and other places for folks to join/participate/feedback when applicable.  It goes a long way.
3.  Avoid just mentioning a bug # without mentioning what it is in context.  Also avoid mentioning a bug and not giving the bug # (or link to bug).  Don&#039;t tease ;-) .
4.  Some more technical discussion can sometimes be much more engaging and encourage readership.  Robert O&#039;Callahan demonstrates this more than anyone these days.
5.  Pictures get folks attention.  Screenshots, mockups, wireframes, cats (preferably in humorous situations with captions).
6.  Demo&#039;s get peoples attention (see hacks.m.o, aza&#039;s blog has that tendency).

I read virtually every mozilla dev blog for the past several years.  I&#039;ve also noticed on my own that the above really makes a distinction between what gets passed over and what gets read/commented on.

Just my $0.02</description>
		<content:encoded><![CDATA[<p>We (the planet team) should really put together a &#8220;tips&#8221; blog post or something on what we&#8217;ve seen works best for folks who want to use a blog as part of their communication.</p>
<p>Some things I&#8217;ve personally noted over the years:</p>
<p>1. Repetitive titles stink as noted by other comments.  Theming titles, or prefixing with &#8220;status update:&#8221; work better. Mention what it&#8217;s about in the title.  People scan those to decide if they will read or skip in their feed reader or on planet.<br />
2.  Include links to bugs, wiki&#8217;s, and other places for folks to join/participate/feedback when applicable.  It goes a long way.<br />
3.  Avoid just mentioning a bug # without mentioning what it is in context.  Also avoid mentioning a bug and not giving the bug # (or link to bug).  Don&#8217;t tease ;-) .<br />
4.  Some more technical discussion can sometimes be much more engaging and encourage readership.  Robert O&#8217;Callahan demonstrates this more than anyone these days.<br />
5.  Pictures get folks attention.  Screenshots, mockups, wireframes, cats (preferably in humorous situations with captions).<br />
6.  Demo&#8217;s get peoples attention (see hacks.m.o, aza&#8217;s blog has that tendency).</p>
<p>I read virtually every mozilla dev blog for the past several years.  I&#8217;ve also noticed on my own that the above really makes a distinction between what gets passed over and what gets read/commented on.</p>
<p>Just my $0.02</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian King</title>
		<link>http://theunfocused.net/2010/02/24/my-status-updates-improving/#comment-6523</link>
		<dc:creator>Brian King</dc:creator>
		<pubDate>Wed, 24 Feb 2010 13:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=407#comment-6523</guid>
		<description>Mitcho&#039;s suggestion is spot-on. Perhaps the date in the title, instead of/as well as keywords.</description>
		<content:encoded><![CDATA[<p>Mitcho&#8217;s suggestion is spot-on. Perhaps the date in the title, instead of/as well as keywords.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shadowbat</title>
		<link>http://theunfocused.net/2010/02/24/my-status-updates-improving/#comment-6522</link>
		<dc:creator>shadowbat</dc:creator>
		<pubDate>Wed, 24 Feb 2010 09:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=407#comment-6522</guid>
		<description>I think some more personality to the updates would be nice. Adding what you like or dislike about the project, some more background, things that could change with your work, whether you liked doing it, about working with your teammates, etc.</description>
		<content:encoded><![CDATA[<p>I think some more personality to the updates would be nice. Adding what you like or dislike about the project, some more background, things that could change with your work, whether you liked doing it, about working with your teammates, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mitcho</title>
		<link>http://theunfocused.net/2010/02/24/my-status-updates-improving/#comment-6521</link>
		<dc:creator>mitcho</dc:creator>
		<pubDate>Wed, 24 Feb 2010 04:35:41 +0000</pubDate>
		<guid isPermaLink="false">http://theunfocused.net/?p=407#comment-6521</guid>
		<description>I always see your status updates on twitter, but the post title is always so generic... just look at it, even your website says &quot;related posts: status update, status update.&quot; Maybe you could add a few key words to the title? :) Thanks.</description>
		<content:encoded><![CDATA[<p>I always see your status updates on twitter, but the post title is always so generic&#8230; just look at it, even your website says &#8220;related posts: status update, status update.&#8221; Maybe you could add a few key words to the title? :) Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

