Comments on: Document it… http://www.yellow-bricks.com/2009/11/04/document-it/ Building blocks for virtualization... Sat, 20 Mar 2010 13:02:53 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: daniel http://www.yellow-bricks.com/2009/11/04/document-it/comment-page-1/#comment-5000 daniel Thu, 05 Nov 2009 09:06:13 +0000 http://www.yellow-bricks.com/?p=4448#comment-5000 I didn't use to document what I did before I started working in the defence industry, few people actually read and benefit from all the hours I put in documenting, but atleast now I know that if I have to do something twice I already know the pitfalls and all the information isn't lost with me. Documenting a little is better than nothing at all, the rest is a matter of discipline. I didn’t use to document what I did before I started working in the defence industry, few people actually read and benefit from all the hours I put in documenting, but atleast now I know that if I have to do something twice I already know the pitfalls and all the information isn’t lost with me. Documenting a little is better than nothing at all, the rest is a matter of discipline.

]]> By: Nicolai http://www.yellow-bricks.com/2009/11/04/document-it/comment-page-1/#comment-4998 Nicolai Wed, 04 Nov 2009 19:06:13 +0000 http://www.yellow-bricks.com/?p=4448#comment-4998 Note to self, for the Defence exam ;-) Completly agrees on it though. The major drawback on this is that, it requires the reciever of the design to actually read it. :-) Note to self, for the Defence exam ;-)

Completly agrees on it though. The major drawback on this is that, it requires the reciever of the design to actually read it. :-)

]]> By: Duncan Epping http://www.yellow-bricks.com/2009/11/04/document-it/comment-page-1/#comment-4996 Duncan Epping Wed, 04 Nov 2009 15:57:53 +0000 http://www.yellow-bricks.com/?p=4448#comment-4996 At least they can't say they did not know about these constraints or requirements. I tend to add it to the beginning of the documentation instead of at the end so it is the first thing people see / read. (or skip for that matter...) At least they can’t say they did not know about these constraints or requirements. I tend to add it to the beginning of the documentation instead of at the end so it is the first thing people see / read. (or skip for that matter…)

]]> By: iHunger http://www.yellow-bricks.com/2009/11/04/document-it/comment-page-1/#comment-4995 iHunger Wed, 04 Nov 2009 15:28:31 +0000 http://www.yellow-bricks.com/?p=4448#comment-4995 I agree with this in principle, but the cynical side of me thinks that documenting the decisions/constraints won't prevent someone arbitrarily changing the design, it only means you can give them grief later for messing everything up. I agree with this in principle, but the cynical side of me thinks that documenting the decisions/constraints won’t prevent someone arbitrarily changing the design, it only means you can give them grief later for messing everything up.

]]>