|
|
|
by Douglas Dow, Managing Editor
October's content explores the continuing identity crisis faced by technical communicators. From Debbie Wiles' meditation on "technical" as the roadblock to our public perception, to Jackie Damrau's contributions on self-understanding in the workplace, to Region 7 Director-Sponsor Rahel Bailie's cogent question, we see new terminology applied to what we do. Human factors architect? Commodity writer? Strategic Communicator? How much longer before we merge totally with the usability and instructional design professions? Or have we done that already?
Newsletter Competition
By the time most of you read this, I'll have filled out the entry forms for next year's competition. (That's a scary process, but only to STC newsletter editors.) Technically Write has beefed up some of its content in the hope that the judges will find all they need to find. The Society's mission statement, for example, which used to dominate the cover page, now has its own section under About Technically Write (Necessary also because the new mission statement is longer.). We have also improved much of the information in the About Technically Write section.
Other than attending to these "required elements," there's not much more I can do. Perhaps you can help. Are you testing new software? Are you reading a great new book that's helping you enhance your performance? What Web sites are features of your "favorites" list? Are you, in fact, one of the many subject matter experts in the area that belong to Lone Star Chapter? Technically Write would love to publish a feature article in which you share your knowledge. We know you're out there! Start that article before the holiday season encroaches on your time.