1 / 11

Technical English: Fewer is better!

Technical English: Fewer is better!. John Morris Faculty of Engineering, Mahasarakham University Computer Science/ Electrical and Computer Engineering, The University of Auckland. Iolanthe II leaves the Hauraki Gulf under full sail – Auckland-Tauranga Race, 2007.

reidar
Télécharger la présentation

Technical English: Fewer is better!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Technical English:Fewer is better! John Morris Faculty of Engineering,Mahasarakham University Computer Science/Electrical and Computer Engineering, The University of Auckland Iolanthe II leaves the Hauraki Gulf under full sail – Auckland-Tauranga Race, 2007

  2. Bad habits I - References • Referring to other’s work by numbers: In [1], it was shown that … • There are several reasons why this is bad! • The people who wrote paper [1] probably put a lot of work into it .. Acknowledge this by writing their names! Smith and Jones showed that …. [1]. • If you only write [1], then I’m forced to go to your reference list to find out what your source is! • However, if I know the field well, ‘Smith and Jones’ may well be enough to tell me which paper you used as a source

  3. References • Where do the reference labels go? • Smith and Jones[1] showed that …. . • Smith and Jones showed that …. [1]. • The label [1] should go after the statement from the source. • This clearly separates information from your source from any comments that you might make! • Smith and Jones showed that …. [1] but they did not consider …..

  4. References • Bad style, not concise In [1], it was shown that … • Better ..

  5. References • Bad style, not concise In [1], it was shown that … • Better .. It has been shown that …[1] • Shorter • Has the label in the right place!! • Note perfect tense here – the work has been reported, so assumed complete! • or, even better .. • X et al showed that …[1] • Direct – active voice instead of passive always reads better!

  6. References • Abstracts • Avoid references in abstracts wherever possible • Definitely do NOT use reference labels! • An abstract will often be read alone • Readers will not have access to the reference list, so the number is useless to them • If you really must .. This study improves A et al’sresult … • Use the name(s) of the authors • You do not need to give the full reference for A et al’s work. • Readers can get this from the full paper (or by Google )

  7. References • Names • English convention • Refer to other authors by family name (surname) alone Smith measured …[32]. • Do not write B. Smith measured …[32]. David Smith measured …[32]. • Only use given names if there are two authors with the same family name B. Smith reported …[32] but J. Smith provided conflicting data[33].

  8. References • Non-English names • Try to determine a family name and use it! • Be careful with Chinese • It’s not always clear which is the family name! • Chinese often reverse from their native order • Family name + two syllable given name, eg Xie Jingling • to an ‘English’ form Jingling Xie • Here family name is Xie, so write Xie reported …[32]. If in doubt, ask a Chinese colleague! • Other Asian languages, eg Japanese, Korean, .. , present similar problems .. Seek advice from a native speaker!

  9. Words to avoid • Functionality • Much loved by computer scientists! • An appalling abuse of English!! • This word was formed in this way • Take a verb (or noun) ‘function’ • Turn it into an adjective ‘functional’ • Turn it back into a noun ‘functionality’ • And use it a synonym for a much simpler word that already existed ‘capability’!! • Worse - use it in place of ‘functions’ • Use ‘capability’ or ‘functions’ instead!!

  10. Words to avoid • Utilize • Use ‘use’ instead!

  11. Words to avoid • Proved • Formal scientific theory …. • Use ‘use’ instead!

More Related