<?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: Diminishing the Role of Folklore in Software Development</title>
	<atom:link href="http://blog.slickedit.com/2009/09/diminishing-the-role-of-folklore-in-software-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.slickedit.com/2009/09/diminishing-the-role-of-folklore-in-software-development/</link>
	<description>&#34;Hello World&#34; - The SlickEdit Developer Blog</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:18:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Scott Westfall</title>
		<link>http://blog.slickedit.com/2009/09/diminishing-the-role-of-folklore-in-software-development/comment-page-1/#comment-734</link>
		<dc:creator>Scott Westfall</dc:creator>
		<pubDate>Mon, 14 Sep 2009 14:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.slickedit.com/?p=347#comment-734</guid>
		<description>Ultimately, wiki maintenance is an issue of discipline and professionalism. Discipline is the mental toughness to follow through on a task. Professionalism is the drive to work in a manner that reflects the best practices of your field. There is no replacement for these characteristics. No amount of management or automation will produce the same results. 

In general, people will maintain the wiki if they see that it is a valuable tool in getting their work done. Otherwise, it&#039;s just another bureaucratic distraction.</description>
		<content:encoded><![CDATA[<p>Ultimately, wiki maintenance is an issue of discipline and professionalism. Discipline is the mental toughness to follow through on a task. Professionalism is the drive to work in a manner that reflects the best practices of your field. There is no replacement for these characteristics. No amount of management or automation will produce the same results. </p>
<p>In general, people will maintain the wiki if they see that it is a valuable tool in getting their work done. Otherwise, it&#8217;s just another bureaucratic distraction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Thomas</title>
		<link>http://blog.slickedit.com/2009/09/diminishing-the-role-of-folklore-in-software-development/comment-page-1/#comment-729</link>
		<dc:creator>Patrick Thomas</dc:creator>
		<pubDate>Fri, 11 Sep 2009 02:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.slickedit.com/?p=347#comment-729</guid>
		<description>I agree that the &quot;capability to create a browseable structure [that] sets MediaWiki apart from other wiki software we tried&quot;, same goes for our telepark.wiki, but how do you &quot;make the wiki an essential part of the problem solving process&quot;? Making a note to comeback when one is querying the wiki and not finding an answer should be a process within and supported by the wiki, i.e. a todo list. That means for the wiki to feature some transactional and database-type functionality (none do out of the box, to my knowledge, but some allow extensions to be programmed).</description>
		<content:encoded><![CDATA[<p>I agree that the &#8220;capability to create a browseable structure [that] sets MediaWiki apart from other wiki software we tried&#8221;, same goes for our telepark.wiki, but how do you &#8220;make the wiki an essential part of the problem solving process&#8221;? Making a note to comeback when one is querying the wiki and not finding an answer should be a process within and supported by the wiki, i.e. a todo list. That means for the wiki to feature some transactional and database-type functionality (none do out of the box, to my knowledge, but some allow extensions to be programmed).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Mei</title>
		<link>http://blog.slickedit.com/2009/09/diminishing-the-role-of-folklore-in-software-development/comment-page-1/#comment-724</link>
		<dc:creator>Sarah Mei</dc:creator>
		<pubDate>Thu, 10 Sep 2009 16:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.slickedit.com/?p=347#comment-724</guid>
		<description>One other barrier I&#039;ve found is that it&#039;s no one&#039;s job to maintain the wiki. That&#039;s sort of the idea; it&#039;s collaboratively edited. But if the app is big enough and the wiki around for long enough, it&#039;ll acquire cruft: old information that&#039;s only relevant to a previous release (but not marked as such), pages put up by someone who&#039;s no longer around to clarify vague statements...etc. 

Once the wiki idea takes off, make it someone&#039;s job to go through once a week or once a month, or whatever, and clean out the cruft.</description>
		<content:encoded><![CDATA[<p>One other barrier I&#8217;ve found is that it&#8217;s no one&#8217;s job to maintain the wiki. That&#8217;s sort of the idea; it&#8217;s collaboratively edited. But if the app is big enough and the wiki around for long enough, it&#8217;ll acquire cruft: old information that&#8217;s only relevant to a previous release (but not marked as such), pages put up by someone who&#8217;s no longer around to clarify vague statements&#8230;etc. </p>
<p>Once the wiki idea takes off, make it someone&#8217;s job to go through once a week or once a month, or whatever, and clean out the cruft.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

