note haxordan <p> A<code>[X]</code> B<code>[X]</code> C<code>[ ]</code> D<code>[ ]</code> </p> <p> I would say a combination of A and B. While it's great to brainstorm to solve a problem, you also need to be able to "sell" your idea should someone should think that you are on the right path to a solution. Feel free to post your ideas, but also be able to back them up (even if it's just with a toy problem) with some proof. That way, you not only will be helping others, but you will also gain experience through your testing. </p> <p>I often look at my code and think "How can I break this?" I try. That way, when I release something, I know it will indeed solve the problem it addresses. Not only does this produce good, stable code, but it also expands your knowledge of the implementation. </p> <p> Just my thoughts. </p> <p> --<br> haxordan </p> <p> If the world is to end in a whisper, I hope that it's not someone whispering,"I wonder what this button does?" -DTB </p> 232157 232157