<?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: Making vs. Taking</title>
	<atom:link href="http://www.mberkay.com/2008/12/12/making-vs-taking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mberkay.com/2008/12/12/making-vs-taking/</link>
	<description></description>
	<lastBuildDate>Wed, 14 Jul 2010 09:30:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chronicles of a Wandering Mind &#187; Bookmarks for December 11th through December 14th</title>
		<link>http://www.mberkay.com/2008/12/12/making-vs-taking/comment-page-1/#comment-56</link>
		<dc:creator>Chronicles of a Wandering Mind &#187; Bookmarks for December 11th through December 14th</dc:creator>
		<pubDate>Sun, 14 Dec 2008 11:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mberkay.com/?p=62#comment-56</guid>
		<description>[...] Chronicles of a Wandering Mind &#187; Making vs. Taking - So we face with the choice Seth states eloquently in his post. Should we try to take market share by identifying RapidInsight with existing solution or should we try to make the market? The answer should not be that difficult. We&#8217;re way too small to make a market. We can easily say &#8220;RapidInsight is like Netcool, only better :). An open source IT event management solution&#8221; It&#8217;s probably better marketing position for us. From a technical perspective, this is an inadequate description of our product. I want to talk about why focusing only on consolidating events, restricted proprietary languages, storing data in relational databases are flawed approaches and why one needs a built-in CMDB, object based data store, use of standard based dynamic scripting language , etc. Yet I have to accept that &#8220;making the market&#8221; is out of our reach, however &#8220;right&#8221; it feels. [...]</description>
		<content:encoded><![CDATA[<p>[...] Chronicles of a Wandering Mind &raquo; Making vs. Taking &#8211; So we face with the choice Seth states eloquently in his post. Should we try to take market share by identifying RapidInsight with existing solution or should we try to make the market? The answer should not be that difficult. We&rsquo;re way too small to make a market. We can easily say &ldquo;RapidInsight is like Netcool, only better <img src='http://www.mberkay.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . An open source IT event management solution&rdquo; It&rsquo;s probably better marketing position for us. From a technical perspective, this is an inadequate description of our product. I want to talk about why focusing only on consolidating events, restricted proprietary languages, storing data in relational databases are flawed approaches and why one needs a built-in CMDB, object based data store, use of standard based dynamic scripting language , etc. Yet I have to accept that &ldquo;making the market&rdquo; is out of our reach, however &ldquo;right&rdquo; it feels. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chronicles of a Wandering Mind &#187; Bookmarks for December 11th through December 14th</title>
		<link>http://www.mberkay.com/2008/12/12/making-vs-taking/comment-page-1/#comment-57</link>
		<dc:creator>Chronicles of a Wandering Mind &#187; Bookmarks for December 11th through December 14th</dc:creator>
		<pubDate>Sun, 14 Dec 2008 11:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mberkay.com/?p=62#comment-57</guid>
		<description>[...] Chronicles of a Wandering Mind &#187; Making vs. Taking - So we face with the choice Seth states eloquently in his post. Should we try to take market share by identifying RapidInsight with existing solution or should we try to make the market? The answer should not be that difficult. We&#8217;re way too small to make a market. We can easily say &#8220;RapidInsight is like Netcool, only better :). An open source IT event management solution&#8221; It&#8217;s probably better marketing position for us. From a technical perspective, this is an inadequate description of our product. I want to talk about why focusing only on consolidating events, restricted proprietary languages, storing data in relational databases are flawed approaches and why one needs a built-in CMDB, object based data store, use of standard based dynamic scripting language , etc. Yet I have to accept that &#8220;making the market&#8221; is out of our reach, however &#8220;right&#8221; it feels. [...]</description>
		<content:encoded><![CDATA[<p>[...] Chronicles of a Wandering Mind &raquo; Making vs. Taking &#8211; So we face with the choice Seth states eloquently in his post. Should we try to take market share by identifying RapidInsight with existing solution or should we try to make the market? The answer should not be that difficult. We&rsquo;re way too small to make a market. We can easily say &ldquo;RapidInsight is like Netcool, only better <img src='http://www.mberkay.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . An open source IT event management solution&rdquo; It&rsquo;s probably better marketing position for us. From a technical perspective, this is an inadequate description of our product. I want to talk about why focusing only on consolidating events, restricted proprietary languages, storing data in relational databases are flawed approaches and why one needs a built-in CMDB, object based data store, use of standard based dynamic scripting language , etc. Yet I have to accept that &ldquo;making the market&rdquo; is out of our reach, however &ldquo;right&rdquo; it feels. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
