Comments on: Different kinds of documentation http://arcadeberg.com/causerie/different-kinds-of-documentation/ aka. "Learning Game Design with Arcade Berg" Fri, 23 Mar 2012 19:21:51 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: HCG Levels in Early Pregnancy http://arcadeberg.com/causerie/different-kinds-of-documentation/comment-page-1/#comment-21703 HCG Levels in Early Pregnancy Sun, 09 Oct 2011 02:07:17 +0000 http://arcadeberg.com/?p=854#comment-21703 <strong>HCG Levels in Early Pregnancy Thanks for writing this, it was very handy and helped me quite a bit...</strong> Thanks for writing this, it was very handy and helped me quite a bit... HCG Levels in Early Pregnancy Thanks for writing this, it was very handy and helped me quite a bit…

Thanks for writing this, it was very handy and helped me quite a bit…

]]> By: Arcade http://arcadeberg.com/causerie/different-kinds-of-documentation/comment-page-1/#comment-3812 Arcade Mon, 09 Nov 2009 22:52:41 +0000 http://arcadeberg.com/?p=854#comment-3812 Thanks for the input. And I totally agree with changes having to be very clear. Thanks for the input.
And I totally agree with changes having to be very clear.

]]> By: Statement http://arcadeberg.com/causerie/different-kinds-of-documentation/comment-page-1/#comment-3811 Statement Mon, 09 Nov 2009 22:44:33 +0000 http://arcadeberg.com/?p=854#comment-3811 I prefer [reading/working with] wiki style documentation as long as the wiki is easy to navigate and that new changes are clearly marked as such. I don't want to wander around in a lonesome forest trying to find the princess, I want the princess come find me. Though I agree, static designs (and boy are they easier to work with) should be in a precise document since there is no need for any changes. The most important aspect is that any changes loudly should be made clear to any readers. I am allergic to changes that are silently added, often in the form of one page that is changed but another one isn't. Make changes in all dependencies, because we (the developers) have to! And please, read it through. Does the document clearly contradict itself? It's just sloppy to hand out something that does. :) I prefer [reading/working with] wiki style documentation as long as the wiki is easy to navigate and that new changes are clearly marked as such. I don’t want to wander around in a lonesome forest trying to find the princess, I want the princess come find me. Though I agree, static designs (and boy are they easier to work with) should be in a precise document since there is no need for any changes. The most important aspect is that any changes loudly should be made clear to any readers. I am allergic to changes that are silently added, often in the form of one page that is changed but another one isn’t. Make changes in all dependencies, because we (the developers) have to! And please, read it through. Does the document clearly contradict itself? It’s just sloppy to hand out something that does. :)

]]>