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.
>>[Somebody] wrote:
>>
>>"When she presented this task to the class,
>> everyone initially took Stephen Victor's attitude: what the
>> fuck does this have to do with technical writing, and why
>> are you insulting my intelligence with this? (This attitude
>> is less forgivable for a student, but still surprising for..."
>>
>>I found the language in your post offensive and did not read past the
>>vulgar language.
>>
>>I personally would appreciate it if you would refrain from using vulgar
>>language in your communications. We are writers and I think that more
>>creative words are available in our vocabularies.\
>>
>>Robin
>I have to agree with Robin. I really don't care about foul language in many
>contexts, but using this sort of language on the tech writer list is
>definitely not appropriate. We shouldn't have to have someone supervising
>the list, but at times like these it seems like a good idea.
>- Tony G. Rocco
I agree too--it's times like this that make it seem like a good idea to
have some master point of control, protecting me from seeing something
"inappropriate" that might bother or offend me. I realize the original post
was on-topic and had a point to make, but I just couldn't
read on after seeing that...that...WORD.
In the future, original poster, please be more aware of my own personal
tastes and avoid using language I consider vulgar or lacking in
creativity.
Thanks,
Brent
Searchable archives located at http://www.documentation.com/
ALL questions or problems concerning the list
should go to the listowner, Eric Ray at ejray -at- ionet -dot- net -dot-