<?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: Day 6: Write a Tech Spec</title>
	<atom:link href="http://coliveira.net/software/day-6-write-a-tech-spec/feed/" rel="self" type="application/rss+xml" />
	<link>http://coliveira.net/software/day-6-write-a-tech-spec/</link>
	<description>Some Ideas by Carlos Oliveira</description>
	<lastBuildDate>Thu, 22 Jul 2010 01:57:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Luca Bernardi</title>
		<link>http://coliveira.net/software/day-6-write-a-tech-spec/comment-page-1/#comment-257</link>
		<dc:creator>Luca Bernardi</dc:creator>
		<pubDate>Fri, 03 Jul 2009 17:27:08 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=385#comment-257</guid>
		<description>I think that writing Tech spec is a realy good practice, but I also think that is really important to spend some time to consider an higher abstraction layer.
I found usefull to start thinking how people will interact with my system...something like a &quot;use case&quot;, this is more informal and I can use a completely informal language mixed up with sketch (or 	
or whatever you prefer).
So in my opinion the workflow should be:
use case -&gt; tech spech -&gt; code (or test if you TDD)
In this way you can gain specificity in small steps.
By the way excellent series of articles</description>
		<content:encoded><![CDATA[<p>I think that writing Tech spec is a realy good practice, but I also think that is really important to spend some time to consider an higher abstraction layer.<br />
I found usefull to start thinking how people will interact with my system&#8230;something like a &#8220;use case&#8221;, this is more informal and I can use a completely informal language mixed up with sketch (or<br />
or whatever you prefer).<br />
So in my opinion the workflow should be:<br />
use case -&gt; tech spech -&gt; code (or test if you TDD)<br />
In this way you can gain specificity in small steps.<br />
By the way excellent series of articles</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: erenNHun</title>
		<link>http://coliveira.net/software/day-6-write-a-tech-spec/comment-page-1/#comment-197</link>
		<dc:creator>erenNHun</dc:creator>
		<pubDate>Wed, 24 Jun 2009 19:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=385#comment-197</guid>
		<description>Thanks for this article. It gives me inspiration in my projects</description>
		<content:encoded><![CDATA[<p>Thanks for this article. It gives me inspiration in my projects</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander</title>
		<link>http://coliveira.net/software/day-6-write-a-tech-spec/comment-page-1/#comment-195</link>
		<dc:creator>Alexander</dc:creator>
		<pubDate>Tue, 23 Jun 2009 13:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://coliveira.net/?p=385#comment-195</guid>
		<description>It&#039;s a very good article!</description>
		<content:encoded><![CDATA[<p>It&#8217;s a very good article!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
