<?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: Best Practices, Part 2</title>
	<atom:link href="http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/</link>
	<description>The mental ramblings of Sanya Weathers</description>
	<lastBuildDate>Mon, 06 Feb 2012 23:58:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Brian</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1932</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Fri, 18 Jul 2008 18:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1932</guid>
		<description>Here&#039;s a network related concept that I&#039;ve had to suffer through.

If you can reduce your expenses by 50% by changing to a newer network, but it doesn&#039;t actually perform all the tasks your employees need, you didn&#039;t actually save money.

More simply:  &quot;Newer isn&#039;t always better&quot;.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a network related concept that I&#8217;ve had to suffer through.</p>
<p>If you can reduce your expenses by 50% by changing to a newer network, but it doesn&#8217;t actually perform all the tasks your employees need, you didn&#8217;t actually save money.</p>
<p>More simply:  &#8220;Newer isn&#8217;t always better&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kennedy</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1931</link>
		<dc:creator>Kennedy</dc:creator>
		<pubDate>Sat, 12 Jul 2008 04:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1931</guid>
		<description>My best practice is to remind my P&amp;L owners and my sales guys that our people and our product are valuable, so in negotiations, value our concessions.  Don&#039;t give anything away for free; there must be quid pro quo, even if it is small.</description>
		<content:encoded><![CDATA[<p>My best practice is to remind my P&amp;L owners and my sales guys that our people and our product are valuable, so in negotiations, value our concessions.  Don&#8217;t give anything away for free; there must be quid pro quo, even if it is small.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1930</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 08 Jul 2008 22:19:28 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1930</guid>
		<description>Every single day shaved off initial design/coding is one more day added to QA. Reduce scope before reducing time in your schedule.</description>
		<content:encoded><![CDATA[<p>Every single day shaved off initial design/coding is one more day added to QA. Reduce scope before reducing time in your schedule.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matennon</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1929</link>
		<dc:creator>Matennon</dc:creator>
		<pubDate>Sun, 06 Jul 2008 22:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1929</guid>
		<description>- Praise in pubic, criticize in private.  Nothing will turn a subordinate against you faster than chastising him/her in front of others, most especially if they are HIS subordinates!  This is also true if you feel the need to take issue with someone higher up in your chain of command.</description>
		<content:encoded><![CDATA[<p>- Praise in pubic, criticize in private.  Nothing will turn a subordinate against you faster than chastising him/her in front of others, most especially if they are HIS subordinates!  This is also true if you feel the need to take issue with someone higher up in your chain of command.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fsanch</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1928</link>
		<dc:creator>fsanch</dc:creator>
		<pubDate>Sun, 06 Jul 2008 12:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1928</guid>
		<description>I have three:

-The worst thing you can say to your team after receiving management direction is &quot;I know it sucks, but...&quot;.
Congratulations, you&#039;ve just screwed up your company unity, because your team will now have an attitude of rebellion you&#039;ve indirectly endorsed. What you should say is, &quot;If you disagree with this, pass me your concerns and I will take them up the chain&quot;.

-Manage expectations about a project up front.
Projects can get fucked because people didn&#039;t know how to handle an issue or what they were supposed to be doing. Go through an exercise to establish your purpose, vision, and brainstorm some ideas to get there. Organize them, and your team, and come up with some action items. This essentially manages expectations and puts everyone on the same page.

-Flex your approach.
Got a worker who values organization? Be overly organized for your meeting with them. Got someone who is easily emotionally affected by their work? Give them praise when they do well. Got a boss who is all about the bottom line? Limit your meetings to no more than 15 minutes. Flex your approach to the people you are dealing with, and you will have a much easier time than trying to ram the way you do things down people&#039;s throats.</description>
		<content:encoded><![CDATA[<p>I have three:</p>
<p>-The worst thing you can say to your team after receiving management direction is &#8220;I know it sucks, but&#8230;&#8221;.<br />
Congratulations, you&#8217;ve just screwed up your company unity, because your team will now have an attitude of rebellion you&#8217;ve indirectly endorsed. What you should say is, &#8220;If you disagree with this, pass me your concerns and I will take them up the chain&#8221;.</p>
<p>-Manage expectations about a project up front.<br />
Projects can get fucked because people didn&#8217;t know how to handle an issue or what they were supposed to be doing. Go through an exercise to establish your purpose, vision, and brainstorm some ideas to get there. Organize them, and your team, and come up with some action items. This essentially manages expectations and puts everyone on the same page.</p>
<p>-Flex your approach.<br />
Got a worker who values organization? Be overly organized for your meeting with them. Got someone who is easily emotionally affected by their work? Give them praise when they do well. Got a boss who is all about the bottom line? Limit your meetings to no more than 15 minutes. Flex your approach to the people you are dealing with, and you will have a much easier time than trying to ram the way you do things down people&#8217;s throats.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Echo</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1927</link>
		<dc:creator>Echo</dc:creator>
		<pubDate>Sun, 06 Jul 2008 06:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1927</guid>
		<description>Everyone is smart, everyone is stupid.

Never assume that anyone is the same kind of smart that you are, and NEVER assume that they are the same kind of stupid.

No matter how efficient, how brilliant or how driven to produce your guy is...NEVER make him the only person in the development loop.

She might be producing 60% of your code, but one set of assumptions not common to the user base and BOOM!</description>
		<content:encoded><![CDATA[<p>Everyone is smart, everyone is stupid.</p>
<p>Never assume that anyone is the same kind of smart that you are, and NEVER assume that they are the same kind of stupid.</p>
<p>No matter how efficient, how brilliant or how driven to produce your guy is&#8230;NEVER make him the only person in the development loop.</p>
<p>She might be producing 60% of your code, but one set of assumptions not common to the user base and BOOM!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: goemagog</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1926</link>
		<dc:creator>goemagog</dc:creator>
		<pubDate>Fri, 04 Jul 2008 15:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1926</guid>
		<description>&quot;realistic expectations&quot;.

and &lt;a href=&quot;http://brokentoys.org/2008/06/12/its-the-fun-stupid/&quot; rel=&quot;nofollow&quot;&gt;fire&lt;/a&gt;.

and &lt;a href=&quot;http://www.awfulplasticsurgery.us/2007/01/man_boobs_4_wor.html&quot; rel=&quot;nofollow&quot;&gt;boobies&lt;/a&gt;.

and our lovely hostess, &lt;a href=&quot;http://www.dreamlandnews.com/divine/img/divinedogs.jpg&quot; rel=&quot;nofollow&quot;&gt;Sanya&lt;/a&gt;.

Goe, going to see fireworks tonight.</description>
		<content:encoded><![CDATA[<p>&#8220;realistic expectations&#8221;.</p>
<p>and <a href="http://brokentoys.org/2008/06/12/its-the-fun-stupid/" rel="nofollow">fire</a>.</p>
<p>and <a href="http://www.awfulplasticsurgery.us/2007/01/man_boobs_4_wor.html" rel="nofollow">boobies</a>.</p>
<p>and our lovely hostess, <a href="http://www.dreamlandnews.com/divine/img/divinedogs.jpg" rel="nofollow">Sanya</a>.</p>
<p>Goe, going to see fireworks tonight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Merlyn</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1925</link>
		<dc:creator>Merlyn</dc:creator>
		<pubDate>Thu, 03 Jul 2008 00:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1925</guid>
		<description>Geez...programming best practices, gaming best practices...

How about the most basic one?

Take care of the customer.  They&#039;re the ones paying your checks (in the end) and they&#039;re the ones you have to make happy.

If they have a problem, resolve it as quickly, and as accurately as you can.

Be polite, be concise, and don&#039;t patronize your customers.  Treat them how you want to be treated, and don&#039;t ever, ever lie to them.  They will find out.

If you make a mistake, admit it, correct it, and explain as best you can.  Cover ups will be detected, and will blow up in your face.

Finally, don&#039;t be scared of telling a customer &quot;no.&quot;  Sometimes, you just can&#039;t accommodate them, and if you don&#039;t pussy-foot around, and just tell them up front, they&#039;ll understand and respect you.

(Yes, I work in support...and I&#039;ve yet to have a customer get mad at me...mad at the product I&#039;m supporting or the company I work for, but not at me.)</description>
		<content:encoded><![CDATA[<p>Geez&#8230;programming best practices, gaming best practices&#8230;</p>
<p>How about the most basic one?</p>
<p>Take care of the customer.  They&#8217;re the ones paying your checks (in the end) and they&#8217;re the ones you have to make happy.</p>
<p>If they have a problem, resolve it as quickly, and as accurately as you can.</p>
<p>Be polite, be concise, and don&#8217;t patronize your customers.  Treat them how you want to be treated, and don&#8217;t ever, ever lie to them.  They will find out.</p>
<p>If you make a mistake, admit it, correct it, and explain as best you can.  Cover ups will be detected, and will blow up in your face.</p>
<p>Finally, don&#8217;t be scared of telling a customer &#8220;no.&#8221;  Sometimes, you just can&#8217;t accommodate them, and if you don&#8217;t pussy-foot around, and just tell them up front, they&#8217;ll understand and respect you.</p>
<p>(Yes, I work in support&#8230;and I&#8217;ve yet to have a customer get mad at me&#8230;mad at the product I&#8217;m supporting or the company I work for, but not at me.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: goemagog</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1924</link>
		<dc:creator>goemagog</dc:creator>
		<pubDate>Wed, 02 Jul 2008 23:14:06 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1924</guid>
		<description>best practices?

don&#039;t take milton&#039;s stapler or he might set the building on fire.

Goe, reminding you that it&#039;s the red one.</description>
		<content:encoded><![CDATA[<p>best practices?</p>
<p>don&#8217;t take milton&#8217;s stapler or he might set the building on fire.</p>
<p>Goe, reminding you that it&#8217;s the red one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pharniel</title>
		<link>http://eatingbees.brokentoys.org/2008/06/30/best-practices-part-2/#comment-1923</link>
		<dc:creator>pharniel</dc:creator>
		<pubDate>Wed, 02 Jul 2008 19:06:21 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=82#comment-1923</guid>
		<description>@ 22 - but that would mean that the people writing the checks are the problem, not the minions who are secretly sabatogeing the investers in the back, no really, arn&#039;t?

we can&#039;t have that. (i see you&#039;ve been on the same cruise i have)</description>
		<content:encoded><![CDATA[<p>@ 22 &#8211; but that would mean that the people writing the checks are the problem, not the minions who are secretly sabatogeing the investers in the back, no really, arn&#8217;t?</p>
<p>we can&#8217;t have that. (i see you&#8217;ve been on the same cruise i have)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

