DOCSLIB.ORG

The Engineers' Guide to Technical Writing: Insights for Budding

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Engineers' Guide to Technical Writing: Insights for Budding Advances in Language and Literary Studies ISSN: 2203-4714 www.alls.aiac.org.au The Engineers’ Guide to Technical Writing: Insights for Budding Engineers Abdul Wadood Khan* Department of English Language and Translation , College of Languages and Translation, King Saud University, Riyadh, Saudi Arabia Corresponding Author: Abdul Wadood Khan, E-mail: [email protected] ARTICLE INFO ABSTRACT Article history Engineers, being hands-on experts, need to produce technical documents that are convincing to Received: March 12, 2019 colleagues, executives, and clients. This study analyzes different technical documents written by Accepted: June 18, 2019 engineers and offers instruction on how to approach the task of technical writing. The quantitative Published: August 31, 2019 part of the study involved gathering statistics on the types of documents most frequently written Volume: 10 Issue: 4 by engineers and the importance engineers assign to technical writing in their career. The study Advance access: July 2019 participants consisted of 60 engineers selected through a snowball sampling method. Data was collected through the use of a questionnaire. The results of the data are presented in frequencies and percentages. An analysis of the data reveals that engineers currently practicing in Saudi Conflicts of interest: None Arabia believe writing to be important in their field. In total, 66.7% believe writing to be “very Funding: None important,” whereas the remaining 33.3% believe it to be “important”; none of the respondents believe writing to be only “slightly important” or “not important.” When asked whether their background education in the engineering field adequately prepared them for writing on the job, Key words: only 30 (50%) were confident of their writing abilities following their engineering degrees. The Engineering Students, other 30 (50%), although they found their skills in technical writing to be useful, were not confident ESP, of its adequacy in the workplace. Given the option of selecting more than one answer, respondents Practicing Engineers, recorded the following frequencies for the type of writing they usually do at work: 40 out of 60 Report-writing, respondents (6.7%) stated that they frequently write interim or progress reports; 30 (50%) stated Technical Writing for Engineers that they write final or recommendation reports. However, only 10 (16.7%) of the respondents revealed that they often write more focused reports, such laboratory reports. Engineers also write a fair number of non-report documents, including memos, emails, and logbook entries. INTRODUCTION their main subjects, which are technical in nature, they fail Globalization has introduced the imperative of adopting a to give much time to language studies because they deem common tool of effective communication that can be used it less important. Hence, they fail to improve their writing. across the world without any ambiguity or misperception. In Admittedly, writing can be difficult for engineering students, response to this need, numerous countries, including Saudi and the strict nature of technical writing makes it a daunting Arabia, have adopted English as a foreign language (EFL) for task. However, the ability to communicate ideas effectively the purpose of operational interaction. Practicing engineers in a document is not just an added advantage but a necessity. are very clear about the importance to their productiveness In addition to studying English, it is imperative that engi- in the engineering industry of developing a comprehensive neers study the essential structure of technical documents if understanding of the English language. Every profession has they are to succeed in technical writing. Practicing engineers its own form of specialized writing. Inasmuch as they are have revealed how important the knowledge of technical hands-on experts, engineers need to develop documents that writing is to their careers (Abed and Ibrahim, 2017). are clear and convincing not only to their colleagues, but to clients as well. Technical documents written by engineers Purpose of the Study need to communicate with their audiences. As a result, it is important to consider the audience when planning, writing, A large number of studies exist on teaching technical writ- and reviewing a technical document. ing to engineering students. This study takes a theoretical It is important to keep in mind that a technical document approach, in that it analyzes the different kinds of techni- is different from a general document, especially as regards cal document used in the engineering field as a preparation its objectives and its audience. Many engineering students for interpreting the responses of practicing engineers to a are not interested in taking courses in academic or tech- questionnaire about technical writing in the workplace. The nical writing; they find the task too cumbersome and too theoretical framework of the study presents useful insights detail-specific. While many engineering students focus on on how to tackle the task of technical writing and provides Published by Australian International Academic Centre PTY.LTD. Copyright (c) the author(s). This is an open access article under CC BY license (https://creativecommons.org/licenses/by/4.0/) http://dx.doi.org/10.7575/aiac.alls.v.10n.4p.80 The Engineers’ Guide to Technical Writing: Insights for Budding Engineers 81 tips for budding engineers as well as teachers. Further, the Colleagues: A solution or technical intervention is study collates the opinion of engineers practicing in Saudi generally designed in collaboration with a colleague or a Arabia concerning writing in the engineering field. Overall, team of colleagues. Engineers have a great deal of technical the study seeks to answer the following research questions: knowledge about the topic under discussion (for example, a 1. How important is technical writing in the field of engi- solution that has been devised), and they are familiar with neering? industry terminology. Still, a well-organized document goes 2. What kinds of technical documents do engineers write a long way in lending clarity to the topic being discussed. at work? When reading a technical document, the reader wants 3. Does an engineering degree adequately prepare engi- absolute certainty that the writer has knowledge of the top- neers for writing in their career? ic under consideration. A technical document should aim to 4. What advice can practicing engineers give to budding achieve the following goals: engineers on writing in the engineering field? • Demonstrate familiarity with the problem: To create credibility, the document needs to present a clear view of the problem in question form. This will help convince THEORETICAL FRAMEWORK readers that the engineer-author understands the prob- The Audience for Technical Engineering Documents lem and will help them gain a better understanding of the problem themselves. Only when the problem is un- Ignoring the audience could well be the biggest communi- derstood can a solution be proposed. A project’s preex- cation mistake an engineer can make, as different types of isting conditions should be discussed from all relevant documents are intended for different readers. To communi- viewpoints. Here is an instance of a problem descrip- cate effectively, an engineer must know the audience well tion, offered by the researcher: in terms of their knowledge of the field and relationship to The houses in Laban Valley have existed for more the business concern as well as their purpose in reading the than two centuries. However, the rate of collapse content. of houses in that region in recent times has been a Clients: When writing for clients, engineers are essen- cause of worry: four houses collapsed due to heavy tially writing as engineering consultants. Documents writ- downpour and flash floods in 2017; a further ten ten for clients need to exhibit perfect clarity, as they usually houses caught fire on the afternoon of 4 September present a solution to a particular problem. As a result, phras- 2018 because of being close together. Houses built es such as “maybe this can help” and “this sounds like a in that era tend to be close by … great idea” should be avoided. Clients look for statements As demonstrated in this example, the document should that convey certainty, with some level of guarantee. It is in first discuss and analyze the problem; only then can the read- order to achieve such certainty that they seek out an engi- er perceive a solution. The discussion of the problem estab- neering consultant in the first place. Clients hire engineer- lishes the expertise and competence of the engineer. ing consultants to analyze situations and present solutions • Solution: The engineering field is steeped in mathe- to specific problems; they expect to be able to make deci- matics. It is important to display results alongside sta- sions based on the engineer’s recommendations (Carlowicz, tistics and simple mathematical expressions, adjusting 2005). Engineers can improve their writing greatly by keep- the level of complexity to the audience of the document ing the level of the audience in mind and making sure that (Caponi et al., 2018). Solutions should not be merely they understand the text well. explained. Without statistics and data to fall back on, Executive or Government Officials: When writing a reader (e.g. an executive or official) is less likely to technical documents for submission to government officials adopt the solution proposed or formulate
Load more

Recommended publications
  • Experiences with Technical Writing Pedagogy Within a Mechanical Engineering Curriculum
    Session 1141 Learning To Write: Experiences with Technical Writing Pedagogy Within a Mechanical Engineering Curriculum Beth Daniell1, Richard Figliola2, David Moline2, and Art Young1 1Department of English 2Department of Mechanical Engineering Clemson University, Clemson, SC 29631 Abstract This case study draws from a recent experience in which we critically reviewed our efforts of teaching technical writing within our undergraduate laboratories. We address the questions: “What do we want to accomplish?” and “So how might we do this effectively and efficiently?” As part of Clemson University's Writing-Across-The-Curriculum Program, English department consultants worked with Mechanical Engineering faculty and graduate assistants on technical writing pedagogy. We report on audience, genre, and conventions as important issues in lab reports and have recommended specific strategies across the program for improvements. Introduction Pedagogical questions continue about the content, feedback and methodology of the technical laboratory writing experience in engineering programs. In fact, there is no known prescription for success, and different programs try different approaches. Some programs delegate primary technical writing instruction to campus English departments, while others maintain such instruction within the engineering department, and hybrids in-between exist. But the approaches seem as much driven by financial necessity and numbers efficiency as they are by pedagogical effectiveness. While better-heeled departments can employ technically trained writing specialists to tutor students individually, the overwhelming majority of engineers are trained at quality institutions whose available resources require other methods. So how can we do this effectively and efficiently? At the heart of the matter is the question, “What do we want to accomplish?” We find ourselves trying to accomplish two instructional tasks that are often competing and we suspect that we are not alone.
    [Show full text]
  • Technical Writing
    A Guide to Estimating Writing Projects Technical Writing Project Task Description Time Estimate Notes End User Guide Research, prepare, interview, write, graphics prep, screen 3-5 hours per page Assumes an average user guide (20-80 pages) of moderate r (e.g., software captures, index. complexity. Availability of existing style guide, SME’s and user manual) source docs will significantly impact time. Online Help Interview, design/layout, write, illustrate/graphics, revise and 3-6 hours per page Consider one page as one help screen. Technical complexity final link verification. and availability of SME’s and source docs are usually the gov- erning factors. Hours per page should be significantly less if help is prepared from an established paper-based user guide. Technical Reference Interview developers/programmers, write, graphic design, 5-9 hours per page Assumes a standard or established format and outline for Material screen captures, flowchart prep, edit, index. the document. Other variables include quantity and quality r (e.g., system of printed source materials, availability of SME’s and time documentation) involved with system or project. Operator’s Manual Interview users/operators to determine product purpose, New Product: Assumes standard/established boilerplate/template format r (e.g., equipment/ functionality, safety considerations, (if applicable) and operat- 3-5 hours per page - factor extra time (10 hours) to design template if none exist. product operation) ing steps. Write, screen capture, graphic design, (photographs, SME’s must be available and have advanced familiarity with if applicable), edit, index. Existing Product product. Rewrite: 1-4 hours per page Procedure Manual Interview users to determine purpose and procedures.
    [Show full text]
  • Healthcare Technical Writer for Interactive Software
    Healthcare Technical Writer for Interactive Software ABOUT US We are looking for an outstanding Medical/Technical writer to create highly engaging, interactive health applications. If you are looking to make your mark in a small but a fast-moving health technology company with a position that has autonomy and variety, you could really shine here. For most of our 15 years, Medicom Health Interactive created award-winning educational/marketing software tools for healthcare clients like Novo Nordisk, Novartis, Pfizer, GSK, the NCI, the ADA, and the AHA. Several years ago, we pivoted the company to focus exclusively on our patient engagement products. These products help top-tier healthcare systems with outreach/awareness to new patients. Visit www.medicomhealth.com for more detail. In 3 of the last 4 years, we have earned Minnesota Business Magazine’s “100 Best Companies To Work For” award, and have previously been named to the Minneapolis/St. Paul Business Journal’s “Fast 50” list of Minnesota’s fastest growing companies. Many of our staff have been here 5, 10, and 15 years. We have recently completed our first capital raise and are poised for additional growth. We pride ourselves on the quality of our work, adaptability, independence, cooperation, and a diverse mix of analytical and creative skills. We are seeking candidates who share these values. POSITION OVERVIEW The Healthcare Technical Writer documents the content and logic (no coding or graphic design) for our new and existing health/wellness web applications. This position is responsible for creating and maintaining the content and documentation of our interactive products in collaboration with our UI/UX specialists and Software Applications Developers.
    [Show full text]
  • Technical Documentation Style Guide
    KSC-DF-107 Revision F TECHNICAL DOCUMENTATION STYLE GUIDE July 8, 2017 Engineering Directorate National Aeronautics and Space Administration John F. Kennedy Space Center KSC FORM 16-12 06/95 (1.0) PREVIOUS EDITIONS MAY BE USED KDP-T-5411_Rev_Basic-1 APPROVED FOR PUBLIC RELEASE — DISTRIBUTION IS UNLIMITED KSC-DF-107 Revision F RECORD OF REVISIONS/CHANGES REV CHG LTR NO. DESCRIPTION DATE Basic issue. February 1979 Basic-1 Added Section V, Space Station Project Documentation July 1987 Format and Preparation Guidelines. A General revision incorporating Change 1. March 1988 B General revision incorporating Supplement 1 and the metric August 1995 system of measurement. C Revised all sheets to incorporate simplified document November 15, 2004 formats and align them with automatic word processing software features. D Revised to incorporate an export control sign-off on the April 6, 2005 covers of documents and to remove the revision level designation for NPR 7120.5-compliant project plans. E General revision. August 3, 2015 F General revision and editorial update. July 8, 2017 ii APPROVED FOR PUBLIC RELEASE — DISTRIBUTION IS UNLIMITED KSC-DF-107 Revision F CONTENTS 1. INTRODUCTION ............................................................................................ 1 1.1 Purpose ......................................................................................................... 1 1.2 Scope and Application.................................................................................... 1 1.3 Conventions of This Guide ............................................................................
    [Show full text]
  • 01: Introduction to Technical Communication
    Kennesaw State University DigitalCommons@Kennesaw State University Open Technical Communication Open Educational Resources 7-1-2019 01: Introduction to Technical Communication Cassandra Race Kennesaw State University, [email protected] Follow this and additional works at: https://digitalcommons.kennesaw.edu/opentc Part of the Technical and Professional Writing Commons Recommended Citation Race, Cassandra, "01: Introduction to Technical Communication" (2019). Open Technical Communication. 1. https://digitalcommons.kennesaw.edu/opentc/1 This Article is brought to you for free and open access by the Open Educational Resources at DigitalCommons@Kennesaw State University. It has been accepted for inclusion in Open Technical Communication by an authorized administrator of DigitalCommons@Kennesaw State University. For more information, please contact [email protected]. 1/8/2020 Introduction to Technical Writing Introduction to Technical Writing Cassandra Race Chapter Objectives Upon completion of this chapter, readers will be able to: 1. Define technical writing. 2. Summarize the six characteristics of technical writing. 3. Explain basic standards of good technical writing. The Nature of Technical Writing Did you know that you probably read or create technical communication every day without even realizing it? If you noticed signs on your way to work, checked the calories on the cereal box, emailed your professor to request a recommendation, or followed instructions to make a withdrawal from an ATM; you have been involved with technical, workplace, or professional communication. So what? You ask. Today, writing is a more important skill for professionals than ever before. The National Commission on Writing for Americas Families, Schools, and Colleges (2004) declares that writing today is not a frill for the few, but an essential skill for the many, and goes on to state that much of what is important in American public and economic life depends on strong written and oral communication skills.
    [Show full text]
  • The First Wave (1953–1961) of the Professionalization Movement in Technical Communication Edward A
    Applied Research The First Wave (1953–1961) of the Professionalization Movement in Technical Communication Edward A. Malone Abstract Purpose: To demonstrate that the professionalization of our field is a long-term project that has included achievements as well as setbacks and delays Methods: Archival research and analysis. Results: Many of the professionalization issues that we are discussing and pursuing today find their genesis – or at least have antecedents – in the work of the founders of the profession in the 1950s. Conclusions: Our appraisal of our professionalization gains must be tempered by a certain amount of realism and an awareness of the history of the professionalism movement in technical communication. Keywords: technical communication, history, professionalization, 1950s Practitioner’s • This study provides a consideration • It makes us better informed about takeaway of current professionalization issues the origin and early development in the context of their historical of the profession of technical development. communication in the United States. • It encourages us to temper our • It contributes to the creation of a enthusiasm and remain cautiously strong, shared historical consciousness optimistic about recent gains in the among members of the profession. quest for professional status and recognition. Introduction what possible consequences might result from our achieving full professional stature” (Savage, 1997, p. As a former president of the Society of Technical 34). The profession-building activities of the 1950s Writers and Publishers (STWP) noted, “There (e.g., the formation of professional organizations was a controversy in the early days. Was technical and journals, the writing of professional codes of writing really a profession? Did we want it to be a conduct, the creation of academic programs) were profession? If it was, how should we get other people attempts to professionalize technical communication.
    [Show full text]
  • Has Technical Communication Arrived As a Profession?
    APPLIED RESEARCH SUMMARY ᭜ Reports results of a practitioner survey on the definition of technical communication and the role of technology in their work ᭜ Argues that technical communication demonstrates a stable set of core values which suggest the field has a professional identity The Future Is the Past: Has Technical Communication Arrived as a Profession? KATHY PRINGLE AND SEAN WILLIAMS INTRODUCTION 139). In other words, like Grice and Krull, Davis sees n the May 2001 Technical communication, Roger technical communication as a profession with a dual iden- Grice and Robert Krull introduced a special issue on tity that involves some set of core skills that dovetail with the future of technical communication by outlining technological skills. Isome skills that participants at a 1997 conference at Davis doesn’t suggest what those core skills are, how- Rensselaer Polytechnic Institute had identified. From the ever, and Grice and Krull base their predictions on intuition list of things identified at that conference, Grice and Krull and conversations that occurred four years prior to the suggest that three categories run through all of the sugges- publication of their special issue. Some questions emerge tions. then. If we are going to postulate what the future of tech- 1. Technical communication will involve some kind nical communication holds, shouldn’t we understand what of information design skill, whether it’s testing, writing, is going on now? What is actually happening in the pro- visual design, or training. fession? What are practitioners in the profession actually 2. Technical communication will involve shifting doing? How do practitioners actually define the field and technological skills, including statistical testing, database their work? Likewise, shouldn’t we have an historical per- design, Web design, and authoring languages.
    [Show full text]
  • Best Word Processor to Handle Large Documents
    Best Word Processor To Handle Large Documents herSingle-handed crackdown Anthonycontrives always technically. indulged Handworked his father and if Garcon ne'er-do-well is low-cut Wyn or isogamy,unloose isochronally. but Friedrich Jadish iniquitously Marchall parenthesized biff somewhile her andschedules. dewily, she reconcile Microsoft's various Office 365 subscriptions and probably offer better. Top 6 Document Collaboration Tools In 2021 Bit Blog Bitai. Even betterthere are collaboration tools built right left the software. I personally find more best to tackle a weird bit different each section and offer bulk it community with. Allows you easy to perish with different tasks at the last time. Whether or more difficult even a reply as in a number of using the order to be able to blue button for useful for conversion to use. No matter how do bold, editing is not supported in both. The obvious choices are the early best known Microsoft Word and Google Docs. Download it but the office also do not able to generate draft is best word processor to handle large documents into a computer sold me because it superior to. How to concede Advantage of Microsoft Word enter Your Galaxy. How well Manage Large Documents in Word. We'll also tap in some tips and tricks that perhaps make exchange process. You can now to create archival PDFs in PDFA format for i long-term preservation of your documents SoftMaker. Home Mellel. 11 Word Processor Essentials That Every Student Needs to. You can in large document information quickly It offers live. Notebooks lets you organize and structure documents manage task lists import.
    [Show full text]
  • 1. Introduction: the Nature of Sexy Technical Writing
    Kennesaw State University DigitalCommons@Kennesaw State University Sexy Technical Communications Open Educational Resources 3-1-2016 1. Introduction: The aN ture of Sexy Technical Writing Cassandra Race Kennesaw State University, [email protected] Follow this and additional works at: http://digitalcommons.kennesaw.edu/oertechcomm Part of the Technical and Professional Writing Commons Recommended Citation Race, Cassandra, "1. Introduction: The aN ture of Sexy Technical Writing" (2016). Sexy Technical Communications. 1. http://digitalcommons.kennesaw.edu/oertechcomm/1 This Article is brought to you for free and open access by the Open Educational Resources at DigitalCommons@Kennesaw State University. It has been accepted for inclusion in Sexy Technical Communications by an authorized administrator of DigitalCommons@Kennesaw State University. For more information, please contact [email protected]. The Nature of Sexy Technical Writing Introduction by Cassandra Race Sexy Technical Communication Home Introduction: The Nature of Sexy Technical Writing Did you know that you probably read or create technical communication every day without even realizing it? If you noticed signs on your way to work, checked the calories on the cereal box, emailed your professor to request a recommendation or followed instructions to make a withdrawal from an ATM, you have been involved with technical, workplace, or professional communication. So what? You ask. Today, writing is a more important skill for professionals than ever before. The National Commission on Writing for Americas Families, Schools, and Colleges (2004) declares that writing today is not a frill for the few, but an essential skill for the many,and goes on to state that much of what is important in American public and economic life depends on strong written and oral communication skills.
    [Show full text]
  • How Are New Technologies Affecting the Technical Writer/Audience Relationship?
    How are new technologies affecting the technical writer/audience relationship? Osha Roopnarine Department of Writing Studies, College of Liberal Arts Mentor: Dr. Ann Hill Duin for WRIT 8505 – Plan C Capstone Please address correspondence to Osha Roopnarine at [email protected], Department of Writing Studies, University of Minnesota Twin Cities, Minneapolis, MN 55455. IRB Exempt: STUDY00002942 In partial fulfilment for a MS in Science and Technical Communication. © May 9th, 2018 Osha Roopnarine Technology, Technical Writer, Audience, Relationship Roopnarine Abstract This research investigates how the technical writer/audience relationship is affected by new technologies. The emergence of new technologies is occurring at a rapid pace and is changing the technical writer and audience relationship. The revised rhetorical triangle model by Lunsford and Ede (2009) does not adequately describe the relationship among these three dimensions (technology, writer, and audience). Therefore, I conducted an online survey with open-ended questions that were designed to gather opinions from an audience familiar with technical writing. I performed qualitative affinity mapping analysis of the responses to determine themes for the relationship among the writer, audience, and technology. I determined that new and emerging technologies are increasing the interaction of the audience with social media, wearables, augmented, and assistive technologies. This gives them easy access to new and archived information, which increases their cognition of the technological world. As a result, they seek alternate ways to comprehend technical information such as in choosing online technical manuals over the printed document, video tutorials over the written format, and opinions and evaluations of products from other users who are posting online.
    [Show full text]
  • Contexts of Technical Communication Sponsored by ■■ Analysis of Industry Job Postings
    November 2015 Volume 62 Number 4 CONTEXTS OF TECHNICAL COMMUNICATION SPONSORED BY ■ ANALYSIS OF INDUSTRY JOB POSTINGS ■ VISUALIZING A NON-PANDEMIC ■ APP ABROAD AND MUNDANE ENCOUNTERS ■ TRANSLATION AS A USER- LOCALIZATION PRACTICE 2015 release Adobe Tech Comm Tools MEET TOMORROW’S NEEDSTODAY Learn more Try now Request demo 2015 release 2015 release 2015 release 2015 release 2015 release Adobe Adobe Adobe Technical Adobe Adobe FrameMaker RoboHelp Communication Suite FrameMaker FrameMaker XML Author Publishing Server Adobe, the Adobe logo, and FrameMaker are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. © 2015 Adobe Systems Incorporated. All rights reserved. Deliver a superior content consumption experience to end users with the new HTML5 layout Announcing the 2015 release of Adobe RoboHelp Dynamic content lters | New HTML5 layout | Mobile app output support | Modern ribbon UI Upgrade to the new Adobe RoboHelp (2015 release) for just US$399.00 Try Now Request Demo Request Info In the new release of Adobe RoboHelp, the latest HTML5 Responsive Layouts support Dynamic Filtering giving users the option to lter the content and see just what is relevant to them. Content Categories in WebHelp gave users the ability to choose sub-sets that had been dened by the author. Dynamic Filtering in HTML5 goes much further as the author can give more options and the user gets to choose which ones they want. Also the author can easily create an app in both iOS and Android formats.” Call 800 —Peter Grainge, Owner, www.grainge.org -833-6687 (Monday-Friday, 5am-7pm PST) Adobe, the Adobe logo, and RoboHelp are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
    [Show full text]
  • Technical Writing in the English Renaissance 1475-1640
    Nadeane Trowse 77 The emergence of a tradition: Technical writing in the English Renaissance 1475-1640 By Nadeane Trowse UBC!University College of the Fraser Valley Elizabeth Tebeaux. The Emergence of a Tradition: Technical Writing in the English Renaissance 1475-1640, Amityville, New York, Baywood Pub­ lishing, 1997. Elizabeth Tebeaux's book The Emergence ofa Tradition: Technical Writing in the English Renaissance 1475-1640 demonstrates that technical writing as a kind of text, as one type of social means for the distribution of information, has a rich history. Tebeaux presents the early modern ancestors of today's "how to" guides, medical manuals, and plant identification guides. Teachers and students of technical writing, working in a discipline that may sometimes feel like a continually emerging disci­ pline, will likely appreciate Tebeaux's work, as she writes technical writing and its scholars into an historical continuum, reinscribing both practitioners and the disci­ pline itself. But such appreciative readers might wish, too, for the insights that would have been provided had Tebeaux situated her discussion of the sociality of the texts and the emergence of technical writing more firmly in current ongoing discussions of the sociality of texts and their formal, situated constraints. Tenebeaux indicates that her book is a response to Michael Moran's challenging claim: "the history of technical writing has not been written" (Moran, 1986, p. 25). Tebeaux offers such a history, at least for the technical writing occurring in England between 1475 and 1640. The texts she examines occupy a significant and highly varied spectrum of English history, from Caxton's printing press to the beginning of the English civil wars between Royalists and supporters ofthe Commonwealth.
    [Show full text]