<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>NCTE TETYC</title>	<link>http://tc.eserver.org/publisher/NCTE_TETYC</link>
	<description>A listing of works published by NCTE TETYC 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>NCTE TETYC</title>
		<link>http://tc.eserver.org/dir/NCTE_TETYC</link>
	</image>
	<item>
		<title>The Professional Email Assignment </title>
		<link>http://tc.eserver.org/28829.html</link>
		<guid>http://tc.eserver.org/28829.html</guid>
		<description>As the semester&apos;s first assignment in a first-year writing course, I have used the professional e-mail assignment for several years in both face-to-face (f2f) and virtual classes, and have experienced great success as well as positive feedback from students. I have also shared this assignment with colleagues who have remarked on the value of critically thinking about e-mail since the genre cuts across every class, every discipline, and almost all employment and home situations. The assignment also sets the tone for all of my assignments because it fits within my pedagogical/theoretical framework, incorporating three important principles: community, critical engagement, and application (Digital 231). As with all of my assignments, this one has a theoretical underpinning, is framed by readings, is distributed to students via a written document that itself serves as &apos;good writing,&apos; provides scaffolding for later assignments, and emphasizes digital literacies that are crucial if students are to be engaged and empowered citizens.</description>
	</item>
	<item>
		<title>Grease on the Keyboard: Making Composition Work in a Technical College</title>
		<link>http://tc.eserver.org/14975.html</link>
		<guid>http://tc.eserver.org/14975.html</guid>
		<description>Times have changed. The industrial age has become the information age, and technology and equipment evolve at such a rapid pace that it is wasteful to train a person for only specific psychomotor skills. Employers are calling for the hands-on training to be combined with more communication and critical thinking skills so that employees have a broader education that allows them to switch speeds or tasks.</description>
	</item>
	<item>
		<title>Collaborative Projects in a Technical Writing Class: A Cost/Benefit Analysis</title>
		<link>http://tc.eserver.org/14043.html</link>
		<guid>http://tc.eserver.org/14043.html</guid>
		<description>With the shift in writing pedagogy from&#xD;product to process, from emphasizing the&#xD;individual writing--in a vacuum--to emphasizing&#xD;the social context and social&#xD;nature of writing, collaboration of some&#xD;sort has found a place in most writing&#xD;classes. The inclusion of collaborative&#xD;projects in technical writing courses has&#xD;a second, practical justification: the idea&#xD;that these courses should prepare students for writing on the job, where collaborative writing is common.</description>
	</item>
	<item>
		<title>Teaching about Plagiarism in the Age of the Internet</title>
		<link>http://tc.eserver.org/14044.html</link>
		<guid>http://tc.eserver.org/14044.html</guid>
		<description>Things have changed since I began teaching research writing ten years ago. I used&#xD;to require students to use at least one electronic source; now, I require that students use at least one paper source. Students used to start their search at the card catalog; now they log onto the Internet. Of course, the change has been gradual, but I have begun to ask what this shift from paper to electronic sources means to academic integrity.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/NCTE_TETYC.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>