Megalextoria
Retro computing and gaming, sci-fi books, tv and movies and other geeky stuff.

Home » Archive » comp.sys.amiga » Why Engineers spell so bad
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Why Engineers spell so bad [message #293660] Mon, 01 December 1986 00:44 Go to next message
dillon is currently offline  dillon
Messages: 81
Registered: November 1985
Karma: 0
Member
Article-I.D.: cory.8612010544.AA20557
Posted: Mon Dec  1 00:44:40 1986
Date-Received: Mon, 1-Dec-86 06:38:11 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 39


	Hay, I cun spel beter thun al of ya!  seee?  Now lisun too me:

	We Engineers are renown for our inability to spell.  The problem isn't
that we don't know how to spell (we do), nor does it have to do with the
size of the Engineering vocabulary we need to know (is BIG).  It especially
has absolutely nothing to do with our writing ability (exception: Bill the 
Cat).

	No folks, the problem is that our brains simply run too fast.  That's
right, the queues going from our primary CPU to our Mechanical Control
Sub-processing Centers get completely overloaded, and, as a result, some 
of the data gets mixed up or chopped off.  We tell our hands to go write
something with a flick of our neurons and go on to other things without
bothering to check on their progress.  This is why you often see whole
phrases missing from unedited engineering papers.  Other examples include
the well documented Kernal Kernel problem.

	English Majors, on the other hand, do not have to be so abstract,
which allows their MCSC's to memorize widely used output strings and thus
keep up with the primary CPU.

	Typists (as a living. Read: 'Data Entry') are on the other side of
the spectrum alltogether.  They don't have to think at all, and can 
concentrate all their resources on the queuing aspect.  Thus, the better
typists (110 Wpm +) do not have to ask the speaker to pause when changing
paper on their type-writer.


	So, in conclusion, the most effective method for an Engineer to
curtail his spelling problems is with a lot of practice on his queuing
ability.  Simply sit down and write a program which scrolls arbitrary
words onto the screen, and see if you can type them in the same order they
appear.  The idea is to always set the speed the program outputs the words 
just a tad faster than your current copying ability.



			-Matt
Re: Why Engineers spell so bad [message #293776 is a reply to message #293660] Tue, 02 December 1986 13:33 Go to previous messageGo to next message
joels is currently offline  joels
Messages: 20
Registered: May 2013
Karma: 0
Junior Member
Article-I.D.: tekred.870
Posted: Tue Dec  2 13:33:03 1986
Date-Received: Fri, 5-Dec-86 21:22:48 EST
References: <8612010544.AA20557@cory.Berkeley.EDU>
Organization: Tektronix Inc., Beaverton, Or.
Lines: 17

In article <8612010544.AA20557@cory.Berkeley.EDU>, dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:

 >  Simply sit down and write a program which scrolls arbitrary
 >  words onto the screen, and see if you can type them in the same order they
 >  appear.  The idea is to always set the speed the program outputs the words 
 >  just a tad faster than your current copying ability.
 >  
 >  
 >  
 >  			-Matt

Why bother? Just use a spelling checker. That's what computers are
for, aren't they?


Joel Swank
Tektronix, Redmond, Oregon
Re: Why Engineers spell so bad [message #293815 is a reply to message #293660] Tue, 02 December 1986 22:55 Go to previous messageGo to next message
star is currently offline  star
Messages: 23
Registered: October 1985
Karma: 0
Junior Member
Article-I.D.: vax4.3710
Posted: Tue Dec  2 22:55:27 1986
Date-Received: Sun, 7-Dec-86 04:26:56 EST
References: <8612010544.AA20557@cory.Berkeley.EDU>
Organization: John Fluke Mfg. Co., Inc., Everett, WA
Lines: 54
Summary: Check this out - Jive is worse!!!



Subject, dig dis: Why Engineers spell so's bad-ass
Message-ID: <8612010544.AA20557@co'y.  Slap mah fro!Berkeley.  Slap mah fro!EDU>
Date, dig dis: 1 Dec 86 05:44:40 GMT
Sender, dig dis: daemon@ucbvax.BERKELEY.EDU
Organizashun: University uh Califo'nia at Berkeley
Lines, dig dis: 39


	Hay, ah' cun spel beta' dun al uh ya.  Right On!    seee?  Now lisun too me, dig dis:

	We Engineers are renown fo' our inability t'spell.  Ya' know?  De problem isn't
dat we  duzn't know how t'spell (we do), no' duz it gots'ta do wid de
size uh de Engineerin' vocabulary we need t'know (is BIG).  It especially
 gots'ta absolutely nodin' t'do wid our writin' ability (excepshun: Bubba de 
Cat).

	No folks, de problem be dat our brains simply run too fast.  Dat's
right, de queues goin' fum our primary CPU t'our Mechanical Control
Sub-processin' Centers git completely overloaded, and, as some result, some 
of de data gits mixed down o' chopped off.  What it is, Mama!  We tell our hands t'go scribble
somedin' wid some flick uh our neurons and go on t'oda' din's widout
boderin' t'check on deir progress.  Dis be why ya' often see whole
phrases missin' fum unedited engineerin' sheets.  Oda' examples include
desheeit documented Kernal Kernel problem.  'S coo', bro.

	English Majo's, on de oda' hand, do not gots'ta be so's abstract,
which allows deir MCSC's t'memo'ize widely used output chittlin's and dus
keep down wid de primary CPU.

	Typists (as some livin'. Read, dig dis: 'Data Entry') are on de oda' side of
de spectrum alltogeder.  Ah be baaad...  Dey  duzn't gots'ta dink at all, and kin 
concentrate all deir resources on de queuin' aspect.  Dus, de better
typists (110 Wpm +) do not gots'ta ax' de speaka' to pause when changin'
sheet on deir type-scribbler.  Ah be baaad...


	So, in conclusion, de most effective medod fo' an Enginea' to
curtail his spellin' problems be wid some lot uh practice on his queuin'
ability.  Slap mah fro!  Simply sit waaay down and scribble some program which scrolls arbitrary
wo'ds onto de screen, and see if ya' kin type dem in de same o'da' dey
appear.  Ah be baaad...  De idea be to always set da damn speed da damn program outputs de wo'ds 
plum a tad fasta' dan yo' current copyin' ability.  Slap mah fro!



			-Matt


-- 
Dave Whitlock
        {decvax!microsof,uw-beaver,ssc-vax,allegra,lbl-csam}!fluke!star
--John Fluke Mfg. Co., 33031 Schoolcraft Road, Livonia, MI 48150
Re: Why Engineers spell so bad [message #293834 is a reply to message #293660] Sun, 07 December 1986 14:34 Go to previous messageGo to next message
dillon is currently offline  dillon
Messages: 81
Registered: November 1985
Karma: 0
Member
Article-I.D.: cory.8612071934.AA10881
Posted: Sun Dec  7 14:34:50 1986
Date-Received: Sun, 7-Dec-86 21:15:57 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 14


 > 	Hay, ah' cun spel beta' dun al uh ya.  Right On!    seee?  Now lisun too me, dig dis:
 > 
 > 	We Engineers are renown fo' our inability t'spell.  Ya' know?  De problem isn't
 > dat we  duzn't know how t'spell (we do), no' duz it gots'ta do wid de
 > size uh de Engineerin' vocabulary we need t'know (is BIG).  It especially
 >  gots'ta absolutely nodin' t'do wid our writin' ability (excepshun: Bubba de 
 > Cat).

	Lets all give a hand to JIVE.

	Clap Clap Clap Clap Clap Clap Clap Clap Clap

				-Matt
Re: Why Engineers spell so bad [message #293926 is a reply to message #293660] Tue, 09 December 1986 08:31 Go to previous message
mjg is currently offline  mjg
Messages: 68
Registered: February 2013
Karma: 0
Member
Article-I.D.: ecsvax.2446
Posted: Tue Dec  9 08:31:38 1986
Date-Received: Wed, 10-Dec-86 12:29:08 EST
References: <8612010544.AA20557@cory.Berkeley.EDU>
Organization: UNC Educational Computing Service
Lines: 6




The real reason is they are too busy to change their socks.

Mike Gingell   ...decvax!mcnc!ecsvax!mjg
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Help with EGad?
Next Topic: DBW vt100 v2.3 running on custom screen
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Apr 24 10:42:10 EDT 2024

Total time taken to generate the page: 0.04378 seconds