Comments on: Documentation size? http://blog.paulpehrson.com/2006/10/04/documentation-size/ Paul Pehrson's technical writing blog Sat, 22 Nov 2008 08:04:07 +0000 http://wordpress.org/?v=2.6.3 By: Janell the Great http://blog.paulpehrson.com/2006/10/04/documentation-size/#comment-4122 Janell the Great Sun, 08 Oct 2006 07:41:13 +0000 http://blog.paulpehrson.com/2006/10/04/documentation-size/#comment-4122 Who reads the documentation anyway?<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('4122','Janell the Great'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('4122','Janell the Great','Who reads the documentation anyway?'); return false;">Quote</a></div> Who reads the documentation anyway?
Reply - Quote
]]> By: paul http://blog.paulpehrson.com/2006/10/04/documentation-size/#comment-4039 paul Wed, 04 Oct 2006 21:34:10 +0000 http://blog.paulpehrson.com/2006/10/04/documentation-size/#comment-4039 Kat - I think Dave is right. It must be some weird memory issue. It was part of a larger assessment of the product, so maybe it started with needing to know the size of the various components, and they added documentation as an afterthought without reconsidering the information they were requesting. Dave - You make me laugh. The Dilbert and the shop analogies are so right on. At least that is what it <i>feels</i> like. :)<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('4039','paul'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('4039','paul','Kat - I think Dave is right. It must be some weird memory issue. It was part of a larger assessment of the product, so maybe it started with needing to know the size of the various components, and they added documentation as an afterthought without reconsidering the information they were requesting.\r\n\r\nDave - You make me laugh. The Dilbert and the shop analogies are so right on. At least that is what it <i>feels<\/i> like. :)'); return false;">Quote</a></div> Kat - I think Dave is right. It must be some weird memory issue. It was part of a larger assessment of the product, so maybe it started with needing to know the size of the various components, and they added documentation as an afterthought without reconsidering the information they were requesting.

Dave - You make me laugh. The Dilbert and the shop analogies are so right on. At least that is what it feels like. :)

Reply - Quote
]]> By: Dave http://blog.paulpehrson.com/2006/10/04/documentation-size/#comment-4038 Dave Wed, 04 Oct 2006 21:27:43 +0000 http://blog.paulpehrson.com/2006/10/04/documentation-size/#comment-4038 The only thing I can think of is that they were concerned about space on a disk or hard drive or something like that. I get that question all the time... from the build team though, and for them that is reasonable since they are literally trying to fit everything into a certain amount of memory space. Then again, maybe your client was trying to act knowledgable like I do when I walk into a car mechanic's shop. "Ahhh, yeah... I think I might have a loose rotary cufflink converter on the... uh... on the momentum translator sytem. ... ... yeah." Of course, there is always the third option: The Dilbert Solution. Reminds me so well of the time that the Pointy Haired Boss firmly declared that a mauve CPU had the most RAM. Yep.<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('4038','Dave'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('4038','Dave','The only thing I can think of is that they were concerned about space on a disk or hard drive or something like that. I get that question all the time... from the build team though, and for them that is reasonable since they are literally trying to fit everything into a certain amount of memory space. \r\n\r\nThen again, maybe your client was trying to act knowledgable like I do when I walk into a car mechanic\'s shop. \"Ahhh, yeah... I think I might have a loose rotary cufflink converter on the... uh... on the momentum translator sytem. ... ... yeah.\"\r\n\r\nOf course, there is always the third option: The Dilbert Solution. Reminds me so well of the time that the Pointy Haired Boss firmly declared that a mauve CPU had the most RAM. \r\n\r\nYep.'); return false;">Quote</a></div> The only thing I can think of is that they were concerned about space on a disk or hard drive or something like that. I get that question all the time… from the build team though, and for them that is reasonable since they are literally trying to fit everything into a certain amount of memory space.

Then again, maybe your client was trying to act knowledgable like I do when I walk into a car mechanic’s shop. “Ahhh, yeah… I think I might have a loose rotary cufflink converter on the… uh… on the momentum translator sytem. … … yeah.”

Of course, there is always the third option: The Dilbert Solution. Reminds me so well of the time that the Pointy Haired Boss firmly declared that a mauve CPU had the most RAM.

Yep.

Reply - Quote
]]> By: Katrina http://blog.paulpehrson.com/2006/10/04/documentation-size/#comment-4037 Katrina Wed, 04 Oct 2006 19:45:22 +0000 http://blog.paulpehrson.com/2006/10/04/documentation-size/#comment-4037 People ask the weirdest things, sometimes. Did you ask why he wanted to know in bytes rather than pages or something?<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('4037','Katrina'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('4037','Katrina','People ask the weirdest things, sometimes. Did you ask why he wanted to know in bytes rather than pages or something?'); return false;">Quote</a></div> People ask the weirdest things, sometimes. Did you ask why he wanted to know in bytes rather than pages or something?
Reply - Quote
]]>