<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Two Approaches for Starting a Software Product Company</title>
	<link>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/</link>
	<description>Relentless Persistence</description>
	<pubDate>Fri, 05 Sep 2008 20:13:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Bubba</title>
		<link>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-117</link>
		<dc:creator>Bubba</dc:creator>
		<pubDate>Thu, 29 Nov 2007 21:53:47 +0000</pubDate>
		<guid>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-117</guid>
		<description>i agree learning is an ROI and have had my share of "failed" projects that have been way more valuable to me than my "succesful" projects.  So I guess I agree on the value (and serendipity factor - just finished black swan, you may like it as it talks about postive randomness).  

One caveat though is that "failing" costs time &#038; the opportunity to do other things - both of which are very expensive for the entrepreneur but not for investors since the later typically has multiple parrellal bets in place with the expectation that some (lots) will fail.  On the other hand one "success" may pay the bills for 10 years for an entrepreneur while working on the next attempt(s)...

Net, net it is just knowing the tradeoffs and personal situation / skills / needs.</description>
		<content:encoded><![CDATA[<p>i agree learning is an ROI and have had my share of &#8220;failed&#8221; projects that have been way more valuable to me than my &#8220;succesful&#8221; projects.  So I guess I agree on the value (and serendipity factor - just finished black swan, you may like it as it talks about postive randomness).  </p>
<p>One caveat though is that &#8220;failing&#8221; costs time &#038; the opportunity to do other things - both of which are very expensive for the entrepreneur but not for investors since the later typically has multiple parrellal bets in place with the expectation that some (lots) will fail.  On the other hand one &#8220;success&#8221; may pay the bills for 10 years for an entrepreneur while working on the next attempt(s)&#8230;</p>
<p>Net, net it is just knowing the tradeoffs and personal situation / skills / needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-112</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Thu, 29 Nov 2007 00:22:41 +0000</pubDate>
		<guid>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-112</guid>
		<description>My friends all roll their eyes when I tell them I have this great idea for a project that could be really cool. They've heard similar ideas from me, gotten excited for me, even signed up and once and a while made good contributions. Eventually they start to ask, "but what about X? are you still working on that?" That's because I usually aim for #2, the "Identify a small unexplored feature, work on it in my spare time, and see if it sticks" route. 

What they don't understand, and what your article doesn't touch on, is what I learned from each experience. I'm one of those bootstrapper web guys. I played with construction toys and video games as a kid and consequently had a knack for computers that got my foot in the door, and work experience did the rest for me. Seven years of freelancing, and about a hundred stillborn personal projects later, I feel like I'm in better shape to startup than ever. Every project teaches you something, and produces code you can hopefully reuse (after you learn you need to make reusable code that is).

So while #2 may have no significant financial ROI for the entrepreneur, there is always the potential for intellectual ROI. Sometimes, that's invaluable. Practice makes perfect.</description>
		<content:encoded><![CDATA[<p>My friends all roll their eyes when I tell them I have this great idea for a project that could be really cool. They&#8217;ve heard similar ideas from me, gotten excited for me, even signed up and once and a while made good contributions. Eventually they start to ask, &#8220;but what about X? are you still working on that?&#8221; That&#8217;s because I usually aim for #2, the &#8220;Identify a small unexplored feature, work on it in my spare time, and see if it sticks&#8221; route. </p>
<p>What they don&#8217;t understand, and what your article doesn&#8217;t touch on, is what I learned from each experience. I&#8217;m one of those bootstrapper web guys. I played with construction toys and video games as a kid and consequently had a knack for computers that got my foot in the door, and work experience did the rest for me. Seven years of freelancing, and about a hundred stillborn personal projects later, I feel like I&#8217;m in better shape to startup than ever. Every project teaches you something, and produces code you can hopefully reuse (after you learn you need to make reusable code that is).</p>
<p>So while #2 may have no significant financial ROI for the entrepreneur, there is always the potential for intellectual ROI. Sometimes, that&#8217;s invaluable. Practice makes perfect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heri Rakotomalala</title>
		<link>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-45</link>
		<dc:creator>Heri Rakotomalala</dc:creator>
		<pubDate>Sun, 28 Oct 2007 20:35:04 +0000</pubDate>
		<guid>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-45</guid>
		<description>Hi,
most people would agree it doesn't take much these days to build a "startup". there are practically no barriers to entry, and I bet in the next few years, there will be more startups, more experimentations, done with a small to non-existant budget. 

btw, we are launching blitzweekend in early spring in montreal, canada. we would invite entrepreneurs, developers, designers etc. to build a startup in one weekend. but unlike startuweekend, people do it in teams of 3 to 5. it's built for pressure, an environment for rapid successes and failures. i guess we are the 2nd approach to its maximum</description>
		<content:encoded><![CDATA[<p>Hi,<br />
most people would agree it doesn&#8217;t take much these days to build a &#8220;startup&#8221;. there are practically no barriers to entry, and I bet in the next few years, there will be more startups, more experimentations, done with a small to non-existant budget. </p>
<p>btw, we are launching blitzweekend in early spring in montreal, canada. we would invite entrepreneurs, developers, designers etc. to build a startup in one weekend. but unlike startuweekend, people do it in teams of 3 to 5. it&#8217;s built for pressure, an environment for rapid successes and failures. i guess we are the 2nd approach to its maximum</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bubba</title>
		<link>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-43</link>
		<dc:creator>Bubba</dc:creator>
		<pubDate>Sun, 28 Oct 2007 04:03:13 +0000</pubDate>
		<guid>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-43</guid>
		<description>Thanks for hte 411 Dave.   I think that maps to the taxonomy / reference point I wrote about.  

Did you do anything specific (or accidentally!) with MessageCast from a technology, product, funding or structure perspective to facilitate your exit goal?</description>
		<content:encoded><![CDATA[<p>Thanks for hte 411 Dave.   I think that maps to the taxonomy / reference point I wrote about.  </p>
<p>Did you do anything specific (or accidentally!) with MessageCast from a technology, product, funding or structure perspective to facilitate your exit goal?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Hodson</title>
		<link>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-42</link>
		<dc:creator>Dave Hodson</dc:creator>
		<pubDate>Sun, 28 Oct 2007 02:13:38 +0000</pubDate>
		<guid>http://murarka.com/2007/10/27/two-approaches-for-starting-a-software-product-company/#comment-42</guid>
		<description>Bubba

When I started MessageCast, I was aiming for an exit with one of the Big 3 (AOL, MS, Y!). My previous company (iPrint) was partnered with MS, but I didn't perceive that would be of much significance (and in the end, I don't think it helped much on the actual acquisition). At the time, AIM was easily #1 in the IM space and so my first protoype actually worked with AIM using Jabber, not MS.

Dave</description>
		<content:encoded><![CDATA[<p>Bubba</p>
<p>When I started MessageCast, I was aiming for an exit with one of the Big 3 (AOL, MS, Y!). My previous company (iPrint) was partnered with MS, but I didn&#8217;t perceive that would be of much significance (and in the end, I don&#8217;t think it helped much on the actual acquisition). At the time, AIM was easily #1 in the IM space and so my first protoype actually worked with AIM using Jabber, not MS.</p>
<p>Dave</p>
]]></content:encoded>
	</item>
</channel>
</rss>
