Reply to thread

Message

<blockquote data-quote="Digital Archon" data-source="post: 2812212" data-attributes="member: 33706">Ok, let me see if i got this straight:I'm kind of talking tangential to the topic, but i'll get back to it in a moment.There is Publisher X. They have selected your group to play test one of their products. During playtest (though i guess it's technically before playtest even began), you have discovered errors and contacted them about it, thereby doing what they've &quot;contracted&quot; you for (i don't konw if it's a real contract, or something else). Publisher X has not gotten back to you, not even with a &quot;thanks for noticing&quot;. How long ago did you send this mail? This seems kind of odd that they'd send stuff out for playtest, and not acknowledge the playtest teams in any way. It's kind of a mixed message &quot;We care about playtesting our product, but we don't care about hearing about it&quot;. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f615.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":confused:" title="Confused&nbsp; &nbsp; :confused:"&nbsp; data-smilie="5"data-shortname=":confused:" /> Anyway, back to the topic. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" />&nbsp; I operate under the following procedure:If it's obviously stupidly broken and important to the product, i either fix it if it won't take much time and there's only a couple of screwy things, or dump the module onto the &quot;steal ideas from, but won't run&quot; pile, if there's a lot.If it's obviously stupidly broken and not important to the product, i get rid of it entirely. I don't have the time to screw around with stuff that should have been caught during playtest, and since it's not important, i won't bother trying to fix it.If it's just something minor and important to the product, then i'll fix it enough that it won't cause a problem.If it's just something minor and not important to the product, then i'll consider fixing it enough that it won't cause a problem. I might just ignore the problem as well. This one is a judgement call, more than anything.</blockquote>

[QUOTE="Digital Archon, post: 2812212, member: 33706"] Ok, let me see if i got this straight: I'm kind of talking tangential to the topic, but i'll get back to it in a moment. There is Publisher X. They have selected your group to play test one of their products. During playtest (though i guess it's technically before playtest even began), you have discovered errors and contacted them about it, thereby doing what they've "contracted" you for (i don't konw if it's a real contract, or something else). Publisher X has not gotten back to you, not even with a "thanks for noticing". How long ago did you send this mail? This seems kind of odd that they'd send stuff out for playtest, and not acknowledge the playtest teams in any way. It's kind of a mixed message "We care about playtesting our product, but we don't care about hearing about it". :confused: Anyway, back to the topic. :) I operate under the following procedure: If it's obviously stupidly broken and important to the product, i either fix it if it won't take much time and there's only a couple of screwy things, or dump the module onto the "steal ideas from, but won't run" pile, if there's a lot. If it's obviously stupidly broken and not important to the product, i get rid of it entirely. I don't have the time to screw around with stuff that should have been caught during playtest, and since it's not important, i won't bother trying to fix it. If it's just something minor and important to the product, then i'll fix it enough that it won't cause a problem. If it's just something minor and not important to the product, then i'll consider fixing it enough that it won't cause a problem. I might just ignore the problem as well. This one is a judgement call, more than anything. [/QUOTE]

Verification