<?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: Z is sexier than A</title>
	<atom:link href="http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/feed/" rel="self" type="application/rss+xml" />
	<link>http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/</link>
	<description></description>
	<lastBuildDate>Thu, 04 Mar 2010 04:13:37 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: @sarahmerion</title>
		<link>http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/comment-page-1/#comment-2518</link>
		<dc:creator>@sarahmerion</dc:creator>
		<pubDate>Tue, 16 Jun 2009 17:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://sarahmerion.com/?p=214#comment-2518</guid>
		<description>That&#039;s exactly why jumping to Z is usually productive if you approach your project correctly.  It allows you to see the bugs, the flaws, and the mistakes as you&#039;re working inside the project.  A lot of tweaks that need to happen can&#039;t be found out until you&#039;re under way and jumping to Z is a good way to get there quicker.</description>
		<content:encoded><![CDATA[<p>That&#39;s exactly why jumping to Z is usually productive if you approach your project correctly.  It allows you to see the bugs, the flaws, and the mistakes as you&#39;re working inside the project.  A lot of tweaks that need to happen can&#39;t be found out until you&#39;re under way and jumping to Z is a good way to get there quicker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdamPieniazek</title>
		<link>http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/comment-page-1/#comment-2517</link>
		<dc:creator>AdamPieniazek</dc:creator>
		<pubDate>Tue, 16 Jun 2009 16:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://sarahmerion.com/?p=214#comment-2517</guid>
		<description>Interesting idea, though I feel that you can jump to Z but will likely have to go back and do some of the other letters anyway.&lt;br&gt;&lt;br&gt;For instance, take web design. You can sort of jump to Z but doing a rough mockup/photoshop example, but in the end you still have to go in and code everything.&lt;br&gt;&lt;br&gt;I&#039;m doing a jump to Z sort of with SP by doing a rough mockup and then going back and redesigning everything and coding all the bits and pieces. But the jump to Z lets me show a rough version of what the real final product will look like.</description>
		<content:encoded><![CDATA[<p>Interesting idea, though I feel that you can jump to Z but will likely have to go back and do some of the other letters anyway.</p>
<p>For instance, take web design. You can sort of jump to Z but doing a rough mockup/photoshop example, but in the end you still have to go in and code everything.</p>
<p>I&#39;m doing a jump to Z sort of with SP by doing a rough mockup and then going back and redesigning everything and coding all the bits and pieces. But the jump to Z lets me show a rough version of what the real final product will look like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @sarahmerion</title>
		<link>http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/comment-page-1/#comment-2417</link>
		<dc:creator>@sarahmerion</dc:creator>
		<pubDate>Tue, 16 Jun 2009 14:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://sarahmerion.com/?p=214#comment-2417</guid>
		<description>That&#039;s exactly why jumping to Z is usually productive if you approach your project correctly.  It allows you to see the bugs, the flaws, and the mistakes as you&#039;re working inside the project.  A lot of tweaks that need to happen can&#039;t be found out until you&#039;re under way and jumping to Z is a good way to get there quicker.</description>
		<content:encoded><![CDATA[<p>That&#39;s exactly why jumping to Z is usually productive if you approach your project correctly.  It allows you to see the bugs, the flaws, and the mistakes as you&#39;re working inside the project.  A lot of tweaks that need to happen can&#39;t be found out until you&#39;re under way and jumping to Z is a good way to get there quicker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdamPieniazek</title>
		<link>http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/comment-page-1/#comment-2416</link>
		<dc:creator>AdamPieniazek</dc:creator>
		<pubDate>Tue, 16 Jun 2009 13:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://sarahmerion.com/?p=214#comment-2416</guid>
		<description>Interesting idea, though I feel that you can jump to Z but will likely have to go back and do some of the other letters anyway.&lt;br&gt;&lt;br&gt;For instance, take web design. You can sort of jump to Z but doing a rough mockup/photoshop example, but in the end you still have to go in and code everything.&lt;br&gt;&lt;br&gt;I&#039;m doing a jump to Z sort of with SP by doing a rough mockup and then going back and redesigning everything and coding all the bits and pieces. But the jump to Z lets me show a rough version of what the real final product will look like.</description>
		<content:encoded><![CDATA[<p>Interesting idea, though I feel that you can jump to Z but will likely have to go back and do some of the other letters anyway.</p>
<p>For instance, take web design. You can sort of jump to Z but doing a rough mockup/photoshop example, but in the end you still have to go in and code everything.</p>
<p>I&#39;m doing a jump to Z sort of with SP by doing a rough mockup and then going back and redesigning everything and coding all the bits and pieces. But the jump to Z lets me show a rough version of what the real final product will look like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jamesconnors</title>
		<link>http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/comment-page-1/#comment-2413</link>
		<dc:creator>jamesconnors</dc:creator>
		<pubDate>Mon, 15 Jun 2009 18:59:53 +0000</pubDate>
		<guid isPermaLink="false">http://sarahmerion.com/?p=214#comment-2413</guid>
		<description>The 7 P&#039;s are global and infallible.</description>
		<content:encoded><![CDATA[<p>The 7 P&#39;s are global and infallible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @sarahmerion</title>
		<link>http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/comment-page-1/#comment-2412</link>
		<dc:creator>@sarahmerion</dc:creator>
		<pubDate>Mon, 15 Jun 2009 18:57:49 +0000</pubDate>
		<guid isPermaLink="false">http://sarahmerion.com/?p=214#comment-2412</guid>
		<description>I do agree. Maybe I should have said X is sexier than A.  Or even R or Q is sexier than A.  I should have expanded more to say that some planning, like you say, is necessary.  For example, I had a plan in my head and very clear goals/intentions for my tweetup.  I&#039;d say that I started at Q for my tweetup and worked my way back.&lt;br&gt;&lt;br&gt;Good points James.  And I love your saying: Proper Prior Planning Prevents Piss Poor Performance.</description>
		<content:encoded><![CDATA[<p>I do agree. Maybe I should have said X is sexier than A.  Or even R or Q is sexier than A.  I should have expanded more to say that some planning, like you say, is necessary.  For example, I had a plan in my head and very clear goals/intentions for my tweetup.  I&#39;d say that I started at Q for my tweetup and worked my way back.</p>
<p>Good points James.  And I love your saying: Proper Prior Planning Prevents Piss Poor Performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Connors</title>
		<link>http://sarahmerion.com/digitalanthropology/z-is-sexier-than-a/comment-page-1/#comment-2411</link>
		<dc:creator>James Connors</dc:creator>
		<pubDate>Mon, 15 Jun 2009 18:25:20 +0000</pubDate>
		<guid isPermaLink="false">http://sarahmerion.com/?p=214#comment-2411</guid>
		<description>I have an issue with this sort of mentality.  I agree with you that when you&#039;re planning something, it is often better to get started without having an entire plan settled.  HOWEVER, doing so without a clear idea of what your framework will be can be very dangerous/disruptive (in a bad way).  &lt;br&gt;&lt;br&gt;For example, starting a business without a plan for profit will fail before it gets off the ground and could pull your personal finances into a blackhole if good planning didn&#039;t take place well in advance.&lt;br&gt;&lt;br&gt;Proper Prior Planning Prevents Piss Poor Performance.</description>
		<content:encoded><![CDATA[<p>I have an issue with this sort of mentality.  I agree with you that when you&#39;re planning something, it is often better to get started without having an entire plan settled.  HOWEVER, doing so without a clear idea of what your framework will be can be very dangerous/disruptive (in a bad way).  </p>
<p>For example, starting a business without a plan for profit will fail before it gets off the ground and could pull your personal finances into a blackhole if good planning didn&#39;t take place well in advance.</p>
<p>Proper Prior Planning Prevents Piss Poor Performance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
