<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>TC</title>	<link>http://tc.eserver.org/dir/TC</link>
	<description>A listing of the most recently indexed works about TC in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>TC</title>
		<link>http://tc.eserver.org/dir/TC</link>
	</image>
	<item>
		<title>Musings About What’s Really Important</title>
		<link>http://tc.eserver.org/35843.html</link>
		<guid>http://tc.eserver.org/35843.html</guid>
		<description>Technical communicators tend to get caught up in tools and techniques and formats. But, as Scott Abel said, It’s not about tech writing. It’s about content.</description>
	</item>
	<item>
		<title>Basic Etiquette of Technical Communication</title>
		<link>http://tc.eserver.org/35838.html</link>
		<guid>http://tc.eserver.org/35838.html</guid>
		<description>Parents spend years trying to teach their children to be polite, and some of us had to learn at school how to properly address an archbishop. Yet, it seems that advice on courteousness and politeness in technical communication is in short supply; most of us learn these skills through what is euphemistically called “on the job training.” With enough bruises on my back to demonstrate the amount and variety of my experience in this area (though not my skill), here are some of the things I’ve learned.</description>
	</item>
	<item>
		<title>Charlotte Regional STC Chapter</title>
		<link>http://tc.eserver.org/35808.html</link>
		<guid>http://tc.eserver.org/35808.html</guid>
		<description>The Charlotte Regional chapter of STC serves primarily members in and nearby the city of Charlotte, North Carolina.</description>
	</item>
	<item>
		<title>Doing Good with Technical Communication Skills</title>
		<link>http://tc.eserver.org/35831.html</link>
		<guid>http://tc.eserver.org/35831.html</guid>
		<description>Writers suggest people maintain or improve skills – or develop new skills – in some open-source type project where there is no pay, but plenty of opportunity to learn and, well, practice. This post is for sharing a few of those places of practice.</description>
	</item>
	<item>
		<title>Sometimes, You&apos;ve Got to Break the Rules</title>
		<link>http://tc.eserver.org/35788.html</link>
		<guid>http://tc.eserver.org/35788.html</guid>
		<description>Sometimes, you don’t need documentation made up of perfectly-chosen words and phrases. Instead, you need something that can be easily scanned, easily understood, and easily digested. Documentation that distills the main points quickly.</description>
	</item>
	<item>
		<title>What Technical Communicators Need to Know About Flash</title>
		<link>http://tc.eserver.org/35767.html</link>
		<guid>http://tc.eserver.org/35767.html</guid>
		<description>What is Flash? It&apos;s a vector-based format for moving images. Adobe technology via Macromedia Proprietary FLA for Flash development files. SWF for compressed files.</description>
	</item>
	<item>
		<title>Reverse Engineering SIGs</title>
		<link>http://tc.eserver.org/35757.html</link>
		<guid>http://tc.eserver.org/35757.html</guid>
		<description>STC SIGs are like areas where outside professions insert specialized instances of their expertise into our profession. But what if we could reverse that gateway? Our SIGs could be an excellent outreach channel to market our specialized knowledge into those other professions.</description>
	</item>
	<item>
		<title>Society for Technical Communications tries to define Technical Communicator and Fails</title>
		<link>http://tc.eserver.org/35721.html</link>
		<guid>http://tc.eserver.org/35721.html</guid>
		<description>Maybe the confusion that surrounds the STC is its inability to define who it serves. Maybe the STC is trying to drum up support and be more inclusive.</description>
	</item>
	<item>
		<title>The Growing Sector of Technical Communication in India</title>
		<link>http://tc.eserver.org/35675.html</link>
		<guid>http://tc.eserver.org/35675.html</guid>
		<description>Over the past decades, technical communication in India has grown from an unknown profession to an indispensable part of many industries and sectors. A testimony to the maturity and significance of this professional field is the tremendous growth of the so-called TWIN community, representing the Technical Communicators of India.</description>
	</item>
	<item>
		<title>STC: Help the Communities Provide Value</title>
		<link>http://tc.eserver.org/35540.html</link>
		<guid>http://tc.eserver.org/35540.html</guid>
		<description>Much has been said about the problem the Society for Technical Communication has found itself in, including on blogs, Twitter, and email listservs. I’ve deliberately kept quiet here until I had some semblance of perspective to offer. But I’ve come to the conclusion that maybe this is a crisis STC needed—an impetus to get us all thinking together about how to improve the model, how to offer more direct benefits to the members.</description>
	</item>
	<item>
		<title>Why Technical Communicators Should Help with Product Text</title>
		<link>http://tc.eserver.org/35529.html</link>
		<guid>http://tc.eserver.org/35529.html</guid>
		<description>A huge problem for projects is the lack of a common language between the developers and the users. When my colleague and I were preparing a presentation for an internal conference on this subject, he said something that has stuck with me. He said, “The goal of the project is to make the user successful.” I added to that: It’s not to write code or validate code. It’s not even to ship a product or make money (of course, this last one is especially true in a non-profit organization). At least, it shouldn’t be these things.</description>
	</item>
	<item>
		<title>Listen to the Radio</title>
		<link>http://tc.eserver.org/35510.html</link>
		<guid>http://tc.eserver.org/35510.html</guid>
		<description>Radio and documentation. It sounds like a strange, if not incompatible, mix. But as Scott Nesbitt explains, an  ideal model for writing documentation is a good radio report.</description>
	</item>
	<item>
		<title>Learn How Much You Don’t Know</title>
		<link>http://tc.eserver.org/35494.html</link>
		<guid>http://tc.eserver.org/35494.html</guid>
		<description>I’m amazed when I hear people say they learn nothing from others in the technical communication field. Some people have a lot of experience, so they feel there are few opportunities to learn from others. I believe they forget that often through discussions, we discover a new perspective or a new way to solve an old problem. Different approaches can also lead to new techniques and solutions.</description>
	</item>
	<item>
		<title>User-Centered Design for Technical Communicators</title>
		<link>http://tc.eserver.org/35450.html</link>
		<guid>http://tc.eserver.org/35450.html</guid>
		<description>How can user-centered design principles be applied to technical communication?</description>
	</item>
	<item>
		<title>Technical Communication: Design or Content?</title>
		<link>http://tc.eserver.org/35445.html</link>
		<guid>http://tc.eserver.org/35445.html</guid>
		<description>How is the role of technical communicators changing? What skills should we be focused on for future success? With content coming from many sources and contributors throughout the community, technical communicators can feel threatened. For many years, we were the sole developers of content, carefully crafting each phrase to deliver information clearly and concisely. As social media expands, our skills for crafting the message may become less important and less valued.</description>
	</item>
	<item>
		<title>Intercom Q&amp;A: Saul Carliner Answers Your Questions</title>
		<link>http://tc.eserver.org/35427.html</link>
		<guid>http://tc.eserver.org/35427.html</guid>
		<description>Branding encompasses everything you do. If you participate in your STC chapter, for example, how does that promote your brand? If you write for a SIG or chapter newsletter or website, or some similar outlet--or give a presentation to one of those groups--how do these activities promote your brand?</description>
	</item>
	<item>
		<title>STC Notebook</title>
		<link>http://tc.eserver.org/35429.html</link>
		<guid>http://tc.eserver.org/35429.html</guid>
		<description>The official voice of the Society for Technical Communication and a blog to enable the tech comm community.</description>
	</item>
	<item>
		<title>How DITA Changed the Tech Comm Landscape</title>
		<link>http://tc.eserver.org/35432.html</link>
		<guid>http://tc.eserver.org/35432.html</guid>
		<description>Before DITA, we told readers how things worked. After DITA, we tell users how to use things. Before, we wrote information linearly. After, we write individual units as needed.</description>
	</item>
	<item>
		<title>The Technical Communication Internship </title>
		<link>http://tc.eserver.org/35412.html</link>
		<guid>http://tc.eserver.org/35412.html</guid>
		<description>Experiential learning theory provides a theoretical foundation for studying technical communication internships. This study explores, through the perspective of the experiential learning cycle model developed by David Kolb, internships in technical communication. Participants in technical communication internship experiences were asked to provide, from their different perspectives, information that described the experience. Program directors, industrial supervisors, and student interns provided different views of what they had experienced, illustrating that most had entirely different perspectives on their level of participation in creating, supervising, and evaluating this form of educational experience. Besides describing technical communication programs in the United States more comprehensively, the results of this study raise questions about how the respondents perceived their experience and how the &quot;reality&quot; of these perceptions often conflict. When these findings are explored within the epistemology conceptualized by Kolb&apos;s experiential learning theory, a framework is established for more systemic procedures and standards that will enhance the internship as a credible learning experience.</description>
	</item>
	<item>
		<title>Mentoring in Technical Communication</title>
		<link>http://tc.eserver.org/35353.html</link>
		<guid>http://tc.eserver.org/35353.html</guid>
		<description>Reports on an online survey of 158 technical communication teachers who were asked about their experiences with mentoring. Finds a divergence between the academic mentor&apos;s experiences in mentoring and previously reported research on the protégée&apos;s mentoring experiences. Argues that risks are inherent in mentoring and proposes a new model that acknowledges them.</description>
	</item>
	<item>
		<title>Putting China&apos;s Technical Communication into Historical Context</title>
		<link>http://tc.eserver.org/35357.html</link>
		<guid>http://tc.eserver.org/35357.html</guid>
		<description>Examines the Chinese culinary instruction genre. Analyzes culinary texts produced from 500 BC to the present. Argues for a historicized and contextualized understanding of technical communication in China.</description>
	</item>
	<item>
		<title>Auswahl eines Help Authoring Tools</title>
		<link>http://tc.eserver.org/35344.html</link>
		<guid>http://tc.eserver.org/35344.html</guid>
		<description>Checkliste der wichtigsten Kriterien für die Auswahl eines Tools zum Erstellen von Software-Dokumentation (Handbücher, Online-Hilfen) - sog. Help Authoring Tools, kurz HAT. Viele Help Authoring Tools können Benutzerhandbücher und Online-Hilfen aus einer gemeinsamen Textquelle heraus generieren (sog. Single Source Publishing).</description>
	</item>
	<item>
		<title>Auswahl eines Screen Capture Tools</title>
		<link>http://tc.eserver.org/35345.html</link>
		<guid>http://tc.eserver.org/35345.html</guid>
		<description>Screenshots oder Screencaptures). Benötigt werden Screenshots in allen Formen von Software-Dokumentation, z.B. für Handbücher, Online-Hilfen, interaktive Demos und Tutorials, aber auch für Webseiten oder Broschüren.</description>
	</item>
	<item>
		<title>Auswahl eines Screencasting Tools</title>
		<link>http://tc.eserver.org/35346.html</link>
		<guid>http://tc.eserver.org/35346.html</guid>
		<description>Checkliste der wichtigsten Kriterien für die Auswahl eines Tools zum Erstellen interaktiver Software-Demos (engl. Screencasts). Verwendet werden Software-Demos oder Screencasts nicht nur auf Webseiten, sondern häufig auch als Ergänzung zur Technischen Dokumentation für Software: z.B. als eigenständiges Tutorial oder auch als integrativer Bestandteil einer Online-Hilfe oder sonstiger Software-Dokumentation.</description>
	</item>
	<item>
		<title>The Council for Programs in Technical and Scientific Communication at 35 Years: A Sequel and Perspective</title>
		<link>http://tc.eserver.org/35332.html</link>
		<guid>http://tc.eserver.org/35332.html</guid>
		<description>Building on the 1996 retrospective by Pearsall and Warren, the authors examine the decade that followed for the Council for Programs in Technical and Scientific Communication (CPTSC). As the world became more closely knitted together through trade agreements and advancements in communication technology, CPTSC took up its mission in response as it helped promote program growth internationally. During this period, the organization added many more members beyond the United States, as it hosted a series of roundtables in Europe and Canada, working to diversify the ethnic make-up of its membership through scholarships.</description>
	</item>
	<item>
		<title>A Mercenary View of STC</title>
		<link>http://tc.eserver.org/35316.html</link>
		<guid>http://tc.eserver.org/35316.html</guid>
		<description>The mission of STC is to “advance the arts and sciences of technical communication.” How does this help you, the member? I have been a freelancer/business owner for the vast majority of my career (so far). Let me say a few things about STC’s value proposition for mercenaries like me.</description>
	</item>
	<item>
		<title>Best Jobs in America 2009: Technical Writer</title>
		<link>http://tc.eserver.org/35296.html</link>
		<guid>http://tc.eserver.org/35296.html</guid>
		<description>Technical writers write technical materials, such as equipment manuals, online help documentation, operating directions and maintenance instructions. Rank: 28th best job in America.</description>
	</item>
	<item>
		<title>STC: Quo Vadis?</title>
		<link>http://tc.eserver.org/35186.html</link>
		<guid>http://tc.eserver.org/35186.html</guid>
		<description>I need to figure out where I am with all the STC stuff going on, and blogging will help my introspection. Also, it will let me share with you some of the background and complexity that surround the current state of affairs with STC. My e-mail tag line reads &quot;Anyone who is sure of the answer doesn&apos;t understand the question,&quot; and this blog is an invitation to join me in understanding how we got here, where we are, and where I think we need to go.</description>
	</item>
	<item>
		<title>Get Passionate about Technical Communication</title>
		<link>http://tc.eserver.org/35194.html</link>
		<guid>http://tc.eserver.org/35194.html</guid>
		<description>Introverted people aren’t normally considered passionate. Even if you’re an extrovert, would you consider yourself passionate about technical communication?</description>
	</item>
	<item>
		<title>Organizational Demography: The Differential Effects of Age and Tenure Distributions on Technical Communication</title>
		<link>http://tc.eserver.org/35128.html</link>
		<guid>http://tc.eserver.org/35128.html</guid>
		<description>Although previous researchers have proposed organizational demography as an important determinant of communication, no one has tested this relationship directly.</description>
	</item>
	<item>
		<title>How to Get a Job in Technical Writing: A 7-Step Guide for Students</title>
		<link>http://tc.eserver.org/35148.html</link>
		<guid>http://tc.eserver.org/35148.html</guid>
		<description>If you’re a college student looking to become a technical writer after you graduate, you face a formidable challenge: you can’t get a job without experience, and you can’t get experience without a job. Especially in a competitive job market, getting a job as a technical writer directly after you graduate — without a foundation of previous jobs, experience with a handful of tools, and an impressive portfolio — can be especially difficult. However, if you follow these seven steps, which are not easy, not something you can do overnight, you will find a job.</description>
	</item>
	<item>
		<title>Contributing to Wikis: A Useful Activity for Novice Tech Writers?</title>
		<link>http://tc.eserver.org/35124.html</link>
		<guid>http://tc.eserver.org/35124.html</guid>
		<description>In this post, technical writer Milan Davidovic that contributing to wikis can help novices build skills and a portfolio. And he offers a simple roadmap for doing that effectively.</description>
	</item>
	<item>
		<title>Technical Communication</title>
		<link>http://tc.eserver.org/35113.html</link>
		<guid>http://tc.eserver.org/35113.html</guid>
		<description>This newsgroup posts news, trends, and articles about the field of technical communication.</description>
	</item>
	<item>
		<title>Technical Communication in R &amp; D Laboratories: The Impact of Project Work Characteristics</title>
		<link>http://tc.eserver.org/35117.html</link>
		<guid>http://tc.eserver.org/35117.html</guid>
		<description>Based on an information processing approach to organizations, this paper argues that product effectiveness is contingent on the match between the project&apos;s communication patterns and the nature of its work.</description>
	</item>
	<item>
		<title>Thinking Outside the Book</title>
		<link>http://tc.eserver.org/35108.html</link>
		<guid>http://tc.eserver.org/35108.html</guid>
		<description>The notes for a presentation (titled Thinking Outside the Book: Wikis for Writing and Delivering Documentation, that discusses the whys, the tools, and the techniques of using wikis for documentation.</description>
	</item>
	<item>
		<title>Conversation and Community: a review (of sorts) in about 1,700 words </title>
		<link>http://tc.eserver.org/35083.html</link>
		<guid>http://tc.eserver.org/35083.html</guid>
		<description>Technical communication is changing rapidly. If you’re not ready for that change, it’s going to really catch you off guard. Anne Gentle&apos;s book Conversation and Community is an excellent guide to rolling with those changes, and for staying ahead of them. This article takes a close look at the book.</description>
	</item>
	<item>
		<title>conneXions: International Professional Communication Journal</title>
		<link>http://tc.eserver.org/35069.html</link>
		<guid>http://tc.eserver.org/35069.html</guid>
		<description>The journal is dedicated to promoting and developing efficient and effective single and multimedia communication and its constituent communities in local, national, international, and global worksite and civic settings. The publication&apos;s major topics lie at the intersection of International Professional Communication.</description>
	</item>
	<item>
		<title>Four Useful Skills for the Technical Communicator</title>
		<link>http://tc.eserver.org/34976.html</link>
		<guid>http://tc.eserver.org/34976.html</guid>
		<description>Skills. For the technical communicator, skills should go beyond the tools and techniques of the trade. This blog post looks at four skills that will be of use to any technical communicator.</description>
	</item>
	<item>
		<title>Rethinking the Articulation Between Business and Technical Communication and Writing in the Disciplines: Useful Avenues for Teaching and Research</title>
		<link>http://tc.eserver.org/34918.html</link>
		<guid>http://tc.eserver.org/34918.html</guid>
		<description>In a profound sense, the teaching of business and technical communication (BTC) is always already the teaching of writing in the disciplines (WID). Yet the WID dimension of BTC is often hard to see. The question this article addresses is, How might the North American tradition of BTC communication courses be more consciously—and effectively—articulated with the disciplines? The article reviews some of the research literature concerning the value of articulating BTC with WID in undergraduate education and program descriptions of such efforts to examine what BTC has done, is doing, and might do in the future to strengthen WID in BTC.</description>
	</item>
	<item>
		<title>Technical Communicators as Potential Usability Reviewers</title>
		<link>http://tc.eserver.org/34946.html</link>
		<guid>http://tc.eserver.org/34946.html</guid>
		<description>There are many articles on the web, which have deliberated upon technical communication (TC) and usability together. Apparently, there are two distinct regions of usability where technical communicators can contribute.</description>
	</item>
	<item>
		<title>Tech Comm Lobotomies</title>
		<link>http://tc.eserver.org/34898.html</link>
		<guid>http://tc.eserver.org/34898.html</guid>
		<description>Although we look at the past with embarrassment about some of our practices, we often lack the foresight to see the present with the same degree of scrutiny. Years from now, we’ll look back at what we’re currently doing and not only blush, but feel remorse and wish we could get back what we lost.</description>
	</item>
	<item>
		<title>The Four Layers of the “Learning Pyramid” for a Junior Technical Communicator</title>
		<link>http://tc.eserver.org/34862.html</link>
		<guid>http://tc.eserver.org/34862.html</guid>
		<description>Once you take an interest in technical communication and documentation you’ll quickly discover that’s it’s an “endless country,” really. There is so much to learn and track since both the market and the technology changes constantly. But this does not mean that you can learn things randomly and become a successful technical communicator.&#xD;&#xD;Actually there’s a better way that I call the “Learning Pyramid” which requires you establish a wide base of learning first and keep on building the upper layers on top of such a strong foundation. Each layer of this pyramid supports the more specialized layer established on top it.</description>
	</item>
	<item>
		<title>Unstoppability</title>
		<link>http://tc.eserver.org/34770.html</link>
		<guid>http://tc.eserver.org/34770.html</guid>
		<description>Unstoppability. What does that mean to you? To Tom Johnson, it&apos;s about leading a life with passion and engagement. In this guest blog post, Tom talks about unstoppability and how it applies to technical communication.</description>
	</item>
	<item>
		<title>What&apos;s New is Old Again</title>
		<link>http://tc.eserver.org/34707.html</link>
		<guid>http://tc.eserver.org/34707.html</guid>
		<description>Social networking and social media have been touted as giving us a never-before possible opportunity to connect with and influence and work with others. The board might be new, but the game is essentially the same.</description>
	</item>
	<item>
		<title>Technical Communication Trends and Ideas</title>
		<link>http://tc.eserver.org/34715.html</link>
		<guid>http://tc.eserver.org/34715.html</guid>
		<description>Technical Communication continues to change as we find new ways to meet the needs of our audiences. I have attended several conferences recently and discussed several of the latest trends with other technical communicators. This article provides a quick list of several of these trends and ideas.</description>
	</item>
	<item>
		<title>Sheep, Chaos, and User Experience</title>
		<link>http://tc.eserver.org/34705.html</link>
		<guid>http://tc.eserver.org/34705.html</guid>
		<description>The people who own the creation, collection, and distribution of content may not be the same people in the very near future. I also believe technical communication is part of information architecture and user experience design. While the technical communication community, specifically many STC members, also work in usability or information design, the culture of the user has changed faster than the culture within the tech comm community.</description>
	</item>
	<item>
		<title>This is the Future of Technical Communication</title>
		<link>http://tc.eserver.org/34695.html</link>
		<guid>http://tc.eserver.org/34695.html</guid>
		<description>In the absence of safety concerns, I think that accuracy must win. Thus, as the information curator, you have a responsibility to correct inaccurate information. If the inaccuracy is truly dangerous, you may need to edit the post directly. Make sure that you disclosure what you&apos;ve done with brackets.</description>
	</item>
	<item>
		<title>Lessons for Technical Communicators from the Telecommunications Sector</title>
		<link>http://tc.eserver.org/34698.html</link>
		<guid>http://tc.eserver.org/34698.html</guid>
		<description>It’s often useful to look at the economic and technological pressures in other industries, to see if the trends emerging there are relevant to the technical communications/publications sector. In recent Blogs, we’ve covered the issues emerging in education, but the telecommunications industry might also provide some useful insights.</description>
	</item>
	<item>
		<title>Bye Bye STC</title>
		<link>http://tc.eserver.org/34651.html</link>
		<guid>http://tc.eserver.org/34651.html</guid>
		<description>Perhaps the time has come to wrap up the STC and let a new organisation grow from the ashes. Those who are interested, and who believe our profession needs such an organisation will rally round and rebuild something. If there is not enough interest then perhaps that is a further indication that the STC has had its time.</description>
	</item>
	<item>
		<title>STC Floundering?</title>
		<link>http://tc.eserver.org/34636.html</link>
		<guid>http://tc.eserver.org/34636.html</guid>
		<description>It&apos;s been pretty clear over the last few months that the Society for Technical Communication (STC) is facing some hard times. Attendance at this year&apos;s conference was way down (below 1,000) and memberships, the other major source of revenue, are falling too. The STC has been sponsoring a series of webinars to discuss future directions and has acknowledged that unless they can turn things around, and quickly, the organization will run out of money in a couple of years.</description>
	</item>
	<item>
		<title>Lifelines to the STC</title>
		<link>http://tc.eserver.org/34625.html</link>
		<guid>http://tc.eserver.org/34625.html</guid>
		<description>In case you haven’t heard, the STC’s finances are facing crisis proportions. Unless membership stabilizes, it could go out of business in a couple of years. Here are a few recommendations to help solve the problems of the STC.</description>
	</item>
	<item>
		<title>In Which I Comment on the STC Issue</title>
		<link>http://tc.eserver.org/34626.html</link>
		<guid>http://tc.eserver.org/34626.html</guid>
		<description>STC represents two conflicting groups: academics and actual business world employees. These are complimentary roles for building theory but they are conflicting for actual execution.</description>
	</item>
	<item>
		<title>Whither STC?</title>
		<link>http://tc.eserver.org/34627.html</link>
		<guid>http://tc.eserver.org/34627.html</guid>
		<description>As you may have heard, STC is in a financial crisis. According to the board of directors meeting minutes from May 5, 2009, STC must retain membership &quot;for the next year or STC will be out of business in two years.&quot; I believe that STC needs to make some significant changes in the following areas.</description>
	</item>
	<item>
		<title>Does the STC Deserve to Survive?</title>
		<link>http://tc.eserver.org/34628.html</link>
		<guid>http://tc.eserver.org/34628.html</guid>
		<description>Recently, I have begun to feel that there is not much value left in STC as it stands today, and it is in need of a radical overhaul in order to survive. I believe that outside the rarefied atmosphere of the STC Board and Head Office, this view is widely shared.</description>
	</item>
	<item>
		<title>The STC Crisis: The Take of a &quot;Young&quot; Writer</title>
		<link>http://tc.eserver.org/34629.html</link>
		<guid>http://tc.eserver.org/34629.html</guid>
		<description>As  a “young” technical writer, I thought I might share some of my feelings on the STC crisis.&#xD;&#xD;First, a little background on me. I knew while I was in college that I wanted to be a technical writer after graduation. I switched to an English major for that purpose, and picked classes that gave me a “technical communication emphasis”. I joined STC while I was in college because I wanted to connect with people in my field. I got a chapter scholarship to attend a regional STC conference, and had a great time meeting people who did for a living what I was studying.</description>
	</item>
	<item>
		<title>STC International Technical Communication: Resources</title>
		<link>http://tc.eserver.org/34588.html</link>
		<guid>http://tc.eserver.org/34588.html</guid>
		<description>Includes articles contributed by STC members, some of whom have worked with translators extensively. Other contributors are affiliated with translation agencies.</description>
	</item>
	<item>
		<title>Words: A Quarterly Bulletin on Writing and Communication</title>
		<link>http://tc.eserver.org/34581.html</link>
		<guid>http://tc.eserver.org/34581.html</guid>
		<description>Words is a free, quarterly bulletin for technical writers and communicators—indeed, for anyone with a passion for words and for what you can do with them.&#xD;&#xD;Each issue of Words will include articles on language, authoring tools and authoring methodologies. Occasionally, other topics will be covered, such as document design, usability and audience profiling. There will also be reviews of books and software from time to time.</description>
	</item>
	<item>
		<title>The Twitter Book and Tech Comm</title>
		<link>http://tc.eserver.org/34543.html</link>
		<guid>http://tc.eserver.org/34543.html</guid>
		<description>The Twitter Book was created as being a different approach to publishing. But it’s also a different approach to writing. And that approach has definite applications in technical communication.&#xD;</description>
	</item>
	<item>
		<title>Dinosaurs, Gazelles, and the Need (or Not) for Organizations</title>
		<link>http://tc.eserver.org/34519.html</link>
		<guid>http://tc.eserver.org/34519.html</guid>
		<description>There was a time when organizations did offer a value proposition. Once upon a time, there was some prestige attached to being part of a professional organization. Being a member marked you as a professional. The potential was there for membership in an organization to open a more than a few doors. And organizations offered training, courses, information, and even pointers to jobs that you couldn’t find anywhere else. The Web, though, hasn’t just leveled the playing field. The Web has flattened the playing field, paved it over, and moved the goal posts.</description>
	</item>
	<item>
		<title>Technical Communication</title>
		<link>http://tc.eserver.org/34470.html</link>
		<guid>http://tc.eserver.org/34470.html</guid>
		<description>The term Technical Communication refers to the process of relaying technology-related information. Sciences, high technology, computers and electronics are a few of the types of technology that may be addressed.</description>
	</item>
	<item>
		<title>The Top Five Technical Writing Skills That Pay Big</title>
		<link>http://tc.eserver.org/34434.html</link>
		<guid>http://tc.eserver.org/34434.html</guid>
		<description>A technical writer is a professional writer who designs, writes, creates, maintains and updates technical documentation including online help, user guidance, white papers, design specifications, system manuals and other documents. A technical writer should possess good research techniques, good sound of language and excellent writing skills. Apart from this one needs to have the following five skills.</description>
	</item>
	<item>
		<title>STC Chicago</title>
		<link>http://tc.eserver.org/34409.html</link>
		<guid>http://tc.eserver.org/34409.html</guid>
		<description>The STC Chicago is an active local community, with frequent meetings and a collection of online articles and resources.</description>
	</item>
	<item>
		<title>Online Resources</title>
		<link>http://tc.eserver.org/34410.html</link>
		<guid>http://tc.eserver.org/34410.html</guid>
		<description>A collection on links to online resources of use to technical communicators.</description>
	</item>
	<item>
		<title>Technical Communicator Jobs</title>
		<link>http://tc.eserver.org/34372.html</link>
		<guid>http://tc.eserver.org/34372.html</guid>
		<description>When a company adds or removes a job from their site, we update ours — automatically. All jobs are collected directly from company websites, not &apos;pay-for&apos; job boards.</description>
	</item>
	<item>
		<title>Discussing Collaboration in Technical Communication</title>
		<link>http://tc.eserver.org/34373.html</link>
		<guid>http://tc.eserver.org/34373.html</guid>
		<description>Professionals use contextual collaboration most frequently. It includes two forms: genre use and document borrowing. Professionals use hierarchical collaboration in moderation. It includes two forms: author-centered and sequential. Professionals use group collaboration the least of all.</description>
	</item>
	<item>
		<title>The Future of Technical Communication: Remix</title>
		<link>http://tc.eserver.org/34344.html</link>
		<guid>http://tc.eserver.org/34344.html</guid>
		<description>In this follow-up piece to her 2004 article, Giammona explores the future of the industry and how technical communicators need to evolve to remain relevant and demonstrate their value.</description>
	</item>
	<item>
		<title>Bloom Wherever You’re Planted: A Different View on Fostering Career Longevity</title>
		<link>http://tc.eserver.org/34345.html</link>
		<guid>http://tc.eserver.org/34345.html</guid>
		<description>Potsus provides twelve tips on how to maintain your mental, spiritual, professional, and physical health in order to ensure you grow and flourish in your career, instead of wither away.</description>
	</item>
	<item>
		<title>Career Planning and Longevity for Technical Communicators</title>
		<link>http://tc.eserver.org/34346.html</link>
		<guid>http://tc.eserver.org/34346.html</guid>
		<description>Cooper discusses her unique approach to career planning and longevity: essentially, do what you enjoy doing and find people and companies that interest you.</description>
	</item>
	<item>
		<title>&quot;Telescoping&quot; to Survive This Recession</title>
		<link>http://tc.eserver.org/34353.html</link>
		<guid>http://tc.eserver.org/34353.html</guid>
		<description>“Telescoping,” or extending and adding to the range of services you provide, is one way to survive this recession, according to Frick.</description>
	</item>
	<item>
		<title>infotexture</title>
		<link>http://tc.eserver.org/34360.html</link>
		<guid>http://tc.eserver.org/34360.html</guid>
		<description>infotexture is the blog of an independent consultancy based in Potsdam, Germany with over 10 years of experience in technical documentation for information technology and telecommunications products.</description>
	</item>
	<item>
		<title>Twitter and Tech Communication</title>
		<link>http://tc.eserver.org/34263.html</link>
		<guid>http://tc.eserver.org/34263.html</guid>
		<description>Twitter can be a great tool, and can help people get answers quickly. However, when you have a question and need an answer, you probably ought to consider your question, and determine what channel is best suited for the type of answer you need. That may or may not be Twitter.</description>
	</item>
	<item>
		<title>Blogging: A New Role for Technical Communicators</title>
		<link>http://tc.eserver.org/34253.html</link>
		<guid>http://tc.eserver.org/34253.html</guid>
		<description>The online transition to web 2.0, with its proliferation of blogs, wikis, podcasts, tweets, and other user-generated content, has posed a question for the state of help content. Should help material concern itself with web 2.0? Do users want to interact and contribute to help content in the same way they contribute and interact with web content? What is the technical writer’s role in relation to new media?</description>
	</item>
	<item>
		<title>Cultural Contexts in Technical Communication:</title>
		<link>http://tc.eserver.org/34198.html</link>
		<guid>http://tc.eserver.org/34198.html</guid>
		<description>Explores how and why the German and Chinese cultures differ in the presentation and perception of technical information. Presents a theoretical framework for technical communication across different cultures. Provides guidelines to technical communicators in Sino-German technical communication and services.</description>
	</item>
	<item>
		<title>Analysis of the Skills Called for by Technical Communication Employers in Recruitment Postings</title>
		<link>http://tc.eserver.org/34199.html</link>
		<guid>http://tc.eserver.org/34199.html</guid>
		<description>Provides a framework of experiences and skills employers call for in job postings. Shows that potential employers are seeking very technical or domain-specific knowledge from technical writers. Shows that specific technology tool skills are less important to employers than more basic technical writing skills.</description>
	</item>
	<item>
		<title>CE 333T: Engineering Communication</title>
		<link>http://tc.eserver.org/34161.html</link>
		<guid>http://tc.eserver.org/34161.html</guid>
		<description>The principle objective of this course is to prepare you for all the communication activities you will engage in as a professional engineer, including various forms of writing, speaking, illustrating, collaborating, and presenting. Since an important part of engineering work is to disseminate the results of research and data collection, the course focuses on reports and presentations. But we also try to duplicate many of the conditions of the workplace, where you will often work with cross-functional teams on collaborative projects and where you will often be communicating to people who are NOT engineers.</description>
	</item>
	<item>
		<title>CE 389C: Advanced Engineering Communication</title>
		<link>http://tc.eserver.org/34162.html</link>
		<guid>http://tc.eserver.org/34162.html</guid>
		<description>This course offers engineering graduate students the opportunity to accomplish the following: communicate effectively with a variety of audiences; communicate effectively in several media: written, oral, visual; manage the process of collecting, synthesizing, and presenting data and information; manage the process of writing and publishing scholarly work; produce a portion of their thesis or dissertation or a complete scholarly paper.</description>
	</item>
	<item>
		<title>Defining a Body of Knowledge</title>
		<link>http://tc.eserver.org/34166.html</link>
		<guid>http://tc.eserver.org/34166.html</guid>
		<description>STC has meant a lot to my professional growth over the past 20+ years as a teacher and practitioner of technical communication, and I want to help STC expand its educational mission for all technical communicators. It is time our profession had a defined body of knowledge. Why?</description>
	</item>
	<item>
		<title>Professionalizing Plain Language: A Postcard on Current Developments</title>
		<link>http://tc.eserver.org/34130.html</link>
		<guid>http://tc.eserver.org/34130.html</guid>
		<description>With the passing of the Brayley Bill in Congress, the significance of plain language has become even more apparent to technical communicators. The author lays out a step-by-step plan to maintain the relevance of plain language as an important and necessary profession.</description>
	</item>
	<item>
		<title>South Korea Beckons: Global Awareness and Cultural Sensitivity Strategies for Western Technical Communicators</title>
		<link>http://tc.eserver.org/34131.html</link>
		<guid>http://tc.eserver.org/34131.html</guid>
		<description>As an Indian living in South Korea for the past few years, Rahul Prabhakar has had the opportunity to gain a unique perspective of global awareness and cultural sensitivity. In his article, he details the positive and negative aspects of living and working amidst a different culture.</description>
	</item>
	<item>
		<title>Turning User Experiences into Learning Experiences</title>
		<link>http://tc.eserver.org/34134.html</link>
		<guid>http://tc.eserver.org/34134.html</guid>
		<description>Savita Taylor talks about her journey from textile engineering to technical communication and beyond.</description>
	</item>
	<item>
		<title>Mapping the Research Questions in Technical Communication</title>
		<link>http://tc.eserver.org/34076.html</link>
		<guid>http://tc.eserver.org/34076.html</guid>
		<description>Agreement about research questions can strengthen disciplinary identity and give direction to a field that is still maturing. The central research question this article poses foregrounds texts, broadly defined as verbal, visual, and multimedia, and the power of texts to mediate knowledge, values, and action in a variety of contexts. Related questions concern disciplinarity, pedagogy, practice, and social change. These questions overlap and inform each other. Any single study does not necessarily fall exclusively into one area. A mapping of a field’s research questions is a political act, emphasizing some questions and marginalizing or excluding others. The emphases may change over time. This mapping illustrates reasons for the tensions between the academic and practitioner areas of the field. It also points out their shared research interests and opportunities for future research.</description>
	</item>
	<item>
		<title>Practitioner Research Instruction: A Neglected Curricular Area in Technical Communication Undergraduate Programs</title>
		<link>http://tc.eserver.org/34077.html</link>
		<guid>http://tc.eserver.org/34077.html</guid>
		<description>Most technical communication practitioners conduct research throughout &#xD;their careers. Yet, a survey of the Web sites of 114 undergraduate technical &#xD;communication programs between September 2006 and April 2007 revealed &#xD;that 65% (about two thirds) of these programs are providing minimal or no &#xD;exposure to research instruction and therefore are not sufficiently preparing &#xD;students to handle the types of research they will encounter in their upcoming &#xD;careers. Given the disconnect between the centrality of research in the work &#xD;that technical communicators do and the low presence of research instruction &#xD;at the undergraduate level, academics need to look for ways to overcome &#xD;institutional and other constraints in order to give research training greater &#xD;priority in their undergraduate programs.</description>
	</item>
	<item>
		<title>The Technical Communication Research Landscape</title>
		<link>http://tc.eserver.org/34079.html</link>
		<guid>http://tc.eserver.org/34079.html</guid>
		<description>This article reports data from questionnaires assessing the day-to-day experiences that members of the technical communication field have in carrying out their research. The data revealed that most members experience at least some frustration and numerous constraints that prevent them from doing the kinds and amounts of research that they want to do and that may affect the quality of their research. In short, technical communication scholars face an array of challenges. This article presents examples of these challenges and ideas that respondents had both for lessening the challenges scholars face and for better preparing graduate students. It suggests several practical initiatives for addressing these challenges along with realistic strategies for implementing those initiatives.</description>
	</item>
	<item>
		<title>Thriving on Ignorance</title>
		<link>http://tc.eserver.org/34064.html</link>
		<guid>http://tc.eserver.org/34064.html</guid>
		<description>A short blog post that discusses why users are more interested in learning how to, and not what is.</description>
	</item>
	<item>
		<title>Putting the Wrecking Ball to the User Interface (UI)</title>
		<link>http://tc.eserver.org/34065.html</link>
		<guid>http://tc.eserver.org/34065.html</guid>
		<description>Does a truly intuitive user interface exist? The author of this blog post doesn&apos;t think so. To create one, designers and developers really need to put the wrecking ball to the UI as it is now.</description>
	</item>
	<item>
		<title>Switching Niches, Redux</title>
		<link>http://tc.eserver.org/34069.html</link>
		<guid>http://tc.eserver.org/34069.html</guid>
		<description>Is it possible for a technical writer to switch niches and write something different? Here&apos;s an example of one person who&apos;s done just that.</description>
	</item>
	<item>
		<title>Technical Writing and Technical Communication As a Job and a Career - Is it For You?</title>
		<link>http://tc.eserver.org/34035.html</link>
		<guid>http://tc.eserver.org/34035.html</guid>
		<description>You might perhaps be considering whether to become a technical writer or not. You might be wondering: “What kind of a job technical writing is exactly and what does the future hold?” I can tell you right away that, at its most fundamental level, technical writing is safe and comfortable office work.</description>
	</item>
	<item>
		<title>Talking Tech with Newbies and Older Generations</title>
		<link>http://tc.eserver.org/33927.html</link>
		<guid>http://tc.eserver.org/33927.html</guid>
		<description>Tech newbies, and often these are people from an older generation than us techies, are easily overwhelmed by technology. Why do we expect them to get it? It&apos;s not their business to get it, it&apos;s our business to get it and then translate it to them. Do we think we are impressing them with all our knowledge? Chances are we are intimidating them. We need to stop, slow down and listen, ask questions, understand where they are coming from and then meet them where they are at. It isn&apos;t condescending or patronizing to slow things down and start with the basics.</description>
	</item>
	<item>
		<title>A Student&apos;s Interview on the Field of Technical Communication</title>
		<link>http://tc.eserver.org/33917.html</link>
		<guid>http://tc.eserver.org/33917.html</guid>
		<description>It is not often I’m contacted by a student to respond to an informational interview, so it was a pleasure when I was contacted early last week by a student in Eugene, Oregon USA to see if I would respond to his by email, and some great questions he had too. With the student’s permission, I’m posting the interview here in the event his questions reflect those of other students, whether in France or anywhere else.</description>
	</item>
	<item>
		<title>STC France Salary Survey</title>
		<link>http://tc.eserver.org/33919.html</link>
		<guid>http://tc.eserver.org/33919.html</guid>
		<description>The STC France Chapter has conducted several salary surveys among its members and non-members living and working in France. The most recent STC France salary survey was conducted in 2006. While these surveys cannot be considered statistically representative of the technical communication job market in France, they may be useful in exploring the value of experience, responsibilities, and skills and their influence on pay scales across the industry.</description>
	</item>
	<item>
		<title>Fundamentals of Business Process Documentation</title>
		<link>http://tc.eserver.org/33888.html</link>
		<guid>http://tc.eserver.org/33888.html</guid>
		<description>It is important to identify, understand, and evaluate key business processes to determine how effective they are in accomplishing the business goals of an organization. As a result, end-to-end business process documentation is increasingly becoming a significant initiative for many organizations. Essentially, process documentation should communicate the guidelines to support specific processes, and can be used by a wide range of business units, partners, process leaders, and anyone who is involved in these processes. Interviewing people who follow a business process is an effective method toward understanding how the business process is executed. While interviewing the right people to understand how they execute processes, it is essential that the writers look beyond just recording what they are told about the process. Handling situations like these also provide opportunities for the writers to evolve to business domain analysts or subject matter experts</description>
	</item>
	<item>
		<title>Palimpsest </title>
		<link>http://tc.eserver.org/33746.html</link>
		<guid>http://tc.eserver.org/33746.html</guid>
		<description>A blog about publishing and technical communications.</description>
	</item>
	<item>
		<title>Creating an Online Survey with SurveyMonkey</title>
		<link>http://tc.eserver.org/33712.html</link>
		<guid>http://tc.eserver.org/33712.html</guid>
		<description>Surveys have always been a great way to gauge users&apos; opinions and reactions toward new and existing products and services. With SurveyMonkey, an online survey software program, creating a survey has become a quick and easy way to create useful surveys for a multitude of needs. In this reprint of David Farbey&apos;s article, originally published in the January 2006 edition of Forward, the newsletter of the UK Chapter, Farbey gives a step-by-step guide on creating a survey with SurveyMonkey.</description>
	</item>
	<item>
		<title>Age 50+ Persona for the STC Body of Knowledge</title>
		<link>http://tc.eserver.org/33713.html</link>
		<guid>http://tc.eserver.org/33713.html</guid>
		<description>Many STC members have contributed to the Body of Knowledge and as the endeavor continues, the more important it becomes to gain many perspectives and ideas from all across the STC membership. SIGs have unique angles for their contributions. Lori Gillen, co-manager of the AccessAbility SIG, contributed this persona for use by the BOK. This persona illustrates pertinent accessibility issues that a body of knowledge for technical communicators should encompass.</description>
	</item>
	<item>
		<title>Breaking Traditions and Taking Risks</title>
		<link>http://tc.eserver.org/33714.html</link>
		<guid>http://tc.eserver.org/33714.html</guid>
		<description>Innovation is important in any area of life, and STC communities are no exception. Last year, STC Chicago and STC-NIU (Northern Illinois University) combined their strengths to facilitate innovation and to help revive a student chapter.</description>
	</item>
	<item>
		<title>Subjectivism vs. Empiricism―How Does the Conflict Play Out in Technical Communication?</title>
		<link>http://tc.eserver.org/33697.html</link>
		<guid>http://tc.eserver.org/33697.html</guid>
		<description>A large number of scholars in technical communication advocate stances that rely more on qualitative methods often associated with more subjectivist research paradigms that seem to acknowledge Foucault’s notion of the episteme with its inherent social and power relations as determining factors in epistemology. Fewer scholars, mostly in textbooks, embrace the scientific method or a variation thereof. However, several scholars attempt to alert us to the benefits of a more varied approach that takes advantage of methods within empiricism to give our field credence and add validity to our research. In summary, I found a continuum of approaches. This continuum, however, is not evenly populated; it appears slanted towards more subjectivist theory and methodology and much more sparsely populated in the realm of empiricist theory.</description>
	</item>
	<item>
		<title>TWIN eBook Volume 1</title>
		<link>http://tc.eserver.org/33698.html</link>
		<guid>http://tc.eserver.org/33698.html</guid>
		<description>A compilation of some of the useful messages posted on TWIN from 1997 through 2002, in Microsoft CHM format (for some reason). These messages are classified into different topic areas, such as Tools, Career-Related, Best Practices, Grammar, etc.</description>
	</item>
	<item>
		<title>Convergence Technical Communication: Strategies for Incorporating Web 2.0</title>
		<link>http://tc.eserver.org/33641.html</link>
		<guid>http://tc.eserver.org/33641.html</guid>
		<description>&quot;Convergence Technical Communication&quot; (CTC) is technical communication that provides information in several forms, including Web 2.0 delivery mechanisms, to improve the user experience. Most of the content is generated by technical communicators; a portion by users.&#xD;&#xD;Web 2.0 makes it possible to create additional deliverables that enhance the user experience several different ways. First, it engages the different learning styles of our audience. Second, it improves user satisfaction with your product by creating communities of practice that allow users to participate in the conversation. Finally, any feedback and suggestions obtained can be used to improve the core deliverable set.</description>
	</item>
	<item>
		<title>Embracing the Un: When the Community Runs the Event</title>
		<link>http://tc.eserver.org/33643.html</link>
		<guid>http://tc.eserver.org/33643.html</guid>
		<description>With the explosion of Web 2.0 come two new kinds of community events: BarCamps and BookSprints. Gentle and Swisher share their experiences with these unconferences.</description>
	</item>
	<item>
		<title>Jazzing It Up in the Emerald City</title>
		<link>http://tc.eserver.org/33648.html</link>
		<guid>http://tc.eserver.org/33648.html</guid>
		<description>According to STC member and jazz musician Matso Limtiaco, there are many similarities between technical communication and musical composition.</description>
	</item>
	<item>
		<title>Tech Comm Toolbox</title>
		<link>http://tc.eserver.org/33633.html</link>
		<guid>http://tc.eserver.org/33633.html</guid>
		<description>Many people will answer that you need to look at the different tools, download trial versions, and test. But where is the list of tools to choose from? It’s here at TechComm Toolbox, your online resource for all applications, services, and consultants related to technical communication.</description>
	</item>
	<item>
		<title>The WritersUA 2008 Skills and Technologies Survey</title>
		<link>http://tc.eserver.org/33623.html</link>
		<guid>http://tc.eserver.org/33623.html</guid>
		<description>There is no question that the software development world offers a lot of excitement and challenging work. In the area of software user assistance we are particularly challenged by having to master a wide range of disciplines. From foundation skills like writing and editing—to the coding of content—to usability testing and user interface design, we find ourselves in a profession that is difficult to define. What is it that we really do? The objective of this survey is to take a snapshot of our collective professional life in an attempt to identify what we value in our daily work as user assistance professionals.</description>
	</item>
	<item>
		<title>Predicting Technical Communication in Product Development Organizations</title>
		<link>http://tc.eserver.org/33577.html</link>
		<guid>http://tc.eserver.org/33577.html</guid>
		<description>This work explores prediction of technical communication patterns within product development organizations. Our methodology involves first predicting the patterns of communication and then measuring the actual communications to see if the anticipated linkages are realized. We applied this methodology to a commercial product development project in the electronics industry. In this case study we found that: 81% of all coordination type communication linkages were predicted in advance; occurrences of frequent communications were more accurately predicted than infrequent communications; and two-way communication exchange was most often observed, even where oneway information transfer was predicted. For the management of product development projects, these results imply that certain aspects of organizational design can be planned by anticipating the technical communication linkages required for project execution. Finally, a critical analysis of our methodology suggests improvements for future work.</description>
	</item>
	<item>
		<title>Technical Communication Degrees for the 21st Century</title>
		<link>http://tc.eserver.org/33578.html</link>
		<guid>http://tc.eserver.org/33578.html</guid>
		<description>The practice of technical communication, especially for professionals just entering the workplace, is rapidly changing. Companies have higher expectations for degrees in technical communication, a strong foundation in technology, and the ability to function on cross-disciplinary teams alongside technical experts in the design and development process. As the practice of technical communication shifts its focus, academics have the responsibility to be certain that technical communication degree programs have a strong component of such topics as engineering design, programming, human factors, usability, instructional design, and project management, in addition to traditional communication skills. Academic programs have lagged behind practice, largely due to the location of degree programs, departmental reward systems, faculty deficiencies in technology, little depth in fields beyond rhetoric, and lack of exposure to best industry practices. This paper addresses these issues and makes some practical recommendations for catching academe up to practice.</description>
	</item>
	<item>
		<title>Categorizing Professional Discourse: Engineering, Administrative, and Technical/Professional Writing</title>
		<link>http://tc.eserver.org/33579.html</link>
		<guid>http://tc.eserver.org/33579.html</guid>
		<description>Rhetorical categories can and should be developed by scholars of professional writing to identify how values held within professions constrain the ways discourse is interpreted in organizational settings. Empirical research (conducted by the author and others), discourse theory, and pedagogical practice in professional writing strongly suggest that at least three categories of professional writing exist: engineering, administrative, and technical/professional writing. The author demonstrates this claim and distinguishes the characteristics of these three categories. Engineering writing is shown to respond to professional values of scientific objectivity and professional judgment as well as to corporate interests. Administrative writing reflects the locus of decision-making authority and promotes institutional identity. Technical/professional writing aims to accommodate audience needs through complying with professional readability standards. Future research should focus on defining the characteristics of these varieties more precisely. Articulated definitions of these three varieties of professional writing can help scholars and practitioners better understand how discourse is framed and interpreted in organizational settings.</description>
	</item>
	<item>
		<title>Feminist Theory and the Redefinition of Technical Communication</title>
		<link>http://tc.eserver.org/33580.html</link>
		<guid>http://tc.eserver.org/33580.html</guid>
		<description>To study the possible impact of feminist theory on technical communication, this article discusses six common characteristics of feminist theory: (a) celebration of difference, (b) impact on social change, (c) acknowledgment of scholars&apos; backgrounds and values, (d) inclusion of women&apos;s experience, (e) study of gaps and silences in traditional scholarship, and (f) new female sources of knowledge. Three debates within feminist theory spring out of these common characteristics: whether to stress similarity or difference between the sexes, whether differences come from biological or social forces, and whether feminist scholars can avoid reinforcing binary opposition. The article then traces the impact of these characteristics of feminist theory and debates within feminist theory on the redefinition of technical communication in terms of the myth of scientific objectivity, the new interest in ethnographic studies of workplace communication, and the recent focus on collaborative writing.</description>
	</item>
	<item>
		<title>Relocating the Value of Work: Technical Communication in a Post-Industrial Age</title>
		<link>http://tc.eserver.org/33561.html</link>
		<guid>http://tc.eserver.org/33561.html</guid>
		<description>This article analyzes the location of “value” in technical communication contexts, arguing that current models of technical communication embrace an outdated, self-deprecating, industrial approach subordinating information to concrete technological products. By rethinking technical communication in terms of Reich&apos;s “symbolic-analytic work”, technical communicators and educators can move into a post-industrial model of work that prioritizes information and communication, with benefits to both technical communicators and users.</description>
	</item>
	<item>
		<title>The Impact of the Internet and Digital Technologies on Teaching and Research in Technical Communication</title>
		<link>http://tc.eserver.org/33562.html</link>
		<guid>http://tc.eserver.org/33562.html</guid>
		<description>Technical communication practices have been changed dramatically by the increasingly ubiquitous nature of digital technologies. Yet, while those who work in the profession have been living through this dramatic change, our academic discipline has been moving at a slower pace, at times appearing quite unsure about how to proceed. This article focuses on the following three areas of opportunity for change in our discipline in relation to digital technologies: access and expectations, scholarship and community building, and accountability and partnering.</description>
	</item>
	<item>
		<title>A Laboratory in Citizenship: Service Learning in the Technical Communication Classroom</title>
		<link>http://tc.eserver.org/33563.html</link>
		<guid>http://tc.eserver.org/33563.html</guid>
		<description>This article presents an argument for and offers illustrations of service learning in technical communication courses and curricula. Alongside traditional internships that prepare students as future employees, service learning provides students with an education in engaged citizenship. This article reviews service-learning literature, discussing specifically the advantages of projects to students, faculty, and the community. The authors also describe three projects in which instructors and students integrated service learning and technical communication in innovative ways.</description>
	</item>
	<item>
		<title>The Process and Prospects for Professionalizing Technical Communication</title>
		<link>http://tc.eserver.org/33564.html</link>
		<guid>http://tc.eserver.org/33564.html</guid>
		<description>Despite claims for at least the past quarter century of mature professional status for the field of technical communication, studies in the history and sociology of the professions provide criteria that suggest we are not yet truly a profession. This article reviews economic, sociopolitical, and ideological factors that characterize the modern professions and argues that the technical communication field, at best, only partially meets the criteria. The prospects for professional status of technical communication might be improved by developing a critical consciousness of the processes of professionalization and concertedly acting in ways that facilitate those processes.</description>
	</item>
	<item>
		<title>Sketching a Framework for Graduate Education in Technical Communication</title>
		<link>http://tc.eserver.org/33566.html</link>
		<guid>http://tc.eserver.org/33566.html</guid>
		<description>Graduate education in technical communication should provide students with an expansive view of the field. Toward that end, we offer a three-dimensional framework that represents technical communication as a robust, diverse, complex whole. Although the framework aims towards coherence, it embraces contradiction. That is, the framework represents a totality but does not purport to be the only possible representation. Key to the framework is our belief that the gap between theory and practice can actually be productive. Almost all binaries encourage overly simplistic understandings. But we should not allow the goal of remediating the binary to close off the important tensions that can allow the field to advance. This very gap is actually one of the few sites in which new ideas and approaches can be forged.</description>
	</item>
	<item>
		<title>Winning as a Tech Writer</title>
		<link>http://tc.eserver.org/33462.html</link>
		<guid>http://tc.eserver.org/33462.html</guid>
		<description>If you need a job, then you might look for companies that have never had a professional technical writer working for them. It may require making calls or networking with friends or former co-workers. Most companies have a ton of writing to do. Usually they put off their documentation requirements and their needs have piled up. You may also find that someone such as a regulator has confronted management about insufficient documentation and they have to put a writer to work immediately.</description>
	</item>
	<item>
		<title>Interview with the Creator of the EServer TC Library</title>
		<link>http://tc.eserver.org/33380.html</link>
		<guid>http://tc.eserver.org/33380.html</guid>
		<description>Tom Johnson has an interview the site&apos;s creator, Geoff Sauer, who explains some of the details behind the site. I found the discussion of their taxonomy particularly interesting, as it&apos;s a problem I&apos;ve struggled with in my own site.</description>
	</item>
	<item>
		<title>Mentoring Another Writer</title>
		<link>http://tc.eserver.org/33320.html</link>
		<guid>http://tc.eserver.org/33320.html</guid>
		<description>Some thoughts on what it takes to effectively mentor another technical communicator.</description>
	</item>
	<item>
		<title>EServer TC Library: The Most Popular Technical Communication Website in the World</title>
		<link>http://tc.eserver.org/33323.html</link>
		<guid>http://tc.eserver.org/33323.html</guid>
		<description>The EServer TC Library dwarfs all other tech comm sites. Granted, EServer TC Library is a library, which people primarily use to browse content located elsewhere, so it’s perhaps not in the same category as the other sites. Still, the sheer amount of traffic is impressive. I caught up with Geoffrey Sauer, the creator of the EServer TC Library, and chatted with him over email.</description>
	</item>
	<item>
		<title>The Yellow Brick Road to Technical Communication</title>
		<link>http://tc.eserver.org/33327.html</link>
		<guid>http://tc.eserver.org/33327.html</guid>
		<description>For those of us who communicate technical content for a living, we share many job titles, such as technical writer, information developer, technical communicator, multimedia engineer, content developer, and many others.  Without one focused set of titles, how did we know this is what we wanted to do?</description>
	</item>
	<item>
		<title>A. Stanley Higgins and the History of STC&apos;s Journal</title>
		<link>http://tc.eserver.org/33302.html</link>
		<guid>http://tc.eserver.org/33302.html</guid>
		<description>A profile of Stan Higgins, one of the first editors of STC&apos;s journal. Based on archival research and an interview with Higgins. Includes a table of journal titles (e.g., TWE Journal, STWE Review) and names of editors.</description>
	</item>
	<item>
		<title>Transitioning from Literary Studies to Technical Communication</title>
		<link>http://tc.eserver.org/33286.html</link>
		<guid>http://tc.eserver.org/33286.html</guid>
		<description>A 250 page manual for a complicated product may be more difficult to write than a master’s thesis. It may require a massive amount of deductive and inductive logic, as you try to figure out how the product works. You may spend months interviewing subject matter experts, asking them hundreds of questions about how the product functions, and then hundreds more to clarify their cryptic answers.</description>
	</item>
	<item>
		<title>STC Northeast Ohio</title>
		<link>http://tc.eserver.org/33211.html</link>
		<guid>http://tc.eserver.org/33211.html</guid>
		<description>A community of hundreds of technical and professional writers, editors and illustrators from around Cleveland, Akron-Canton, Youngstown and Ashtabula who exchange ideas and feelings about their careers.</description>
	</item>
	<item>
		<title>Becoming a Technical Communicator </title>
		<link>http://tc.eserver.org/33169.html</link>
		<guid>http://tc.eserver.org/33169.html</guid>
		<description>Thinking of a career in technical communication? This article offers one point of view on what you need to know to be successful in the field. </description>
	</item>
	<item>
		<title>Is Communications Up to Job of Running Intranet?</title>
		<link>http://tc.eserver.org/33077.html</link>
		<guid>http://tc.eserver.org/33077.html</guid>
		<description>The natural home of the intranet is in communications. However, intranet management requires particular skills that many traditional communications departments don’t have.</description>
	</item>
	<item>
		<title>A Technical Speaking Course in Mathematics</title>
		<link>http://tc.eserver.org/32786.html</link>
		<guid>http://tc.eserver.org/32786.html</guid>
		<description>Development and Implementation of a Technical Speaking Course in Mathematics, will give students an opportunity to cultivate technical, discipline-specific, verbal communication skills and experiences needed to be successful in their chosen disciplines. They will develop skills in assessing an audience’s technical sophistication and adapting their own communications to accommodate the audience. Mathematics will become a familiar “vehicle” for development of general and technical communication competencies.</description>
	</item>
	<item>
		<title>DITA and the Technical Communicator</title>
		<link>http://tc.eserver.org/32793.html</link>
		<guid>http://tc.eserver.org/32793.html</guid>
		<description>How will DITA conversion affect your work? Sigman shares what she&apos;s learned from her own survey of technical communicators.</description>
	</item>
	<item>
		<title>Ethics Case: The Engineered Résumé</title>
		<link>http://tc.eserver.org/32796.html</link>
		<guid>http://tc.eserver.org/32796.html</guid>
		<description>A proposal specialist must decide whether to pursue more information about a new coworker whom she has reason to suspect was dishonest during the hiring process.</description>
	</item>
	<item>
		<title>STC Eastern Ontario: Links</title>
		<link>http://tc.eserver.org/32808.html</link>
		<guid>http://tc.eserver.org/32808.html</guid>
		<description>A collection of links to technical communication resources online, maintained by the STC Eastern Ontario community.</description>
	</item>
	<item>
		<title>Talking Shop with Anne Gentle</title>
		<link>http://tc.eserver.org/32784.html</link>
		<guid>http://tc.eserver.org/32784.html</guid>
		<description>A chat with technical communicator and blogger Anne Gentle in which we discuss wikis, DITA, the XO Laptop, documenting Open Source software, and a lot more.</description>
	</item>
	<item>
		<title>Four More Reasons Your Company Needs Technical Communicators</title>
		<link>http://tc.eserver.org/32764.html</link>
		<guid>http://tc.eserver.org/32764.html</guid>
		<description>A few months ago I posted seven reasons an organization needs technical communicators. This week, a program manager I work with provided a few more ways that technical writers provide value to organizations and projects, so I wanted to pass along his wisdom—with my own discussion, of course. Because I gave seven reasons before, I’ll start with number eight.</description>
	</item>
	<item>
		<title>Seven Reasons Your Company Needs a Technical Communicator</title>
		<link>http://tc.eserver.org/32765.html</link>
		<guid>http://tc.eserver.org/32765.html</guid>
		<description>If you&apos;re in the business of developing and selling products that are in any way technical in nature, you probably spend most of your time planning or implementing specifications, development and release schedules, budgets, and engineering strategies. Or you may be directly involved in the day-to-day development and testing of the product. Whatever your role, the product is the most important thing.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/TC.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>