<?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: How to Wreck Your Brand</title>
	<atom:link href="http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/</link>
	<description>Thought stream from SmugMug's CEO &#38; Chief Geek</description>
	<lastBuildDate>Tue, 24 Nov 2009 10:26:00 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9-rare</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John A. Davis</title>
		<link>http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/comment-page-1/#comment-46797</link>
		<dc:creator>John A. Davis</dc:creator>
		<pubDate>Tue, 10 Apr 2007 19:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/#comment-46797</guid>
		<description>God I remember being in love with all the Sony gadgets, from their headphones to their Professional Walkman&#039;s (there are some popular music albums that were recorded on a Sony Pro Walkman). There was nothing as sweet as Sony in the pre-computer days. I guess that dates me, sigh.</description>
		<content:encoded><![CDATA[<p>God I remember being in love with all the Sony gadgets, from their headphones to their Professional Walkman&#8217;s (there are some popular music albums that were recorded on a Sony Pro Walkman). There was nothing as sweet as Sony in the pre-computer days. I guess that dates me, sigh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Somewhere out there! &#187; Blog Archive &#187; PS3 losing the plot</title>
		<link>http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/comment-page-1/#comment-46545</link>
		<dc:creator>Somewhere out there! &#187; Blog Archive &#187; PS3 losing the plot</dc:creator>
		<pubDate>Sun, 08 Apr 2007 22:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/#comment-46545</guid>
		<description>[...] From How to Wreck Your Brand. [...]</description>
		<content:encoded><![CDATA[<p>[...] From How to Wreck Your Brand. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/comment-page-1/#comment-46384</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sat, 07 Apr 2007 15:02:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/#comment-46384</guid>
		<description>I think its easy to say you are listening to your customers because you are in a position to do something about it.  You do not ship hardware that you have to commit to for years.  The advantage of company built around a website is that you have full control over the end product at all times.   But whos to say that some new technology won&#039;t come in and make your website irrelevant?  It seems impossible now, but i&#039;m sure Sony thought the same thing about its Walkman (iPod) and PS2 (Wii).

Sony has to anticipate the customer&#039;s wants before they want it.  Even though the PS2 still sells by the truckload, each generation of videogames is very different and a company can easily fall from the top in only a few years (see SEGA).  I think PS3 will still do well, because the demand for HD gaming &amp; movies will only increase, but it will be a luxury item for a long time.  What they should have done is released a cheaper non-HD PS3, without BluRay much like Nintendo&#039;s strategy.  I think Nintendo knows that HD adoption is still about 4 years out, so they can release an inexpensive 480p console now, and worry about HD later.</description>
		<content:encoded><![CDATA[<p>I think its easy to say you are listening to your customers because you are in a position to do something about it.  You do not ship hardware that you have to commit to for years.  The advantage of company built around a website is that you have full control over the end product at all times.   But whos to say that some new technology won&#8217;t come in and make your website irrelevant?  It seems impossible now, but i&#8217;m sure Sony thought the same thing about its Walkman (iPod) and PS2 (Wii).</p>
<p>Sony has to anticipate the customer&#8217;s wants before they want it.  Even though the PS2 still sells by the truckload, each generation of videogames is very different and a company can easily fall from the top in only a few years (see SEGA).  I think PS3 will still do well, because the demand for HD gaming &amp; movies will only increase, but it will be a luxury item for a long time.  What they should have done is released a cheaper non-HD PS3, without BluRay much like Nintendo&#8217;s strategy.  I think Nintendo knows that HD adoption is still about 4 years out, so they can release an inexpensive 480p console now, and worry about HD later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Jaynes</title>
		<link>http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/comment-page-1/#comment-46364</link>
		<dc:creator>Matt Jaynes</dc:creator>
		<pubDate>Sat, 07 Apr 2007 12:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smugmug.com/don/2007/04/07/how-to-wreck-your-brand/#comment-46364</guid>
		<description>I worked with them on the development of their http://musicstore.connect.com/ site that was their attempted &#039;iTunes Store killer&#039; (just saying that makes me chuckle). Wow, what a mess. Talk about spaghetti code that had mushroomed into a giant ball of mud. It was *way* over budget and took much longer than anyone anticipated. And a year later, it still only supports Internet Explorer and Windows.

My take on what went wrong in this instance: they did not manage complexity. 
They let it grow and grow and did not believe that &#039;code debt&#039; was a reality. It soon took 10 times longer to make even the simplest changes because of the very poor state of the code. 

I have seen this happen at several companies and it&#039;s usually the same story. There are B and C level coders that don&#039;t understand the dangers or code complexity or code debt and thus create loads of both. The A level coders that do understand this try to explain the growing problem to management. The management doesn&#039;t know any better, so they see code cleanup as a needless expense that will only slow down rolling out new features and so they side with the B and C level coders. Of course, the irony is that development will eventually crawl to a near halt because the code is undecipherable. Along the way the A level coders get so frustrated with the state of the code base that they leave the company for greener pastures. This is the critical turning point since the B and C level coders will only hire other B and C level coders - and the project will die a slow death as the cycle continues.</description>
		<content:encoded><![CDATA[<p>I worked with them on the development of their <a href="http://musicstore.connect.com/" rel="nofollow">http://musicstore.connect.com/</a> site that was their attempted &#8216;iTunes Store killer&#8217; (just saying that makes me chuckle). Wow, what a mess. Talk about spaghetti code that had mushroomed into a giant ball of mud. It was *way* over budget and took much longer than anyone anticipated. And a year later, it still only supports Internet Explorer and Windows.</p>
<p>My take on what went wrong in this instance: they did not manage complexity.<br />
They let it grow and grow and did not believe that &#8216;code debt&#8217; was a reality. It soon took 10 times longer to make even the simplest changes because of the very poor state of the code. </p>
<p>I have seen this happen at several companies and it&#8217;s usually the same story. There are B and C level coders that don&#8217;t understand the dangers or code complexity or code debt and thus create loads of both. The A level coders that do understand this try to explain the growing problem to management. The management doesn&#8217;t know any better, so they see code cleanup as a needless expense that will only slow down rolling out new features and so they side with the B and C level coders. Of course, the irony is that development will eventually crawl to a near halt because the code is undecipherable. Along the way the A level coders get so frustrated with the state of the code base that they leave the company for greener pastures. This is the critical turning point since the B and C level coders will only hire other B and C level coders &#8211; and the project will die a slow death as the cycle continues.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
