<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Is this why some artists (and others) are starving?</title>
	<atom:link href="http://www.rescuemarketing.com/blog/2009/03/23/starving-artists/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rescuemarketing.com/blog/2009/03/23/starving-artists/</link>
	<description>Strategic, common sense marketing, operations and tech advice that will strengthen your business - today!</description>
	<lastBuildDate>Wed, 18 Jan 2012 23:16:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark</title>
		<link>http://www.rescuemarketing.com/blog/2009/03/23/starving-artists/comment-page-1/#comment-3744</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 24 Mar 2009 03:34:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.rescuemarketing.com/blog/?p=1976#comment-3744</guid>
		<description>Probably 6-8 years ago, I had a GB guy who had a pile of problems with his network. Repeatedly tried to get him to isolate the problem to 1 component on the machine. He was halfway across the US from me. We did various things, but I never could get him to try what I asked. He had several firms come in and look at the machine. Finally the last guy took the troubled machine off the network and all their network problems instantly disappeared. He replaced the NIC and put it back on the network, all good. Dude called me up and apologized - 2 years after our initial conversation. That was cool.</description>
		<content:encoded><![CDATA[<p>Probably 6-8 years ago, I had a GB guy who had a pile of problems with his network. Repeatedly tried to get him to isolate the problem to 1 component on the machine. He was halfway across the US from me. We did various things, but I never could get him to try what I asked. He had several firms come in and look at the machine. Finally the last guy took the troubled machine off the network and all their network problems instantly disappeared. He replaced the NIC and put it back on the network, all good. Dude called me up and apologized &#8211; 2 years after our initial conversation. That was cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ Eggen</title>
		<link>http://www.rescuemarketing.com/blog/2009/03/23/starving-artists/comment-page-1/#comment-3743</link>
		<dc:creator>Russ Eggen</dc:creator>
		<pubDate>Mon, 23 Mar 2009 20:39:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.rescuemarketing.com/blog/?p=1976#comment-3743</guid>
		<description>Mark,

A few years ago I had a client who had a tendancy to be a bit toxic.  He would go on and on how my programs I built for him crashed (it would never happen while I was there - despite our best efforts).  He also had some very old computers and my advice was to replace them with modern systems (he had the funds).  He finally did so.

My next visit on site and he started going off the handle: &quot;I replaced the machines and the program still crashes, not a good return on investment...&quot;

I simply turn to him and with a straight face informed him &quot;Yeah, but look how much &lt;i&gt;faster &lt;/i&gt;it crashes now!&quot;  He stopped dead in his tracks, deer in headlights look and then busted out laughing.

We found the problem in the next 20 minutes.  Lesson learned?  No sense in getting upset about a mistake.  Take a few moments to realize that getting angry is not solving a problem and it would be a good idea to mull over what just happened.  I&#039;ve found that can devise a solid solution that way.</description>
		<content:encoded><![CDATA[<p>Mark,</p>
<p>A few years ago I had a client who had a tendancy to be a bit toxic.  He would go on and on how my programs I built for him crashed (it would never happen while I was there &#8211; despite our best efforts).  He also had some very old computers and my advice was to replace them with modern systems (he had the funds).  He finally did so.</p>
<p>My next visit on site and he started going off the handle: &#8220;I replaced the machines and the program still crashes, not a good return on investment&#8230;&#8221;</p>
<p>I simply turn to him and with a straight face informed him &#8220;Yeah, but look how much <i>faster </i>it crashes now!&#8221;  He stopped dead in his tracks, deer in headlights look and then busted out laughing.</p>
<p>We found the problem in the next 20 minutes.  Lesson learned?  No sense in getting upset about a mistake.  Take a few moments to realize that getting angry is not solving a problem and it would be a good idea to mull over what just happened.  I&#8217;ve found that can devise a solid solution that way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

