<?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: The 80/20 Rule chop and screwed for WordPress</title>
	<atom:link href="http://ptahdunbar.com/wordpress/the-8020-rule-chop-and-screwed-for-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://ptahdunbar.com/wordpress/the-8020-rule-chop-and-screwed-for-wordpress/</link>
	<description>Web Craftsman, WordPress &#38; BuddyPress hacker, and Entrepreneur</description>
	<lastBuildDate>Mon, 05 Apr 2010 15:32:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Ptah Dunbar</title>
		<link>http://ptahdunbar.com/wordpress/the-8020-rule-chop-and-screwed-for-wordpress/#comment-3027</link>
		<dc:creator>Ptah Dunbar</dc:creator>
		<pubDate>Tue, 30 Dec 2008 02:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://ptahdunbar.com/?p=415#comment-3027</guid>
		<description>@Zed: Hmmm.. Well there seems to be several problems with that kind of thinking.. it would seem to get confusing down the line when earlier adopters are trying to figure out which &quot;type&quot; of WP package they want to install. 

I was thinking that WP should do less, feature wise.. and focus primarily on the architect and providing a great base/framework while letting the community provide all the extensibility via themes/plugins. That way you&#039;ll please everyone (for the most part) and users will be satisfied.</description>
		<content:encoded><![CDATA[<p>@Zed: Hmmm.. Well there seems to be several problems with that kind of thinking.. it would seem to get confusing down the line when earlier adopters are trying to figure out which &#8220;type&#8221; of WP package they want to install. </p>
<p>I was thinking that WP should do less, feature wise.. and focus primarily on the architect and providing a great base/framework while letting the community provide all the extensibility via themes/plugins. That way you&#8217;ll please everyone (for the most part) and users will be satisfied.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zed</title>
		<link>http://ptahdunbar.com/wordpress/the-8020-rule-chop-and-screwed-for-wordpress/#comment-3026</link>
		<dc:creator>zed</dc:creator>
		<pubDate>Sun, 28 Dec 2008 03:53:04 +0000</pubDate>
		<guid isPermaLink="false">http://ptahdunbar.com/?p=415#comment-3026</guid>
		<description>Just curious, but why not just use both, and have 100%? Even if, in the context of &quot;identically purposed&quot; software, it means learning two systems? That kind of perspective is exactly what&#039;s needed to help fill the &quot;last 20%&quot; in on your 80% software, and also what can help you turn a magical 20% into an eventual 40-60-80%. 

I&#039;d say it&#039;s far truer in relationships, though, where it&#039;s not up to &quot;choosing one&quot; - you can easily get over 100% in that situation, which is admittedly harder with the software example.</description>
		<content:encoded><![CDATA[<p>Just curious, but why not just use both, and have 100%? Even if, in the context of &#8220;identically purposed&#8221; software, it means learning two systems? That kind of perspective is exactly what&#8217;s needed to help fill the &#8220;last 20%&#8221; in on your 80% software, and also what can help you turn a magical 20% into an eventual 40-60-80%. </p>
<p>I&#8217;d say it&#8217;s far truer in relationships, though, where it&#8217;s not up to &#8220;choosing one&#8221; &#8211; you can easily get over 100% in that situation, which is admittedly harder with the software example.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
