TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
fwiw, I learned the concept of "chunking" when I was studying to be a
psychotherapist in the mid-70s. the whole point was to "chunk down" a problem
into manageable components, so it didn't seem so overwhelming. Then, you work
on solving each "chunk"
the other interesting thing I learned in those mis-begotten days was that the
solution to a problem is inherent in the statement of the problem. If there are
no viable solutions, try re-phrasing the problem.
both work a treat.
-becca
George E. Baker wrote:
> For those interested in the direct take on the chunking principle, look up
> the book "Mapping Hyptertext" by Robert E. Horne [ISBN 0-9625565-0-5]. This
> book contains the principles, process, and framework for developing
> materials utilizing the chunking methodology.
--
Becca Price
beccap -at- rust -dot- net
"Wisdom begins when you discover the difference between 'That doesn't make
sense' and "I don't understand.' "
Children of God, by Mary Doria Russell; pg 142-143
