<?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 thingamy manifesto</title>
	<atom:link href="http://gapingvoid.com/2007/01/08/the-thingamy-manifesto/feed/" rel="self" type="application/rss+xml" />
	<link>http://gapingvoid.com/2007/01/08/the-thingamy-manifesto/</link>
	<description>&#34;cartoons drawn on the back of business cards&#34;</description>
	<lastBuildDate>Fri, 10 Feb 2012 23:17:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Steve Borthwick</title>
		<link>http://gapingvoid.com/2007/01/08/the-thingamy-manifesto/#comment-16444</link>
		<dc:creator>Steve Borthwick</dc:creator>
		<pubDate>Wed, 10 Jan 2007 02:57:56 +0000</pubDate>
		<guid isPermaLink="false">http://gapingvoid.com/?p=3410#comment-16444</guid>
		<description>It&#039;s nice to hear about other small software companies and their ideas, most firms seem to be too paranoid to share any (real) information or vision during their development process - you just get the same old corporate happy-talk (thanks for that phrase Hugh, I use it a lot!).
I agree with all but one of these, I don&#039;t get the big thing about tree structures?
What we try to do at my little software outfit is to design a data structure that&#039;s relevant to the business problem you are modelling (and ideally flexible too - we rarely get it right 1st time!), if you need attributes (or tags) and other descriptive/categorisation mechanisms then we try to design the data structures accordingly.
Ultimately I see the &quot;tree&quot; bit as only how the underlying data structure is surfaced in a U/I and so providing several different ways to surface the same underlying data model is key to meeting all the various needs of punters; picking on poor old trees seems a bit arbitrary, why not reports, these seem to be much more widely &quot;abused&quot; as vehicles for data in my experience?
Just interested..
Cheers, Steve
</description>
		<content:encoded><![CDATA[<p>It’s nice to hear about other small software companies and their ideas, most firms seem to be too paranoid to share any (real) information or vision during their development process — you just get the same old corporate happy-talk (thanks for that phrase Hugh, I use it a lot!).<br />
I agree with all but one of these, I don’t get the big thing about tree structures?<br />
What we try to do at my little software outfit is to design a data structure that’s relevant to the business problem you are modelling (and ideally flexible too — we rarely get it right 1st time!), if you need attributes (or tags) and other descriptive/categorisation mechanisms then we try to design the data structures accordingly.<br />
Ultimately I see the “tree” bit as only how the underlying data structure is surfaced in a U/I and so providing several different ways to surface the same underlying data model is key to meeting all the various needs of punters; picking on poor old trees seems a bit arbitrary, why not reports, these seem to be much more widely “abused” as vehicles for data in my experience?<br />
Just interested..<br />
Cheers, Steve</p>
]]></content:encoded>
	</item>
</channel>
</rss>

