SavinDwa
07-29-2005, 12:58 AM
<DIV>I'm sure the developers in SOE do an excellent job (programmers, designers, et al). But the latest change to guild status makes me wonder about the whole process.</DIV> <DIV> </DIV> <DIV>I'm sure it took time to think the change through</DIV> <DIV> </DIV> <DIV>It took time to design the change</DIV> <DIV> </DIV> <DIV>It took time to code the change</DIV> <DIV> </DIV> <DIV>It took time to implement it and do first level integration testing.</DIV> <DIV> </DIV> <DIV>It took time to move it to test</DIV> <DIV> </DIV> <DIV>It took time to write the patch notes</DIV> <DIV> </DIV> <DIV>This adds up to a lot of effort. With a little more effort you could have explained why you felt the change was required -- I assume that someone knows why? This would have helped.</DIV> <DIV> </DIV> <DIV>I'm personally pretty sure that the change as designed will not work and with any luck will not go live. 90% of the feed back is consistent and negative. The flaws are pretty obvious to most people playing the game.</DIV> <DIV> </DIV> <DIV>I don't think anyone is stupid for having made this change. We all know what happens when you get ina room and youa re asked to solve "problem A" -- its amazing how often it is overlooked that while it solves problem A it causes problems B and C.</DIV> <DIV> </DIV> <DIV>HOWEVER!!!</DIV> <DIV> </DIV> <DIV>You could have thought through .. jumped right to "writing the patch notes" added the "this is the problem we are solving" and posted it here and youn would have had the same feed back. You would have saved a lot of designer and programmer time in the process.</DIV> <DIV> </DIV> <DIV>You have a large user community and it can give good and bad feed back, but as long as you learn to spot the good feedback you win.</DIV> <DIV> </DIV> <DIV>So ... why code these major changes before testing them on the community in a "potential patch release notes" and save all the coding and stuff until you are sure you have the design right.</DIV> <DIV> </DIV> <DIV>There has got to be a better way than</DIV> <DIV> </DIV> <DIV>design</DIV> <DIV>code</DIV> <DIV>install on test</DIV> <DIV>listen to user feed back on design</DIV> <DIV>design </DIV> <DIV>code </DIV> <DIV>install on test ...</DIV> <DIV> </DIV> <DIV> </DIV> <DIV>hmm...</DIV> <DIV> </DIV> <DIV>You can get a lot of feed back without coding and installing code but by producing propsed patch notes. its something to think about.</DIV> <DIV> </DIV> <DIV>It might also help if you started explaining why you are making the change -- if we knnew we might say "hmm that's a good point, we had not thought about that:</DIV> <DIV> </DIV> <DIV> </DIV><p>Message Edited by SavinDwarf on <span class=date_text>07-28-2005</span> <span class=time_text>01:59 PM</span>