<?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 for Eating Bees</title>
	<atom:link href="http://eatingbees.brokentoys.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://eatingbees.brokentoys.org</link>
	<description>The mental ramblings of Sanya Weathers</description>
	<pubDate>Wed, 17 Mar 2010 01:49:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Expectations, Part 29548 by ReptileHouse</title>
		<link>http://eatingbees.brokentoys.org/2010/03/11/expectations-part-29548/comment-page-1/#comment-3826</link>
		<dc:creator>ReptileHouse</dc:creator>
		<pubDate>Mon, 15 Mar 2010 16:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.brokentoys.org/?p=271#comment-3826</guid>
		<description>How much of the early hype and spin is really targeted at consumers, and how much is building interest to attract investors?</description>
		<content:encoded><![CDATA[<p>How much of the early hype and spin is really targeted at consumers, and how much is building interest to attract investors?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expectations, Part 29548 by Arrakiv</title>
		<link>http://eatingbees.brokentoys.org/2010/03/11/expectations-part-29548/comment-page-1/#comment-3822</link>
		<dc:creator>Arrakiv</dc:creator>
		<pubDate>Sun, 14 Mar 2010 17:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.brokentoys.org/?p=271#comment-3822</guid>
		<description>You know, that first paragraph is a rather simple, short, and straightforward with some information that probably should be pretty much common knowledge and common sense. Yet, I can't help but feel that it needs to somehow be required reading.

Heck, I'm happy I read it for the reminder....</description>
		<content:encoded><![CDATA[<p>You know, that first paragraph is a rather simple, short, and straightforward with some information that probably should be pretty much common knowledge and common sense. Yet, I can&#8217;t help but feel that it needs to somehow be required reading.</p>
<p>Heck, I&#8217;m happy I read it for the reminder&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expectations, Part 29548 by gentimouton</title>
		<link>http://eatingbees.brokentoys.org/2010/03/11/expectations-part-29548/comment-page-1/#comment-3820</link>
		<dc:creator>gentimouton</dc:creator>
		<pubDate>Sat, 13 Mar 2010 21:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.brokentoys.org/?p=271#comment-3820</guid>
		<description>&lt;q&gt;If you ask early adopters, as I recently did,&lt;/q&gt; (quote from examiner.com) Did you go and talk to them as a community manager or as a random player? I'm not sure, but I think there can be a difference.

It's obvious that AAA MMOG need to create a buzz and give glimpses about their crazy/new/unsuspected stuff. After all, marketing is one third of the success of a game, right? But players do not make the difference between an MMOG from a private company (like Turbine, cf comments on examiner.com) or from a publisher/with-shareholders. So should this undifferentiation be maintained by to the PR/CM? Caricature (of really bad CM): "Sorry, this feature you expected so much is quite botched because our shareholders thought it would cost too many resources for too little ROI". 

&lt;q&gt;I am not sure the explosion of community-style jobs has been a good thing for the industry, because these basics don’t seem to have been learned.&lt;/q&gt; To my mind, there should be a marked difference between PR and CM roles. You surely have a broader view of the industry than me. How is it in practice?

And finally, OK, your post is a rant. But how do you solve the problem? Should a CM be as inconsistent and unpredictable as possible? I guess not.</description>
		<content:encoded><![CDATA[<p><q>If you ask early adopters, as I recently did,</q> (quote from examiner.com) Did you go and talk to them as a community manager or as a random player? I&#8217;m not sure, but I think there can be a difference.</p>
<p>It&#8217;s obvious that AAA MMOG need to create a buzz and give glimpses about their crazy/new/unsuspected stuff. After all, marketing is one third of the success of a game, right? But players do not make the difference between an MMOG from a private company (like Turbine, cf comments on examiner.com) or from a publisher/with-shareholders. So should this undifferentiation be maintained by to the PR/CM? Caricature (of really bad CM): &#8220;Sorry, this feature you expected so much is quite botched because our shareholders thought it would cost too many resources for too little ROI&#8221;. </p>
<p><q>I am not sure the explosion of community-style jobs has been a good thing for the industry, because these basics don’t seem to have been learned.</q> To my mind, there should be a marked difference between PR and CM roles. You surely have a broader view of the industry than me. How is it in practice?</p>
<p>And finally, OK, your post is a rant. But how do you solve the problem? Should a CM be as inconsistent and unpredictable as possible? I guess not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expectations, Part 29548 by Kinada</title>
		<link>http://eatingbees.brokentoys.org/2010/03/11/expectations-part-29548/comment-page-1/#comment-3819</link>
		<dc:creator>Kinada</dc:creator>
		<pubDate>Sat, 13 Mar 2010 11:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.brokentoys.org/?p=271#comment-3819</guid>
		<description>Expectations are the root of all evil :P

Really.

Everyone is guilty of it at some point. Hell the more MMOs that I play the more I tend to expect. 

I think the fact that Asheron's Call is my favorite MMO even considering the amount of EQ, DAOC and WoW that I've played kinda proves it. Long live Darktide!</description>
		<content:encoded><![CDATA[<p>Expectations are the root of all evil <img src='http://eatingbees.brokentoys.org/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
<p>Really.</p>
<p>Everyone is guilty of it at some point. Hell the more MMOs that I play the more I tend to expect. </p>
<p>I think the fact that Asheron&#8217;s Call is my favorite MMO even considering the amount of EQ, DAOC and WoW that I&#8217;ve played kinda proves it. Long live Darktide!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Signs You Are Not Smart Enough To Moderate Boards by sanya</title>
		<link>http://eatingbees.brokentoys.org/2008/02/01/signs-you-are-not-smart-enough-to-moderate-boards/comment-page-1/#comment-3818</link>
		<dc:creator>sanya</dc:creator>
		<pubDate>Fri, 12 Mar 2010 19:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=60#comment-3818</guid>
		<description>Wow. Holy late to the party, Batman. This is a two year old post.

"I quit my TL position when I learned that the "class balance" wasn't being done in terms of relative power, nor relative fun, but rather by relative number of players in a class."

That was not ever the case when I was running the TL program. When it came to bugs, we often prioritized bugs in terms of how many people were being directly affected, but balance decisions were simply never made that way during my tenure.</description>
		<content:encoded><![CDATA[<p>Wow. Holy late to the party, Batman. This is a two year old post.</p>
<p>&#8220;I quit my TL position when I learned that the &#8220;class balance&#8221; wasn&#8217;t being done in terms of relative power, nor relative fun, but rather by relative number of players in a class.&#8221;</p>
<p>That was not ever the case when I was running the TL program. When it came to bugs, we often prioritized bugs in terms of how many people were being directly affected, but balance decisions were simply never made that way during my tenure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Consulting Again by Schirf</title>
		<link>http://eatingbees.brokentoys.org/2010/03/01/consulting/comment-page-1/#comment-3817</link>
		<dc:creator>Schirf</dc:creator>
		<pubDate>Fri, 12 Mar 2010 18:14:31 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.brokentoys.org/?p=269#comment-3817</guid>
		<description>Customers have a hard time understanding coder-hours.  On a software project I mistakenly commented that I felt that I could code a solution to a particular problem in one solid day at the keyboard.  When the estimate was complete and passed to the customer they balked at a 24 hour number.  “You said you could code it in a WORK day, not a 24 hour day!”  We sat down and went over the numbers in detail, which we don’t actually include in the estimate:  

Meeting of three people for two hours to come up with the detailed design = 6 hours
Customer meeting to review design, identify and make minor spec changes, get approval = 2 hours
QA staff member review of spec and creation of test plan = 2 hours
One solid heads down day of coding = 8 hours
Code review with QA = 1 hour (two people / 30 minute meeting)
QA staff member executes test plan = 1 hour
Bug fix time estimate (8 hour coding time x .25) = 2 hours
Demo to customer of completed subsystem = 1 hour
Project wrap up / integration / documentation of lessons learned = 1 hour

Their response “I don’t want to pay for all of that… I just want to pay for the coding!”</description>
		<content:encoded><![CDATA[<p>Customers have a hard time understanding coder-hours.  On a software project I mistakenly commented that I felt that I could code a solution to a particular problem in one solid day at the keyboard.  When the estimate was complete and passed to the customer they balked at a 24 hour number.  “You said you could code it in a WORK day, not a 24 hour day!”  We sat down and went over the numbers in detail, which we don’t actually include in the estimate:  </p>
<p>Meeting of three people for two hours to come up with the detailed design = 6 hours<br />
Customer meeting to review design, identify and make minor spec changes, get approval = 2 hours<br />
QA staff member review of spec and creation of test plan = 2 hours<br />
One solid heads down day of coding = 8 hours<br />
Code review with QA = 1 hour (two people / 30 minute meeting)<br />
QA staff member executes test plan = 1 hour<br />
Bug fix time estimate (8 hour coding time x .25) = 2 hours<br />
Demo to customer of completed subsystem = 1 hour<br />
Project wrap up / integration / documentation of lessons learned = 1 hour</p>
<p>Their response “I don’t want to pay for all of that… I just want to pay for the coding!”</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Signs You Are Not Smart Enough To Moderate Boards by Schirf</title>
		<link>http://eatingbees.brokentoys.org/2008/02/01/signs-you-are-not-smart-enough-to-moderate-boards/comment-page-1/#comment-3816</link>
		<dc:creator>Schirf</dc:creator>
		<pubDate>Fri, 12 Mar 2010 17:44:49 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.wordpress.com/?p=60#comment-3816</guid>
		<description>I was a DAoC team lead for a while.  

I am totally opposed to the idea that something sent to a person is "private" an can't be shared openly.  There are reasons for private messages, and I'm not talking about NDA type stuff... I quit my TL position when I learned that the "class balance" wasn't being done in terms of relative power, nor relative fun, but rather by relative number of players in a class.  I was told that I wasn't allowed to share that information, but did anyway immidiately after quiting, given that it wasn't an NDA issue, nor had I signed any NDA anyway, and I'd already quit the position.

I didn't mind the abuse at the hands of players.  My problem was the abuse at the hands of the VNboard staff who went in and deleted many of my posts.  Almost everything I ever wrote as a TL was removed, including things that had nothing to do with the above incident. Bad taste?  Yup.</description>
		<content:encoded><![CDATA[<p>I was a DAoC team lead for a while.  </p>
<p>I am totally opposed to the idea that something sent to a person is &#8220;private&#8221; an can&#8217;t be shared openly.  There are reasons for private messages, and I&#8217;m not talking about NDA type stuff&#8230; I quit my TL position when I learned that the &#8220;class balance&#8221; wasn&#8217;t being done in terms of relative power, nor relative fun, but rather by relative number of players in a class.  I was told that I wasn&#8217;t allowed to share that information, but did anyway immidiately after quiting, given that it wasn&#8217;t an NDA issue, nor had I signed any NDA anyway, and I&#8217;d already quit the position.</p>
<p>I didn&#8217;t mind the abuse at the hands of players.  My problem was the abuse at the hands of the VNboard staff who went in and deleted many of my posts.  Almost everything I ever wrote as a TL was removed, including things that had nothing to do with the above incident. Bad taste?  Yup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expectations, Part 29548 by Yeebo</title>
		<link>http://eatingbees.brokentoys.org/2010/03/11/expectations-part-29548/comment-page-1/#comment-3812</link>
		<dc:creator>Yeebo</dc:creator>
		<pubDate>Thu, 11 Mar 2010 21:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.brokentoys.org/?p=271#comment-3812</guid>
		<description>Hammer, meet head of nail.  

Most of the big MMO PR plunders I can think of over the last few years come down largely to "managing customer expectations poorly."  See Cryptic's behavior over the last year for some good examples (though their behavior does at least reflect their name well).  You'd think little things like those you mention would be common sense, but in practice...apparently not.</description>
		<content:encoded><![CDATA[<p>Hammer, meet head of nail.  </p>
<p>Most of the big MMO PR plunders I can think of over the last few years come down largely to &#8220;managing customer expectations poorly.&#8221;  See Cryptic&#8217;s behavior over the last year for some good examples (though their behavior does at least reflect their name well).  You&#8217;d think little things like those you mention would be common sense, but in practice&#8230;apparently not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expectations, Part 29548 by Dan Gray</title>
		<link>http://eatingbees.brokentoys.org/2010/03/11/expectations-part-29548/comment-page-1/#comment-3811</link>
		<dc:creator>Dan Gray</dc:creator>
		<pubDate>Thu, 11 Mar 2010 19:06:56 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.brokentoys.org/?p=271#comment-3811</guid>
		<description>Has there been some recent event that's subconciously prompted us to talk about expectation management? I put a post up at KTR about the very same thing today.

Either way, I enjoyed your alternate approach to it.</description>
		<content:encoded><![CDATA[<p>Has there been some recent event that&#8217;s subconciously prompted us to talk about expectation management? I put a post up at KTR about the very same thing today.</p>
<p>Either way, I enjoyed your alternate approach to it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Consulting Again by Ambera</title>
		<link>http://eatingbees.brokentoys.org/2010/03/01/consulting/comment-page-1/#comment-3808</link>
		<dc:creator>Ambera</dc:creator>
		<pubDate>Thu, 11 Mar 2010 09:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://eatingbees.brokentoys.org/?p=269#comment-3808</guid>
		<description>Well, the old tropes aply - their loss being our gain, and all that. Your posts are always informative and entertaining and I look forward to reading more of your thoughts again. Good luck keeping the coffers filled, of course.</description>
		<content:encoded><![CDATA[<p>Well, the old tropes aply - their loss being our gain, and all that. Your posts are always informative and entertaining and I look forward to reading more of your thoughts again. Good luck keeping the coffers filled, of course.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
