| 000 | 03223nam a2200361 i 4500 | ||
|---|---|---|---|
| 005 | 20250919011736.0 | ||
| 008 | 160412s20142014flu b 001 0 eng | ||
| 020 |
_a9781482234312 _qpaperback _cRM209.37 |
||
| 039 | 9 |
_a201608261130 _bbaiti _c201608101008 _drahah _y04-12-2016 _zrahah |
|
| 040 |
_aDLC _beng _cDLC _erda _dDLC _dUKM |
||
| 090 | _aT11.R683 3 | ||
| 090 |
_aT11 _b.R683 3 |
||
| 100 | 1 |
_aRothwell, Edward J. _eauthor |
|
| 245 | 1 | 0 |
_aEngineering writing by design : _bcreating formal documents of lasting value / _cEdward J. Rothwell, Department of Electrical and Computer Engineering, Michigan State University, East Lansing, USA, Michael J. Cloud, Department of Electrical and Computer Engineering, Lawrence Technological University, Southfield, Michigan, USA. |
| 264 | 1 |
_aBoca Raton : _bCRC Press, Taylor & Francis Group, _c[2014] |
|
| 264 | 4 | _c©2014 | |
| 300 |
_axi, 187 pages ; _c23 cm |
||
| 336 |
_atext _2rdacontent |
||
| 337 |
_aunmediated _2rdamedia |
||
| 338 |
_avolume _2rdacarrier |
||
| 504 | _aIncludes bibliographical references and index. | ||
| 520 |
_a'Preface In Walden, Henry Thoreau asserts that'Books must be read as deliberately and reservedly as they were written.' Given the serious and highly technical nature of formal engineering writing, any reader of such writing would be wise to follow Thoreau's advice. The purpose of the present book, however, is to speak to the engineering writer. Our basic premise is that engineering material should be written as deliberately and carefully as it will be read. Engineers are smart people and their work is important. Their writing should not be inaccurate, vague, ambiguous, or otherwise opaque. To a great extent, modern engineering is an extension of science and mathematics and is therefore amenable to clear and logical exposition. Some aspects of engineering remain more art than science, to be sure. We would argue, however, that in such cases it is especially important for engineers to write precisely, as readers will be in less of a position to close expository gaps through deductive reasoning. In other words, clear description is just as important in technical writing as clear argumentation. Technical subjects can make for difficult reading as it is. A reader should not have to go over a passage again and again, finally being forced to guess whether the writer was attempting to motivate a viewpoint, describe something that already exists, describe something that could conceivably exist, draw a conclusion from known facts, persuade, or something else. Yet, a writer who approaches the writing task carelessly, by simply accumulating a pile of words and equations, may produce just that sort of confusion'-- _cProvided by publisher. |
||
| 650 | 0 | _aTechnical writing. | |
| 700 | 1 |
_aCloud, Michael J. _eauthor |
|
| 907 |
_a.b16307732 _b2019-11-12 _c2019-11-12 |
||
| 942 |
_c01 _n0 _kT11.R683 3 |
||
| 914 | _avtls003604166 | ||
| 990 | _abety | ||
| 991 | _aFakulti Kejuruteraan dan Alam Bina | ||
| 998 |
_al _b2016-12-04 _cm _da _feng _gflu _y0 _z.b16307732 |
||
| 999 |
_c608320 _d608320 |
||