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.
<<The end user doesn't need or want to know about such things as file <<structures, parameters types, function calls, etc., etc. The end user <<wants to know "How do I use this program to do my resume/term <<paper, etc."
That all depends on who your end user is! Not all of us write documentation for word processing programs ;-) Some of us write technical documentation for how to use new programming languages, databases, or network software that require the user to understand file structures, parameter types, function calls, etc.
IMHO I guess what it boils down to is that some of us are better prepared to write to the highly technical audiences than others. It is what makes us stand out in the technical writing field and keeps our customers coming back to us.
