Reply to thread

Message

<blockquote data-quote="WayneF" data-source="post: 310211" data-attributes="member: 12496">You seem to perceive a difference where I don't.&nbsp; The card is only written from the buffer.&nbsp; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Manuals are hard, and in my experience, a separate effort.&nbsp; I have jaded notions, but designers implement the product, and then the tech pubs dept tries to describe using it.&nbsp; Some writers there are really good, but some are summer hires.&nbsp; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp; &nbsp; Designers do know what it does, but are more impressed with subtle features, without much idea how users will perceive it. And generally too busy to be much involved with the manual, that product is already finished. But when I was working, a few times it was me that had to do a first draft manual to send to tech pubs, since otherwise, they had no clue about the product. They tended to think my version was unacceptable, since they really didn't want to know how it works inside, but&nbsp; just wanted a few words about each button or menu (stuff they could see).&nbsp;&nbsp; Both points of view are poor from aspect of user with an overall job to do.&nbsp; But I always thought the user needed to know what it was going to do.&nbsp; Anyway, the finished manual often has surprises and disappointments to the designers.&nbsp; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="WayneF, post: 310211, member: 12496"] You seem to perceive a difference where I don't. The card is only written from the buffer. :) Manuals are hard, and in my experience, a separate effort. I have jaded notions, but designers implement the product, and then the tech pubs dept tries to describe using it. Some writers there are really good, but some are summer hires. :) Designers do know what it does, but are more impressed with subtle features, without much idea how users will perceive it. And generally too busy to be much involved with the manual, that product is already finished. But when I was working, a few times it was me that had to do a first draft manual to send to tech pubs, since otherwise, they had no clue about the product. They tended to think my version was unacceptable, since they really didn't want to know how it works inside, but just wanted a few words about each button or menu (stuff they could see). Both points of view are poor from aspect of user with an overall job to do. But I always thought the user needed to know what it was going to do. Anyway, the finished manual often has surprises and disappointments to the designers. :) [/QUOTE]

Verification