<?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: Closing the documentation gap</title>
	<atom:link href="http://tech.turbu-rpg.com/104/closing-the-documentation-gap/feed" rel="self" type="application/rss+xml" />
	<link>http://tech.turbu-rpg.com/104/closing-the-documentation-gap</link>
	<description>My thoughts on Delphi programming in general, and particularly on the technical aspects of developing the TURBU engine and editor.</description>
	<lastBuildDate>Sun, 29 Jan 2012 00:52:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jim McKeeth</title>
		<link>http://tech.turbu-rpg.com/104/closing-the-documentation-gap/comment-page-1#comment-222</link>
		<dc:creator>Jim McKeeth</dc:creator>
		<pubDate>Fri, 26 Mar 2010 08:06:42 +0000</pubDate>
		<guid isPermaLink="false">http://tech.turbu-rpg.com/?p=104#comment-222</guid>
		<description>OK, I took your post and ran with it.

http://www.delphi.org/2010/03/delphi-overflow-doc-wiki-initiative/</description>
		<content:encoded><![CDATA[<p>OK, I took your post and ran with it.</p>
<p><a href="http://www.delphi.org/2010/03/delphi-overflow-doc-wiki-initiative/" rel="nofollow">http://www.delphi.org/2010/03/delphi-overflow-doc-wiki-initiative/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Delphi Overflow Doc Wiki Initiative &#45; The Podcast at Delphi.org</title>
		<link>http://tech.turbu-rpg.com/104/closing-the-documentation-gap/comment-page-1#comment-221</link>
		<dc:creator>The Delphi Overflow Doc Wiki Initiative &#45; The Podcast at Delphi.org</dc:creator>
		<pubDate>Fri, 26 Mar 2010 07:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://tech.turbu-rpg.com/?p=104#comment-221</guid>
		<description>[...] was reading Mason&#8217;s post about Stack Overflow closing the Delphi documentation gap where he advocated Embarcadero setting up a new feature of the Delphi Doc Wiki so people could [...]</description>
		<content:encoded><![CDATA[<p>[...] was reading Mason&#8217;s post about Stack Overflow closing the Delphi documentation gap where he advocated Embarcadero setting up a new feature of the Delphi Doc Wiki so people could [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yogi Yang</title>
		<link>http://tech.turbu-rpg.com/104/closing-the-documentation-gap/comment-page-1#comment-215</link>
		<dc:creator>Yogi Yang</dc:creator>
		<pubDate>Fri, 26 Mar 2010 04:49:09 +0000</pubDate>
		<guid isPermaLink="false">http://tech.turbu-rpg.com/?p=104#comment-215</guid>
		<description>There is a facility in SO to make a question, answer, etc. as Wiki.

Can&#039;t Embarcadero just borrow this contents from SO by paying a small fee?

Such a feature should also be implemented into Embarcadero News Groups so any question/reply marked as Wiki should automatically get filed to wiki in some way.

Just an idea!</description>
		<content:encoded><![CDATA[<p>There is a facility in SO to make a question, answer, etc. as Wiki.</p>
<p>Can&#8217;t Embarcadero just borrow this contents from SO by paying a small fee?</p>
<p>Such a feature should also be implemented into Embarcadero News Groups so any question/reply marked as Wiki should automatically get filed to wiki in some way.</p>
<p>Just an idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim McKeeth</title>
		<link>http://tech.turbu-rpg.com/104/closing-the-documentation-gap/comment-page-1#comment-213</link>
		<dc:creator>Jim McKeeth</dc:creator>
		<pubDate>Fri, 26 Mar 2010 02:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://tech.turbu-rpg.com/?p=104#comment-213</guid>
		<description>Maybe a better solution would be for Embarcadero to have a tech writer go through Stack Overflow&#039;s Delphi questions and where appropriate import the interesting bits into the Doc Wiki, then do a little cleaning and copy editing.  More often then not a question answer pair like is found on Delphi would be out of place for the Doc Wiki.</description>
		<content:encoded><![CDATA[<p>Maybe a better solution would be for Embarcadero to have a tech writer go through Stack Overflow&#8217;s Delphi questions and where appropriate import the interesting bits into the Doc Wiki, then do a little cleaning and copy editing.  More often then not a question answer pair like is found on Delphi would be out of place for the Doc Wiki.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joar Bølstad</title>
		<link>http://tech.turbu-rpg.com/104/closing-the-documentation-gap/comment-page-1#comment-212</link>
		<dc:creator>Joar Bølstad</dc:creator>
		<pubDate>Wed, 24 Mar 2010 15:04:49 +0000</pubDate>
		<guid isPermaLink="false">http://tech.turbu-rpg.com/?p=104#comment-212</guid>
		<description>Hi Mason, 

It was me who asked that question. I couldn&#039;t have agreed more, why Experts-Exchange failed to realize what they could&#039;ve become is beyond me. And you&#039;re absolutely right regarding the docs as well: the documentation issues should have been solved directly in the wiki. Except for pricing, I believe the lack of documentation to be the single most important drawback of Delphi.

I think inquiry driven documentation would be very interesting. Documentation based on questions would necessarily answer real world problems. To elaborate a little around your suggestion, consider the following:

A user asks a question in some forum connected to the wiki. The question will enter a question pool. Volunteers can choose to answer questions from the pool, either by creating a new section in an existing article in the wiki (frequently) or create a new article if the question/answer calls for this (rarely). Finally, the question in the question pool will be automatically attached to the submitted content. Right?</description>
		<content:encoded><![CDATA[<p>Hi Mason, </p>
<p>It was me who asked that question. I couldn&#8217;t have agreed more, why Experts-Exchange failed to realize what they could&#8217;ve become is beyond me. And you&#8217;re absolutely right regarding the docs as well: the documentation issues should have been solved directly in the wiki. Except for pricing, I believe the lack of documentation to be the single most important drawback of Delphi.</p>
<p>I think inquiry driven documentation would be very interesting. Documentation based on questions would necessarily answer real world problems. To elaborate a little around your suggestion, consider the following:</p>
<p>A user asks a question in some forum connected to the wiki. The question will enter a question pool. Volunteers can choose to answer questions from the pool, either by creating a new section in an existing article in the wiki (frequently) or create a new article if the question/answer calls for this (rarely). Finally, the question in the question pool will be automatically attached to the submitted content. Right?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

