<?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 security of working at a startup</title>
	<atom:link href="http://yanpritzker.com/2008/04/21/the-security-of-working-at-a-startup/feed/" rel="self" type="application/rss+xml" />
	<link>http://yanpritzker.com/2008/04/21/the-security-of-working-at-a-startup/</link>
	<description>photographer, entrepreneur, software engineer, musician, skier</description>
	<lastBuildDate>Wed, 01 Feb 2012 00:01:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: yan</title>
		<link>http://yanpritzker.com/2008/04/21/the-security-of-working-at-a-startup/comment-page-1/#comment-11385</link>
		<dc:creator>yan</dc:creator>
		<pubDate>Mon, 21 Apr 2008 19:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/04/21/the-security-of-working-at-a-startup/#comment-11385</guid>
		<description>You are right, there is less margin for error in startups, but my point is that in a small team you know your team mates, and you know yourself, and you know the sum of your efforts is what is making success or failure for the company. I think it&#039;s easy to see when something is going wrong in a small company as opposed to a big one where usually the negative change comes from the top and several levels above you, where you are certainly powerless to have any effect.

Small company within a large one is also very nice - I worked one summer at IBM Extreme Blue which was just like a little startup within the gigantic IBM, and it was also a great experience.</description>
		<content:encoded><![CDATA[<p>You are right, there is less margin for error in startups, but my point is that in a small team you know your team mates, and you know yourself, and you know the sum of your efforts is what is making success or failure for the company. I think it&#8217;s easy to see when something is going wrong in a small company as opposed to a big one where usually the negative change comes from the top and several levels above you, where you are certainly powerless to have any effect.</p>
<p>Small company within a large one is also very nice &#8211; I worked one summer at IBM Extreme Blue which was just like a little startup within the gigantic IBM, and it was also a great experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: edgar</title>
		<link>http://yanpritzker.com/2008/04/21/the-security-of-working-at-a-startup/comment-page-1/#comment-11384</link>
		<dc:creator>edgar</dc:creator>
		<pubDate>Mon, 21 Apr 2008 18:25:20 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/04/21/the-security-of-working-at-a-startup/#comment-11384</guid>
		<description>I worked for a startup for four years. I now work for a big company and I&#039;m going on three years.

One problem with startups is that there isn&#039;t room for mistakes and if that mistake is from the owner/CEO, then there isn&#039;t much one can do to undo it.

They had potential to be successful by now, if they had followed my advice.

My current employment act as a small company within a large one so I basically benefit from both types. It was a good move.</description>
		<content:encoded><![CDATA[<p>I worked for a startup for four years. I now work for a big company and I&#8217;m going on three years.</p>
<p>One problem with startups is that there isn&#8217;t room for mistakes and if that mistake is from the owner/CEO, then there isn&#8217;t much one can do to undo it.</p>
<p>They had potential to be successful by now, if they had followed my advice.</p>
<p>My current employment act as a small company within a large one so I basically benefit from both types. It was a good move.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

