I seem to remember something about setting the buffer length differently and getting significantly faster results -- but that makes the story much less interesting.
That was a good course -- the guy ping-ponged between starting companies and teaching, so his course was solidly grounded in reality. He had _lots_ of stories about wide-eyed technical innocence running smack into hard engineering realities.
And since this is far OT -- any TECO fans [that almost came as fanatics] out there. In early 70's I worked in Maynard [ML5-5 to be exact]. Came in one Saturday to finish up a 2 page report using TECO on a KL-10 system that during week handled major portion of DEC's production control. Misplaced a ";" IIRCC thus copying file to itself ;[
Got thrown off system by upper level supervisor program that someone with my permissions should not have even new knew existed. However many scratch disks there were, I attempted to fill them all. A systems expert acquaitence told be I had managed to skip 2-3 levels of protection. Gee, wonder why DEC tried vainly to discourage use of that program -- you could do just about anything in it.
Actually I found quite a few google links to antifreeze with the apparently misspelled Xerex in place of Zerex. Regardless of the spelling the pronuciation is the same and companies likely would not want to have their product confused for another with a similar name.
ah but no magazine editor or book editor that I know of is capable of detecting technical errors, for example in an equation. They're not skilled in all aspects of every engineering topic (no one is). So the editors are expecting that the content of a magazine article, or a technical book, is correct. It's up to the author to make sure the material is correct.
The problem is: once an author writes some technical material that author is the *LEAST* reliable person on the planet Earth to find mistakes in that material. I'm sure you know that. So, ... finding a competent person to review technical writing is **VERY** important. The problem is: reviewing tech material in a thorough way is painful, unpleasant, and yields almost no reward. So it's a royal pain to ask reviewers to carefully review your writing and then tell those reviewers that, by the way, there's no reward for their efforts.
The reason I said there is "usually" a technical review is because the last technical book that I bought contained SOOooo many technical errors that it's clear that no tech review was performed. None!
The typical tech book has a silly little "typo" or misspelled word once every 20-30 pages. The book I bought had an average of more than one "typo" per page!! I am NOT joking. (One page contained four "typos"!!)
What an unprofessional mess by both the authors and the Publisher.
There was a time when looking for a intro to something new I'd give preference to a SAMS book. Not since the early 70's though. Hmmm, did they get bought out in late 60's/early 70's?
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.