<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
	<channel>
		<title>gdp's Comments</title>
		<language>en-us</language>
		<link>https://www.intensedebate.com/users/2150</link>
		<description>Comments by Waleed</description>
<item>
<title>Startup Weekend San Francisco &#8212; November 16-18 : Idea Form</title>
<link>http://sf.startupweekend.com/idea-form/#IDComment38837</link>
<description>Yes, that&amp;#039;s a better way to describe it. </description>
<pubDate>Fri, 16 Nov 2007 02:42:03 +0000</pubDate>
<guid>http://sf.startupweekend.com/idea-form/#IDComment38837</guid>
</item><item>
<title>Startup Weekend San Francisco &#8212; November 16-18 : Idea Form</title>
<link>http://sf.startupweekend.com/idea-form/#IDComment38836</link>
<description>Agree. And it adds a dose of healthy competition to the mix. In fact if we do 4, we&amp;#039;ll still have an average of 50 people per startup. In legal terms, it&amp;#039;ll still be one startup company that we all own, but it&amp;#039;ll release 2 or 4 products.  &lt;br /&gt; </description>
<pubDate>Fri, 16 Nov 2007 02:38:44 +0000</pubDate>
<guid>http://sf.startupweekend.com/idea-form/#IDComment38836</guid>
</item><item>
<title>Startup Weekend San Francisco &#8212; November 16-18 : Idea Form</title>
<link>http://sf.startupweekend.com/idea-form/#IDComment38393</link>
<description>With about 200 people signed up, we have good news and bad news: &lt;br /&gt; &lt;br /&gt;1. The Bad News: Our big team.  &lt;br /&gt;     Because the productivity of a team tends to decline as the team size grows. We should avoid ideas that has one single core in which most of the coding is done because, then, we&amp;#039;ll have developers getting into each other&amp;#039;s way. We&amp;#039;ll need to choose an idea that allows us to split into teams. Our product should have a Web site and an associated Facebook and OpenSocial apps, and maybe a mobile version or a Wordpress plugin. &lt;br /&gt; &lt;br /&gt;2. The Good News: Again, Our big team. &lt;br /&gt;     We have a lot of early adapters: us; and PR and marketing people. These are things that most startups wish they had. We should play this advantage. Our team puts us in a great position to create a social application that we, ourselves, could use. This is important, because if we create something that we&amp;#039;re not going to use ourselves, then we&amp;#039;ll likely fail. On the other hand, if the 200 of us join our social application and invite our friends, we&amp;#039;ll have thousands of users overnight. We could build momentum that&amp;#039;s likely to sustain itself. &lt;br /&gt; &lt;br /&gt;Here is an idea to consider. Not particularly creative, but I&amp;#039;m listing it as an example: &lt;br /&gt; &lt;br /&gt;Discussions on the Fly: An application in which you can quickly create a micro-forum to discuss something, and discard it once a conclusion is reached. You can start a discussion from your Facebook or OpenSocial app, or directly on the Web site. You get a unique conversation ID that you send to anyone who likes to join the discussion. Once they sign up, they can participate in any open discussions that are active at the time. &lt;br /&gt; </description>
<pubDate>Thu, 15 Nov 2007 16:50:43 +0000</pubDate>
<guid>http://sf.startupweekend.com/idea-form/#IDComment38393</guid>
</item>	</channel>
</rss>