WEBVTT - Turboencabulators and Technobabble

0:00:04.120 --> 0:00:07.160
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:07.200 --> 0:00:13.720
<v Speaker 1>stuff Works dot com. Hey therein Welcome to tech Stuff

0:00:13.720 --> 0:00:17.960
<v Speaker 1>and Happy April Fool's Day everyone. I'm Jonathan Strickland. I'm

0:00:18.000 --> 0:00:20.439
<v Speaker 1>an executive producer with How Stuff Works in my Heart Radio,

0:00:20.440 --> 0:00:23.600
<v Speaker 1>and I love all things tech and this episode should

0:00:23.640 --> 0:00:28.120
<v Speaker 1>publish on April first, two thousand nineteen, unless my producer

0:00:28.200 --> 0:00:30.960
<v Speaker 1>Tari has played in April Fool's Joke on me while

0:00:30.960 --> 0:00:34.200
<v Speaker 1>I'm on vacation, and I thought, well, I could do

0:00:34.560 --> 0:00:37.519
<v Speaker 1>another follow up episode on the various tech pranks that

0:00:37.560 --> 0:00:39.640
<v Speaker 1>have been pulled since the last time I did a

0:00:39.760 --> 0:00:43.400
<v Speaker 1>prank roundup, which I think was in two thousand fifteen,

0:00:43.640 --> 0:00:46.839
<v Speaker 1>But then I decided to focus on something else, a

0:00:46.920 --> 0:00:51.120
<v Speaker 1>really amazing example of engineering. So there was a fellow

0:00:51.159 --> 0:00:54.560
<v Speaker 1>who was named John Helen's Quick who published a piece

0:00:54.760 --> 0:00:57.840
<v Speaker 1>at least as early as nineteen It was in a

0:00:57.920 --> 0:01:02.560
<v Speaker 1>December edition of the British Institution of Electrical Engineers Students

0:01:02.640 --> 0:01:05.840
<v Speaker 1>Quarterly Journal. Now I say at least as early as

0:01:06.000 --> 0:01:09.440
<v Speaker 1>nineteen forty four, because there's some people who say that

0:01:09.520 --> 0:01:12.560
<v Speaker 1>it may have been published even earlier in some other

0:01:12.640 --> 0:01:15.640
<v Speaker 1>journal by nineteen forty two, but it's super hard to

0:01:15.640 --> 0:01:19.480
<v Speaker 1>track down. The earliest I found was this nineteen journal.

0:01:19.800 --> 0:01:23.840
<v Speaker 1>The article is a masterpiece. It describes a transformative technology

0:01:23.920 --> 0:01:28.039
<v Speaker 1>called the turbo encabulator. Now, normally I wouldn't read out

0:01:28.080 --> 0:01:31.000
<v Speaker 1>an entire piece, but in order to understand how important

0:01:31.040 --> 0:01:34.160
<v Speaker 1>this is, I figured I would make an exception, and

0:01:34.200 --> 0:01:38.800
<v Speaker 1>so here is Mr Quick's description of the turbo encabulator.

0:01:39.280 --> 0:01:42.000
<v Speaker 1>For a number of years now, work has been proceeding

0:01:42.040 --> 0:01:45.479
<v Speaker 1>in order to bring perfection to the crudely conceived idea

0:01:45.560 --> 0:01:48.960
<v Speaker 1>of a transmission that would not only supply inverse reactive

0:01:49.000 --> 0:01:52.720
<v Speaker 1>current for use in unilateral phase detractors, but would also

0:01:52.760 --> 0:01:57.200
<v Speaker 1>be capable of automatically synchronizing cardinal gram meters. Such an

0:01:57.240 --> 0:02:01.680
<v Speaker 1>instrument is the turbo encabulator. Now, basically, the only new

0:02:01.720 --> 0:02:05.240
<v Speaker 1>principle involved is that instead of power being generated by

0:02:05.280 --> 0:02:08.760
<v Speaker 1>the relative motion of conductors and fluxes, it is produced

0:02:08.800 --> 0:02:12.960
<v Speaker 1>by the modial interaction of magneto reluctance and capacitive diractants.

0:02:13.400 --> 0:02:17.359
<v Speaker 1>The original machine had a base plate of prefabriulated ammulite

0:02:17.600 --> 0:02:21.200
<v Speaker 1>surmounted by a malleable logarithmic casing in such a way

0:02:21.240 --> 0:02:24.280
<v Speaker 1>that the two sperving bearings were in a direct line

0:02:24.320 --> 0:02:28.200
<v Speaker 1>with the pentometric fan. The ladder consisted simply of six

0:02:28.280 --> 0:02:33.560
<v Speaker 1>hydrocoptic marsal vances, so fitted to the ambifacient lunar wainshaft

0:02:33.840 --> 0:02:38.280
<v Speaker 1>that side fumbling was effectively prevented. The main winding was

0:02:38.440 --> 0:02:42.519
<v Speaker 1>of the normal lotus o delta type, placed in penandermic

0:02:42.680 --> 0:02:46.440
<v Speaker 1>semi boloid slots in the stature, every seventh conductor being

0:02:46.480 --> 0:02:49.959
<v Speaker 1>connected by a non reversible trimmy pipe to the differential

0:02:50.040 --> 0:02:53.000
<v Speaker 1>girdle spring on the up end of the gram meters

0:02:53.320 --> 0:02:57.360
<v Speaker 1>forty one manestic league spaced grouding brushes were arranged to

0:02:57.440 --> 0:03:00.639
<v Speaker 1>feed into the rotor slip stream a mixed of high

0:03:00.880 --> 0:03:06.920
<v Speaker 1>s value phenel hydro benzamine and five percent ruminative tetralio hexamine.

0:03:07.120 --> 0:03:11.120
<v Speaker 1>Both these liquids have specific paracoustics given by p equals

0:03:11.160 --> 0:03:14.400
<v Speaker 1>two times five c end to the six times seven,

0:03:14.919 --> 0:03:20.120
<v Speaker 1>wherein is the diathetical evolute of retrograde temperature phase disposition

0:03:20.480 --> 0:03:26.200
<v Speaker 1>and see is col Mondlaise annular grillage coefficient. Initially, n

0:03:26.360 --> 0:03:30.040
<v Speaker 1>was measured with the aid of a metapolar refractive pilfometer,

0:03:30.440 --> 0:03:33.040
<v Speaker 1>but up to the present date nothing has been found

0:03:33.040 --> 0:03:38.000
<v Speaker 1>to equal the transcendental hopper data scope. Electrical engineers will

0:03:38.000 --> 0:03:41.760
<v Speaker 1>appreciate the difficulty of new being together the regurgative pur

0:03:41.880 --> 0:03:45.960
<v Speaker 1>well and a supremitive went al sprocket. Indeed, this proved

0:03:46.000 --> 0:03:48.800
<v Speaker 1>to be a stumbling block to further development until in

0:03:48.920 --> 0:03:52.680
<v Speaker 1>nWo it was found that the use of anhydrous nangling

0:03:52.720 --> 0:03:57.200
<v Speaker 1>pins enabled a cryptognastic bowling him to be tankered. The

0:03:57.280 --> 0:04:02.040
<v Speaker 1>early attempts to construct a sufficiently robust spiral dcommutator failed

0:04:02.120 --> 0:04:05.240
<v Speaker 1>largely because of a lack of appreciation of the large

0:04:05.320 --> 0:04:09.320
<v Speaker 1>quasi p stic stresses and Grimlin studs. The latter were

0:04:09.440 --> 0:04:12.400
<v Speaker 1>specially designed to hold the roth Itt bars to the

0:04:12.440 --> 0:04:16.640
<v Speaker 1>spam shaft. When, however, it was discovered that the winding

0:04:16.800 --> 0:04:20.640
<v Speaker 1>could be prevented by a simple addition to the living sockets,

0:04:20.680 --> 0:04:25.000
<v Speaker 1>almost perfect running was secured. The operating point is maintained

0:04:25.040 --> 0:04:28.240
<v Speaker 1>as near as possible to the h f rempeak by

0:04:28.320 --> 0:04:33.560
<v Speaker 1>constantly formaging the bitumogeneous spandrels. This is a distinct advance

0:04:33.640 --> 0:04:37.120
<v Speaker 1>on the standard nivel sheave. In the no dramcock oil

0:04:37.279 --> 0:04:41.719
<v Speaker 1>is required after the phase detractors have been remissed. Undoubtedly,

0:04:42.000 --> 0:04:45.479
<v Speaker 1>the turbo encabulator has now reached a very high level

0:04:45.520 --> 0:04:49.240
<v Speaker 1>of technical development. It has been successfully used for operating

0:04:49.279 --> 0:04:54.680
<v Speaker 1>no fur trunions. In addition, wherever Barrissant score motion is required,

0:04:54.720 --> 0:04:58.360
<v Speaker 1>it may be employed in conjunction with a drawn reciprocating

0:04:58.440 --> 0:05:04.120
<v Speaker 1>dingle arm to reduce ying a soiled deplinoration. Now my

0:05:04.320 --> 0:05:07.120
<v Speaker 1>guess is you just listen to me read off that

0:05:08.160 --> 0:05:11.880
<v Speaker 1>let's say, remarkable description, and you're left with the obvious

0:05:11.880 --> 0:05:16.120
<v Speaker 1>response of of course, that's that's blatantly obvious, that's old news.

0:05:16.920 --> 0:05:21.120
<v Speaker 1>Or perhaps you're having what was the intended response, you're

0:05:21.160 --> 0:05:25.559
<v Speaker 1>confused as heck, Quick's piece was a tongue in cheek

0:05:25.760 --> 0:05:31.159
<v Speaker 1>example of satire, highlighting how engineers would sometimes rely very

0:05:31.240 --> 0:05:35.039
<v Speaker 1>heavily on jargon that you know, didn't seem to really

0:05:35.120 --> 0:05:39.840
<v Speaker 1>mean anything, or purposefully obfuscated the functionality of a system,

0:05:39.960 --> 0:05:43.280
<v Speaker 1>or maybe even cover up the engineer's own ignorance of

0:05:43.279 --> 0:05:48.160
<v Speaker 1>how a system actually worked. Jargon does have some purposes,

0:05:48.200 --> 0:05:51.400
<v Speaker 1>of course. Sometimes you need to create words to describe

0:05:51.480 --> 0:05:55.360
<v Speaker 1>something that didn't exist before. If you make a new

0:05:55.400 --> 0:05:58.359
<v Speaker 1>device that fulfills a specific purpose, you need to have

0:05:58.440 --> 0:06:01.320
<v Speaker 1>a name for it. You might need a name for

0:06:01.400 --> 0:06:04.400
<v Speaker 1>the thing that the device actually does. Maybe whatever the

0:06:04.400 --> 0:06:07.240
<v Speaker 1>device is doing is a brand new thing, so you've

0:06:07.240 --> 0:06:10.320
<v Speaker 1>gotta have some word to describe it. Maybe what it

0:06:10.360 --> 0:06:14.200
<v Speaker 1>does is a very specific instance of a more broad concept.

0:06:14.240 --> 0:06:17.440
<v Speaker 1>So it's not doing a brand new thing, it's just

0:06:17.520 --> 0:06:20.360
<v Speaker 1>doing a thing in a new way. So you create

0:06:20.400 --> 0:06:23.960
<v Speaker 1>words to help build in precision. You don't just mean

0:06:24.000 --> 0:06:27.480
<v Speaker 1>a dingle angle. You might mean a one eighth hexagonal

0:06:27.640 --> 0:06:31.080
<v Speaker 1>matrix dingle angle, so you call this particular component of

0:06:31.440 --> 0:06:35.599
<v Speaker 1>a fronyon or whatever. With precision, you can more quickly

0:06:35.680 --> 0:06:40.840
<v Speaker 1>communicate your exact needs or intentions to others within that field.

0:06:41.440 --> 0:06:45.200
<v Speaker 1>But with that growing precision comes a knowledge gap between

0:06:45.240 --> 0:06:48.960
<v Speaker 1>the people in your field and everybody else. Now, in

0:06:49.000 --> 0:06:53.520
<v Speaker 1>other cases, people rely on jargon not to convey specific meaning,

0:06:53.920 --> 0:06:58.560
<v Speaker 1>but rather to come across as being more sophisticated or intelligent,

0:06:59.080 --> 0:07:01.839
<v Speaker 1>or to make something more complicated than it really is.

0:07:02.320 --> 0:07:04.960
<v Speaker 1>So I'm gonna give you guys some examples from my

0:07:05.040 --> 0:07:09.720
<v Speaker 1>own life. In my life, before I ever was a podcaster,

0:07:09.880 --> 0:07:13.160
<v Speaker 1>before I was a writer for how Stuff Works dot com,

0:07:13.200 --> 0:07:17.680
<v Speaker 1>I worked for a couple of different management consulting firms. Now,

0:07:17.720 --> 0:07:22.120
<v Speaker 1>these were companies that were geared toward helping other companies

0:07:22.280 --> 0:07:26.880
<v Speaker 1>assess manager styles or figure out what a corporate culture

0:07:27.120 --> 0:07:31.160
<v Speaker 1>was within a certain business, to improve workplace efficiencies, that

0:07:31.240 --> 0:07:34.960
<v Speaker 1>kind of thing. I was essentially working for the Bobs

0:07:35.240 --> 0:07:37.760
<v Speaker 1>from Office Space. I guess you could say so if

0:07:37.760 --> 0:07:40.040
<v Speaker 1>you're familiar with that film and the two consultants who

0:07:40.040 --> 0:07:42.560
<v Speaker 1>come in and essentially start slashing jobs left and right.

0:07:43.280 --> 0:07:46.320
<v Speaker 1>I was kind of their employee in a roundabout way,

0:07:46.320 --> 0:07:51.960
<v Speaker 1>although we didn't typically advocate for slashing huge numbers off

0:07:52.000 --> 0:07:57.440
<v Speaker 1>of a corporate employee list. Occasionally, yes, but not frequently.

0:07:58.000 --> 0:08:01.640
<v Speaker 1>So my work was focused on help in consultants produce

0:08:01.840 --> 0:08:06.480
<v Speaker 1>proposals and reports. Largely, I was there to review, to proof,

0:08:06.480 --> 0:08:12.280
<v Speaker 1>freed to format, and occasionally to tweak stuff. Now I

0:08:12.480 --> 0:08:15.360
<v Speaker 1>majored in English Lit when I was in college. I

0:08:15.400 --> 0:08:20.480
<v Speaker 1>have a fairly extensive vocabulary, but frequently I would find

0:08:20.520 --> 0:08:24.920
<v Speaker 1>myself working on documents that were so full of jargon

0:08:25.480 --> 0:08:27.600
<v Speaker 1>that I would have to bring the documents over to

0:08:27.640 --> 0:08:31.400
<v Speaker 1>a consultant and say, what exactly do you mean when

0:08:31.440 --> 0:08:34.080
<v Speaker 1>you say this? You know, I would highlight a passage

0:08:34.120 --> 0:08:36.800
<v Speaker 1>and say what does this actually mean? Because I couldn't

0:08:36.840 --> 0:08:40.920
<v Speaker 1>really edit or produce documents if I didn't understand the

0:08:41.000 --> 0:08:44.160
<v Speaker 1>meaning because it might mean I could let something go

0:08:44.280 --> 0:08:47.760
<v Speaker 1>out of the office that was incorrect, and it was

0:08:47.800 --> 0:08:51.079
<v Speaker 1>incorrect because I didn't understand what was actually being meant

0:08:51.160 --> 0:08:55.640
<v Speaker 1>and whether or not the consultant was accurate in their language.

0:08:55.880 --> 0:08:57.920
<v Speaker 1>So I would have to talk with these consultants on

0:08:57.960 --> 0:08:59.880
<v Speaker 1>a very frank level and say, no, no, no, I

0:09:00.040 --> 0:09:03.600
<v Speaker 1>understand what each individual word means in this sentence, but

0:09:03.679 --> 0:09:06.560
<v Speaker 1>can you tell me what the overall meaning is? What

0:09:06.640 --> 0:09:09.320
<v Speaker 1>are you actually getting at when you say this? And

0:09:09.320 --> 0:09:11.599
<v Speaker 1>if they could tell me in plain English, then I

0:09:11.640 --> 0:09:14.720
<v Speaker 1>would ask them, so, why don't you say it that

0:09:14.760 --> 0:09:18.280
<v Speaker 1>way in this report? Why are you using language that

0:09:18.480 --> 0:09:23.360
<v Speaker 1>is so complicated or non intuitive that what you actually

0:09:23.400 --> 0:09:27.080
<v Speaker 1>mean is hidden by that language? What good does that

0:09:27.160 --> 0:09:30.840
<v Speaker 1>do you? My fear was that the consultants were writing

0:09:30.880 --> 0:09:33.920
<v Speaker 1>these reports in a way to kind of hide the

0:09:34.000 --> 0:09:38.160
<v Speaker 1>meaning because it gave them some wiggle room in the interpretations.

0:09:38.559 --> 0:09:42.120
<v Speaker 1>And I thought that was maybe a little disingenuous, Like

0:09:42.559 --> 0:09:44.960
<v Speaker 1>if you could word a report in such a way

0:09:45.000 --> 0:09:47.600
<v Speaker 1>that two different people could come away with two totally

0:09:47.600 --> 0:09:53.640
<v Speaker 1>different interpretations, and both interpretations are seemingly valid because you

0:09:53.720 --> 0:10:00.120
<v Speaker 1>were purposefully vague or Uh, using very weird jargon in

0:10:00.200 --> 0:10:03.440
<v Speaker 1>your descriptions, then you haven't really done your job. You

0:10:03.520 --> 0:10:06.800
<v Speaker 1>haven't actually helped them in any way, because no one

0:10:06.880 --> 0:10:10.040
<v Speaker 1>has any consensus on what to do next. So I

0:10:10.080 --> 0:10:14.000
<v Speaker 1>found it very frustrating working in that world. Well, the

0:10:14.040 --> 0:10:18.400
<v Speaker 1>same thing can happen with engineers, or really any profession

0:10:18.600 --> 0:10:22.280
<v Speaker 1>that has its own jargon, from medicine to law, to

0:10:22.520 --> 0:10:26.720
<v Speaker 1>science to content creation on the Internet. I've been to

0:10:26.880 --> 0:10:31.319
<v Speaker 1>plenty of meetings where there's been a lot of discussion

0:10:31.720 --> 0:10:35.240
<v Speaker 1>about things on the Internet, where I felt it was

0:10:35.280 --> 0:10:40.400
<v Speaker 1>being unnecessarily complicated, where people were talking about buckets and verticals,

0:10:40.440 --> 0:10:45.440
<v Speaker 1>and they're talking about all sorts of things and deliverables

0:10:45.440 --> 0:10:48.560
<v Speaker 1>and asking to dialogue with someone, And I kept thinking,

0:10:48.600 --> 0:10:51.880
<v Speaker 1>why are we using this language? There are other words

0:10:51.920 --> 0:10:55.520
<v Speaker 1>we can use that everyone understands, that will convey exactly

0:10:55.559 --> 0:11:02.079
<v Speaker 1>the meaning you you want, and yet we're progressively going

0:11:02.440 --> 0:11:08.040
<v Speaker 1>to this this weird quasi language that that has a

0:11:08.080 --> 0:11:10.880
<v Speaker 1>lot of ambiguity in it and therefore makes it harder

0:11:10.920 --> 0:11:14.800
<v Speaker 1>to understand the meaning anyway. That was really what this

0:11:14.840 --> 0:11:17.480
<v Speaker 1>piece was all about. There has to be a balance

0:11:17.920 --> 0:11:22.240
<v Speaker 1>between precision that you get with the specific language that

0:11:22.280 --> 0:11:25.800
<v Speaker 1>you were relying upon and clarity what you mean by

0:11:25.840 --> 0:11:29.120
<v Speaker 1>that language. So this piece by student John H. Quick

0:11:29.520 --> 0:11:33.760
<v Speaker 1>was really meant to raise the reliance of jargon two

0:11:33.880 --> 0:11:38.559
<v Speaker 1>ridiculous extremes, to say, if we really crank up the

0:11:38.679 --> 0:11:44.120
<v Speaker 1>jargon speak in a piece, you realize how silly it

0:11:44.200 --> 0:11:47.960
<v Speaker 1>can get. And the joke may well have died a

0:11:48.040 --> 0:11:51.400
<v Speaker 1>quiet death on its own, or maybe only been something

0:11:51.520 --> 0:11:55.840
<v Speaker 1>that engineers would joke about, just an inside joke among them,

0:11:55.880 --> 0:11:59.559
<v Speaker 1>if it hadn't been for Time Magazine. The Arthur d

0:12:00.000 --> 0:12:03.600
<v Speaker 1>Old Industrial Bulletin in the United States would take this

0:12:03.640 --> 0:12:06.959
<v Speaker 1>piece and publish it in ninety six, but that didn't

0:12:06.960 --> 0:12:10.800
<v Speaker 1>exactly hit mainstream readership. It did, however, get some attention

0:12:10.840 --> 0:12:15.280
<v Speaker 1>by people who would review technical documents, and in April

0:12:15.280 --> 0:12:18.280
<v Speaker 1>of that year, Time Magazine ran the piece with the

0:12:18.320 --> 0:12:22.400
<v Speaker 1>title for No for Trunnions. It was produced without an

0:12:22.400 --> 0:12:25.120
<v Speaker 1>overt nod that the whole thing was a wind up,

0:12:25.840 --> 0:12:28.400
<v Speaker 1>and the people at Time Magazine knew it was a joke,

0:12:28.600 --> 0:12:31.240
<v Speaker 1>but they were presenting it as if it were a

0:12:31.280 --> 0:12:36.040
<v Speaker 1>realistic document. Some readers were legitimately flabbergasted. They thought it

0:12:36.080 --> 0:12:39.280
<v Speaker 1>was meant as an actual example of engineering, but other

0:12:39.320 --> 0:12:41.719
<v Speaker 1>people actually picked up on the joke and ran with it.

0:12:42.240 --> 0:12:46.600
<v Speaker 1>Stanton Tompkins, for example, wrote to Time Magazine and included

0:12:46.640 --> 0:12:49.560
<v Speaker 1>the comment, may I add that if the bearings are

0:12:49.640 --> 0:12:54.439
<v Speaker 1>lubricated with warm smorch, they will not grune. Others added

0:12:54.480 --> 0:12:58.520
<v Speaker 1>equally nonsensical comments to push the joke further. One that's

0:12:58.559 --> 0:13:02.040
<v Speaker 1>frequently mentioned is from a guy named Ernest In Kerman.

0:13:02.120 --> 0:13:06.359
<v Speaker 1>He wrote in and said, after being advised and cerebral

0:13:06.440 --> 0:13:09.880
<v Speaker 1>lee malliated by one point five no fur trunnions from

0:13:09.880 --> 0:13:15.240
<v Speaker 1>a magitudinitative zero four or five one gmt to an

0:13:15.240 --> 0:13:19.800
<v Speaker 1>epin nocturnal proximate eleven fifty five e s T. I

0:13:19.880 --> 0:13:23.880
<v Speaker 1>felt the need of spiri in animating filiperative and therefore

0:13:24.000 --> 0:13:31.080
<v Speaker 1>submersonized my hypercincinate indoderm in a five percent Fijian nate

0:13:31.320 --> 0:13:39.080
<v Speaker 1>by Carbo la kai nat ing Kepsi pola little slightly

0:13:39.160 --> 0:13:42.760
<v Speaker 1>veiled pepsi cola reference. They're still The joke could have

0:13:42.800 --> 0:13:46.560
<v Speaker 1>faded away from memory after the Time Magazine piece weren't

0:13:46.559 --> 0:13:48.840
<v Speaker 1>not for the determination of a few jokesters in the

0:13:48.880 --> 0:13:51.400
<v Speaker 1>engineering world to give it a shot in the arm

0:13:51.440 --> 0:13:55.000
<v Speaker 1>every few decades. Like the instrument department at General Electric

0:13:55.200 --> 0:13:57.480
<v Speaker 1>they wrote up an entire data sheet on the fictional

0:13:57.520 --> 0:14:00.880
<v Speaker 1>turbo encabulator. More on that in just moment, but first

0:14:01.240 --> 0:14:13.120
<v Speaker 1>let's take a quick break. On December one, nineteen sixty two,

0:14:13.360 --> 0:14:16.880
<v Speaker 1>the Instrument Department at GE released a fact sheet on

0:14:16.920 --> 0:14:21.680
<v Speaker 1>the turbo encabulator. By the way, I've seen turbo encabulator

0:14:21.760 --> 0:14:24.800
<v Speaker 1>presented as both a single word and as two words

0:14:24.840 --> 0:14:29.880
<v Speaker 1>as turbo incabulator, so dealer's choice. I guess both appear

0:14:30.200 --> 0:14:36.240
<v Speaker 1>throughout engineering joke literature. The fact sheet, however, really helps

0:14:36.280 --> 0:14:39.680
<v Speaker 1>clear things up. For example, the function of the turbo

0:14:39.800 --> 0:14:43.160
<v Speaker 1>encabulator is made clear by this fact sheet. It's quote

0:14:43.520 --> 0:14:46.840
<v Speaker 1>to measure inverse reactive current in unilateral phase detractors with

0:14:46.920 --> 0:14:52.120
<v Speaker 1>a display of percent realization end quote. So finally we

0:14:52.200 --> 0:14:55.240
<v Speaker 1>know what's going on, right. Much of the fact sheet

0:14:55.520 --> 0:14:59.520
<v Speaker 1>is drawn directly from Quick's description of the turbo encabulator

0:14:59.560 --> 0:15:05.840
<v Speaker 1>from back. Other parts gleefully build upon the nonsense. For example,

0:15:06.040 --> 0:15:08.280
<v Speaker 1>there is a section on the fact sheet about the

0:15:08.280 --> 0:15:12.560
<v Speaker 1>application of the device that reads, quote caution because of

0:15:12.600 --> 0:15:18.000
<v Speaker 1>the replenorative flow characteristics of positive ions and unilateral phase detractors,

0:15:18.040 --> 0:15:22.080
<v Speaker 1>the use of quasi static regeneration oscillator is recommended if

0:15:22.120 --> 0:15:26.480
<v Speaker 1>turbo encabulator is used in explosive atmospheres. End quote. The

0:15:26.480 --> 0:15:30.040
<v Speaker 1>fact sheet actually includes an image of the supposed device,

0:15:30.840 --> 0:15:34.440
<v Speaker 1>the first image that I could actually find on record

0:15:35.040 --> 0:15:36.920
<v Speaker 1>this version. If you were to look at it looks

0:15:36.960 --> 0:15:39.680
<v Speaker 1>kind of like a cylinder mounted on its side on

0:15:39.760 --> 0:15:43.200
<v Speaker 1>a small stand, so think of like a like a

0:15:43.240 --> 0:15:46.200
<v Speaker 1>water bottle, but you have it on its side. On

0:15:46.200 --> 0:15:49.080
<v Speaker 1>one end of this cylinder is a fan that sticks

0:15:49.080 --> 0:15:51.440
<v Speaker 1>out of the end. There's a length of piping that

0:15:51.480 --> 0:15:55.520
<v Speaker 1>stretches across the top of the turbo encabulator, so again

0:15:55.560 --> 0:15:57.520
<v Speaker 1>like it would be the side of the cylinder, but

0:15:57.600 --> 0:16:00.800
<v Speaker 1>the top of the device. And there's some other details

0:16:00.840 --> 0:16:02.800
<v Speaker 1>on this as well, although it's hard to make out

0:16:02.920 --> 0:16:06.520
<v Speaker 1>because I've only seen scans of the original document and

0:16:06.520 --> 0:16:08.840
<v Speaker 1>they tend to be pretty low quality scans, so it's

0:16:08.840 --> 0:16:12.160
<v Speaker 1>hard to make out details. The entire write up followed

0:16:12.160 --> 0:16:16.040
<v Speaker 1>the format of official g E standards for product documentation,

0:16:16.600 --> 0:16:19.680
<v Speaker 1>so the people who made this actually made it so

0:16:19.760 --> 0:16:25.400
<v Speaker 1>it looked exactly like any standard g E documentation. They

0:16:25.480 --> 0:16:28.520
<v Speaker 1>followed all the rules and it was inserted into the

0:16:28.600 --> 0:16:33.200
<v Speaker 1>official GE handbook. Now I'm sure that those who painstaking

0:16:33.360 --> 0:16:37.160
<v Speaker 1>lee read through the entire handbook were amused or maybe

0:16:37.200 --> 0:16:40.520
<v Speaker 1>befuddled by the joke. Also, I feel this is a

0:16:40.520 --> 0:16:43.200
<v Speaker 1>good place to say that it pays to read through

0:16:43.640 --> 0:16:46.800
<v Speaker 1>employee handbooks because you never know when someone's going to

0:16:46.840 --> 0:16:49.480
<v Speaker 1>slip in a joke. And as someone who has actually

0:16:49.520 --> 0:16:52.920
<v Speaker 1>designed employee handbooks in the past, I'd also say it

0:16:53.000 --> 0:16:57.760
<v Speaker 1>is incredibly satisfying to put jokes into official materials, you know,

0:16:57.840 --> 0:17:00.480
<v Speaker 1>so long as those jokes aren't going to backfire on you.

0:17:00.600 --> 0:17:03.600
<v Speaker 1>So I would actually recommend getting official approval before getting

0:17:03.600 --> 0:17:07.720
<v Speaker 1>wacky with the official handbook. It is good to see

0:17:07.720 --> 0:17:11.680
<v Speaker 1>why a in those cases. Still, at this point, we're

0:17:11.720 --> 0:17:18.240
<v Speaker 1>talking about print representations of this ridiculous notion. In ninety seven,

0:17:18.480 --> 0:17:22.479
<v Speaker 1>the Turbo Encabulator made the transition from page to screen.

0:17:22.880 --> 0:17:25.960
<v Speaker 1>An actor named Bud Haggart, who was well known for

0:17:26.119 --> 0:17:30.320
<v Speaker 1>voiceover and industrial film performances, took on the role of

0:17:30.359 --> 0:17:34.080
<v Speaker 1>an engineer delivering a matter of fact explanation of the

0:17:34.080 --> 0:17:38.480
<v Speaker 1>turbo Encabulator. The script was nearly word for word Quick's

0:17:38.520 --> 0:17:42.080
<v Speaker 1>original piece in ninety four. It was edited a bit

0:17:42.320 --> 0:17:45.040
<v Speaker 1>but had essentially the same flow, and it was helped

0:17:45.080 --> 0:17:48.960
<v Speaker 1>with meaningless diagrams and sketches that Haggard would point to

0:17:49.080 --> 0:17:53.200
<v Speaker 1>throughout his delivery as if he was actually pointing at

0:17:53.240 --> 0:17:58.480
<v Speaker 1>the physical components of this fictional device. His tone and

0:17:58.560 --> 0:18:01.240
<v Speaker 1>approach made it so like he was talking about something

0:18:01.240 --> 0:18:05.280
<v Speaker 1>that any kid could understand with relative ease. It was brilliant.

0:18:06.200 --> 0:18:10.600
<v Speaker 1>According to Internet lore, Hanard proposed doing the short as

0:18:10.720 --> 0:18:14.000
<v Speaker 1>an add on after an official short film for GMC

0:18:15.080 --> 0:18:18.679
<v Speaker 1>was shot. It was an industrial film about one of

0:18:18.680 --> 0:18:22.280
<v Speaker 1>their truck lines. So he goes in. He does this

0:18:23.040 --> 0:18:27.480
<v Speaker 1>commercial shoot for GMC about their truck lines, and he

0:18:27.600 --> 0:18:29.880
<v Speaker 1>works with the film crew, and then afterwards he takes

0:18:29.880 --> 0:18:32.280
<v Speaker 1>the film crew aside. He talks to the director, whose

0:18:32.320 --> 0:18:35.359
<v Speaker 1>name was Dave Ron Dutt, and he asks them to

0:18:35.480 --> 0:18:39.240
<v Speaker 1>stay after so that he might shoot a short film

0:18:39.840 --> 0:18:43.840
<v Speaker 1>that is based off the turbo encabulator piece. Haggard had

0:18:43.840 --> 0:18:48.440
<v Speaker 1>actually written the script based on that n article and

0:18:48.640 --> 0:18:52.119
<v Speaker 1>made it something that he could create a presentation out of.

0:18:52.800 --> 0:18:57.840
<v Speaker 1>And industrial films were something of a of a big

0:18:57.920 --> 0:19:00.760
<v Speaker 1>deal in the seventies and eighties, and they could actually

0:19:00.840 --> 0:19:04.360
<v Speaker 1>make the rounds within an industry. So this nineteen seventies

0:19:04.400 --> 0:19:08.880
<v Speaker 1>seven fake industrial film that Haggard made made the rounds,

0:19:09.000 --> 0:19:12.199
<v Speaker 1>and some folks over at Chrysler saw it. So in

0:19:13.440 --> 0:19:16.880
<v Speaker 1>Chrysler hired Haggard to come over and shoot a new

0:19:17.000 --> 0:19:22.280
<v Speaker 1>version of his turbo encabulator presentation at Chrysler's facility, and

0:19:22.640 --> 0:19:25.240
<v Speaker 1>it was purporting to be a new product from the

0:19:25.320 --> 0:19:29.160
<v Speaker 1>auto company. In this case, he had some actual machinery

0:19:29.400 --> 0:19:32.679
<v Speaker 1>to gesture toward while delivering his presentation, but none of

0:19:32.680 --> 0:19:35.240
<v Speaker 1>the things he was pointing to had anything to do

0:19:35.400 --> 0:19:40.320
<v Speaker 1>with what he was actually saying. Cat's cuttle fish to

0:19:40.400 --> 0:19:45.080
<v Speaker 1>the second oil age and his kingdom with fur of darkness.

0:19:45.080 --> 0:19:49.840
<v Speaker 1>I don't dispute the eurostata, but if he's down here,

0:19:50.080 --> 0:19:58.040
<v Speaker 1>not blood but darkness, the earth's black riches, I could

0:19:58.040 --> 0:20:02.200
<v Speaker 1>taste it on my lips. Today, I want to talk

0:20:02.240 --> 0:20:16.119
<v Speaker 1>to you about the science of transgenesis Genesis time show. WHOA.

0:20:17.840 --> 0:20:20.639
<v Speaker 1>I'm not sure what what happened just there? That was

0:20:21.560 --> 0:20:27.840
<v Speaker 1>That was odd um? All right? Well, getting back into

0:20:27.880 --> 0:20:34.240
<v Speaker 1>it talking about the films. Both the original video or

0:20:34.320 --> 0:20:37.240
<v Speaker 1>film rather that Haggard shot and the Chrysler version of

0:20:37.280 --> 0:20:40.439
<v Speaker 1>the presentation are available online. You can watch both of

0:20:40.480 --> 0:20:42.800
<v Speaker 1>them and you can find them on YouTube. You can

0:20:42.840 --> 0:20:45.159
<v Speaker 1>find them on other platforms as well, And there is

0:20:46.040 --> 0:20:50.240
<v Speaker 1>no way at all that I could deliver the techno

0:20:50.280 --> 0:20:54.400
<v Speaker 1>babble with the same dead pan skill as Mr Haggard.

0:20:54.520 --> 0:20:59.320
<v Speaker 1>It is a masterpiece of dead pan humor. It's also

0:20:59.359 --> 0:21:02.439
<v Speaker 1>pretty clear that he wasn't using any Q cards or

0:21:02.480 --> 0:21:05.959
<v Speaker 1>a teleprompter. His eyes hold steady the entire time. They

0:21:05.960 --> 0:21:09.280
<v Speaker 1>don't have the tell tale scanning motions you get when

0:21:09.320 --> 0:21:12.680
<v Speaker 1>you're watching someone who's reading from Q cards or a teleprompter.

0:21:13.000 --> 0:21:15.680
<v Speaker 1>If you've ever watched Saturday Night Live, if you ever

0:21:15.720 --> 0:21:19.320
<v Speaker 1>even watched videos that I have done. I've done several

0:21:19.400 --> 0:21:22.600
<v Speaker 1>videos without a teleprompter, and I've done videos with teleprompters.

0:21:22.640 --> 0:21:24.600
<v Speaker 1>And if you watch my eyes, you can tell which

0:21:24.600 --> 0:21:27.440
<v Speaker 1>one you're seeing because you can see that I'm actually

0:21:27.440 --> 0:21:29.720
<v Speaker 1>reading something on the teleprompter one. So I get really

0:21:29.720 --> 0:21:32.159
<v Speaker 1>sensitive to this kind of thing. I notice it pretty quickly,

0:21:32.200 --> 0:21:35.080
<v Speaker 1>I think most people do, but it jumps out at me.

0:21:35.600 --> 0:21:37.199
<v Speaker 1>So I wondered at first how he did it, Like,

0:21:37.240 --> 0:21:43.440
<v Speaker 1>how did he actually memorize this incredibly dense list of jargon. Well,

0:21:43.440 --> 0:21:46.680
<v Speaker 1>according to the director Ron Dot, the nineteen seventy seven

0:21:46.800 --> 0:21:50.040
<v Speaker 1>version was done with an audio prompter. It was a

0:21:50.080 --> 0:21:54.240
<v Speaker 1>wired earpiece that connected to a real to real tape recorder.

0:21:54.920 --> 0:21:59.600
<v Speaker 1>Uh so Haggard had gone and recorded the entire speech

0:21:59.720 --> 0:22:02.720
<v Speaker 1>on to the reel to reel and he used the

0:22:02.760 --> 0:22:06.600
<v Speaker 1>earpiece as a prompter for himself. Now, I can't imagine

0:22:06.640 --> 0:22:10.000
<v Speaker 1>how difficult that was to do at pace where you're

0:22:10.040 --> 0:22:12.560
<v Speaker 1>delivering it right after you're hearing it. Because if you've

0:22:12.560 --> 0:22:16.360
<v Speaker 1>ever tried to speak well hearing your own audio, you

0:22:16.440 --> 0:22:18.520
<v Speaker 1>know that that can get really difficult. You can find

0:22:18.560 --> 0:22:22.960
<v Speaker 1>it very disorienting and disconcerting. So maybe he practiced it

0:22:23.080 --> 0:22:26.359
<v Speaker 1>enough to speak the piece in time with the recorded version,

0:22:26.440 --> 0:22:28.560
<v Speaker 1>sort of like singing along to the radio when a

0:22:28.640 --> 0:22:31.479
<v Speaker 1>song is playing, you might find that, oh, I know

0:22:31.600 --> 0:22:33.960
<v Speaker 1>all the lyrics when I sing along to the radio,

0:22:34.160 --> 0:22:35.919
<v Speaker 1>but if you asked me to try and sing the

0:22:36.000 --> 0:22:39.320
<v Speaker 1>lyrics on my own without the song playing, suddenly I

0:22:39.359 --> 0:22:41.600
<v Speaker 1>start having trouble. Maybe it was something like that, I

0:22:41.640 --> 0:22:44.800
<v Speaker 1>don't know. The Chrysler video has a follow up part

0:22:45.359 --> 0:22:48.320
<v Speaker 1>and there's another actor who talks about the diagnosis and

0:22:48.440 --> 0:22:52.639
<v Speaker 1>service of the turbo encabulator. That segment includes even more

0:22:52.880 --> 0:22:56.520
<v Speaker 1>techno babble and jargon, adding yet more complexity to the

0:22:56.600 --> 0:22:58.760
<v Speaker 1>overall joke. Now, I'm not going to go into the

0:22:58.760 --> 0:23:01.520
<v Speaker 1>whole script like I did with the original publication, but

0:23:01.560 --> 0:23:03.600
<v Speaker 1>I do want to point out a couple of favorite

0:23:03.640 --> 0:23:08.359
<v Speaker 1>parts of mine. The presenter says, for the purposes of obscurity,

0:23:08.520 --> 0:23:11.000
<v Speaker 1>we have removed the casing to expose the heart of

0:23:11.040 --> 0:23:15.600
<v Speaker 1>the turbo encabulator, the magneto reluctance modial interactor. Since little

0:23:15.680 --> 0:23:19.000
<v Speaker 1>or nothing is known about the principles involved in magneto reluctance,

0:23:19.200 --> 0:23:23.440
<v Speaker 1>diagnosing faults can be a problem that to me is

0:23:23.480 --> 0:23:26.400
<v Speaker 1>absolutely hysterical. The notion that we have built an important

0:23:26.400 --> 0:23:30.159
<v Speaker 1>piece of technology without an understanding of the underlying science

0:23:30.200 --> 0:23:33.400
<v Speaker 1>that makes it work is already pretty amusing. So yeah,

0:23:33.400 --> 0:23:35.639
<v Speaker 1>if you don't understand how something works, how would you

0:23:35.680 --> 0:23:39.200
<v Speaker 1>know when something is wrong. There's also a terrible pun

0:23:39.320 --> 0:23:42.400
<v Speaker 1>in that segment, in which the presenter says a diagnostic

0:23:42.440 --> 0:23:46.440
<v Speaker 1>tool will display any faults in code, adding quote it's

0:23:46.440 --> 0:23:49.719
<v Speaker 1>a simple head code. Anyone can catch it end quote

0:23:50.160 --> 0:23:52.439
<v Speaker 1>That in turn might be a bit of a joke theft,

0:23:52.880 --> 0:23:57.000
<v Speaker 1>because I actually recall that the absurdist radio comedy group

0:23:57.040 --> 0:24:00.399
<v Speaker 1>Fire Sign Theater had a similar joke about a simple

0:24:00.440 --> 0:24:05.040
<v Speaker 1>schoolboy code that anyone could catch. In general, the Chrysler

0:24:05.119 --> 0:24:07.480
<v Speaker 1>video makes it more apparent that the whole thing is

0:24:07.520 --> 0:24:11.800
<v Speaker 1>done for laughs. It is less of a uh, it's

0:24:11.840 --> 0:24:15.520
<v Speaker 1>it's less done as a serious piece the original piece.

0:24:15.840 --> 0:24:19.119
<v Speaker 1>If you didn't know better, if you were completely naive

0:24:19.240 --> 0:24:22.679
<v Speaker 1>about engineering, you might think, while this is just I

0:24:22.720 --> 0:24:24.679
<v Speaker 1>don't understand any of it. I have no idea what

0:24:24.720 --> 0:24:28.240
<v Speaker 1>this thing does. But if you know what he's talking about,

0:24:28.320 --> 0:24:30.440
<v Speaker 1>or at least no enough to know that it's nonsense,

0:24:30.480 --> 0:24:33.000
<v Speaker 1>then it's a joke. Well, in this case, the Chrysler

0:24:33.080 --> 0:24:37.160
<v Speaker 1>version is more obviously a joke. Another video that will

0:24:37.160 --> 0:24:40.120
<v Speaker 1>pop up if you search for turbo encabulator is from

0:24:40.320 --> 0:24:45.359
<v Speaker 1>Rockwell Automation, produced in nine, which tells us that seems

0:24:45.400 --> 0:24:47.440
<v Speaker 1>like we get a new version every decade or so,

0:24:47.480 --> 0:24:50.200
<v Speaker 1>because the first one came out in nineteen seventy seven,

0:24:50.240 --> 0:24:52.919
<v Speaker 1>the next one came out in the late eighties, and

0:24:52.960 --> 0:24:55.920
<v Speaker 1>then you have nine or so for the third one.

0:24:56.400 --> 0:25:00.280
<v Speaker 1>The company Rockwell Automation started at the big ending of

0:25:00.320 --> 0:25:03.920
<v Speaker 1>the twentieth century, a different company name, but what would

0:25:03.920 --> 0:25:07.000
<v Speaker 1>evolve into Rockwell Automation traces its history back that far.

0:25:07.600 --> 0:25:11.840
<v Speaker 1>The company creates industrial automation technology for other companies, so

0:25:11.880 --> 0:25:14.720
<v Speaker 1>it's not exactly the place you would expect to find humor.

0:25:14.840 --> 0:25:17.639
<v Speaker 1>But Rockwell produced their own video in the spirit of

0:25:17.680 --> 0:25:22.399
<v Speaker 1>the Turbo Encabulator, this time called the Retro Encabulator. Actor

0:25:22.520 --> 0:25:25.600
<v Speaker 1>Mike Craft served as the host of the video, and

0:25:25.680 --> 0:25:29.520
<v Speaker 1>Craft had done presentations at industry conferences and events on

0:25:29.560 --> 0:25:33.480
<v Speaker 1>behalf of companies like Alan Bradley for years. Craft had

0:25:33.480 --> 0:25:37.160
<v Speaker 1>discovered the Bud Haggart piece many years earlier and had

0:25:37.160 --> 0:25:39.800
<v Speaker 1>memorized it, and I didn't realize it at first when

0:25:39.840 --> 0:25:42.440
<v Speaker 1>I was watching it. But Craft also was the repair

0:25:42.520 --> 0:25:46.440
<v Speaker 1>technician who did the follow up segment in Haggart's Chrysler video,

0:25:46.520 --> 0:25:49.040
<v Speaker 1>so he actually got to work with Bud Haggart at

0:25:49.080 --> 0:25:52.200
<v Speaker 1>Chrysler and then was able to do the full presentation

0:25:52.440 --> 0:25:56.920
<v Speaker 1>over at Rockwell. Also, like Haggard, Craft used an ear prompter,

0:25:57.200 --> 0:25:59.600
<v Speaker 1>although at this point we were talking about a wireless one,

0:25:59.640 --> 0:26:03.000
<v Speaker 1>not a fired one. Like the Chrysler video, the Rockwell

0:26:03.040 --> 0:26:06.639
<v Speaker 1>one makes use of actual devices to illustrate the point.

0:26:07.119 --> 0:26:11.199
<v Speaker 1>With Chrysler, the device would be like transmission parts, you know,

0:26:11.240 --> 0:26:14.399
<v Speaker 1>they were car parts, but with Rockwell it was actually

0:26:14.440 --> 0:26:18.680
<v Speaker 1>electrical wall panels. That Craft was opening up and using

0:26:18.720 --> 0:26:22.800
<v Speaker 1>to illustrate his fictional points. The video also featured shoutouts

0:26:22.800 --> 0:26:27.280
<v Speaker 1>to Rockwell customers like Dodge, Alan Bradley and Alliance Electric,

0:26:27.880 --> 0:26:30.840
<v Speaker 1>and claiming that the incabulator was really a joint effort

0:26:30.880 --> 0:26:33.800
<v Speaker 1>between these different companies, but the description of the device

0:26:33.920 --> 0:26:37.520
<v Speaker 1>was again largely the same as the original nineteen forty

0:26:37.560 --> 0:26:41.520
<v Speaker 1>four Right up, and you should check out retro incabulator

0:26:41.680 --> 0:26:45.520
<v Speaker 1>dot com because you'll be directed to Mic Craft's acting website.

0:26:45.840 --> 0:26:49.000
<v Speaker 1>The joke survives to this day with side shows Hank

0:26:49.119 --> 0:26:52.280
<v Speaker 1>Green delivering a performance just a few years ago, I

0:26:52.280 --> 0:26:54.919
<v Speaker 1>think two thousand thirteen, and there was an April Fool's

0:26:54.960 --> 0:26:57.919
<v Speaker 1>Day joke and he again delivers it exactly the way

0:26:57.960 --> 0:27:00.359
<v Speaker 1>you would expect Hank Green to do it per lely,

0:27:00.800 --> 0:27:02.840
<v Speaker 1>and it does a masterful job as well. Those of

0:27:02.840 --> 0:27:05.480
<v Speaker 1>you who remember my series Forward Thinking, you might be

0:27:05.520 --> 0:27:09.119
<v Speaker 1>amused to know that our series director, Dan Bush wanted

0:27:09.160 --> 0:27:12.000
<v Speaker 1>me to do a version of the turbo encabulator as

0:27:12.040 --> 0:27:14.280
<v Speaker 1>an April Fool's joke for the show, to do a

0:27:14.359 --> 0:27:18.240
<v Speaker 1>full Forward Thinking episode about the turbo encabulator. We never

0:27:18.320 --> 0:27:21.480
<v Speaker 1>could get clear approval to move forward on that, so

0:27:21.640 --> 0:27:25.119
<v Speaker 1>it never happened. I guess I should be thankful, because

0:27:25.200 --> 0:27:28.520
<v Speaker 1>I'm absolutely certain shooting a video version of that would

0:27:28.560 --> 0:27:32.000
<v Speaker 1>have required countless takes to get it right. In fact,

0:27:32.040 --> 0:27:34.159
<v Speaker 1>I imagine I would still be in the studio today

0:27:34.359 --> 0:27:37.080
<v Speaker 1>if that were the case. So that's the story about

0:27:37.080 --> 0:27:40.800
<v Speaker 1>the turbo encabulator. But I've got more to say about

0:27:40.920 --> 0:27:44.280
<v Speaker 1>jargon and techno babble in just a moment. But let's

0:27:44.320 --> 0:27:54.439
<v Speaker 1>take another quick break, all right, So let's talk a

0:27:54.480 --> 0:27:58.719
<v Speaker 1>bit about techno babble or sometimes known as techno speak,

0:27:59.000 --> 0:28:02.359
<v Speaker 1>which you could call a trope. Trope means a couple

0:28:02.359 --> 0:28:04.879
<v Speaker 1>of different things. Yes, I should really define what I

0:28:04.920 --> 0:28:07.680
<v Speaker 1>mean by it, since I'm talking all about being precise

0:28:07.800 --> 0:28:11.080
<v Speaker 1>and clear. So in this case, a trope, as I'm

0:28:11.160 --> 0:28:14.520
<v Speaker 1>I'm using it, refers to some sort of common literary

0:28:14.600 --> 0:28:18.520
<v Speaker 1>or rhetorical device, something that is used frequently enough to

0:28:18.520 --> 0:28:22.479
<v Speaker 1>be part of a common language or even a cliche. Uh,

0:28:22.680 --> 0:28:24.760
<v Speaker 1>it doesn't even have to be language. It can be

0:28:25.160 --> 0:28:28.520
<v Speaker 1>a specific sort of events. So a horror movie trope,

0:28:28.800 --> 0:28:31.159
<v Speaker 1>a very common horror movie trope might be something like

0:28:31.840 --> 0:28:34.439
<v Speaker 1>let's split up. You see that in horror movies all

0:28:34.480 --> 0:28:37.240
<v Speaker 1>the time. You already know what that means. When when

0:28:37.320 --> 0:28:40.240
<v Speaker 1>characters say let's split up, you know that means that

0:28:40.320 --> 0:28:44.160
<v Speaker 1>whatever the the antagonist is in the horror movie, whether

0:28:44.200 --> 0:28:48.600
<v Speaker 1>it's a slasher or a ghost or goblins or whatever

0:28:48.640 --> 0:28:51.920
<v Speaker 1>it might be, they're gonna get somebody because they split

0:28:52.040 --> 0:28:55.880
<v Speaker 1>up and they're more vulnerable. So splitting up is always

0:28:55.880 --> 0:28:57.760
<v Speaker 1>a great idea in the context of a horror movie.

0:28:57.760 --> 0:29:00.760
<v Speaker 1>And you can subvert tropes too. You don't have to

0:29:00.840 --> 0:29:03.720
<v Speaker 1>just fulfill tropes. You could do a horror movie where

0:29:03.720 --> 0:29:06.200
<v Speaker 1>you say let's split up. Everyone splits up, and then

0:29:06.240 --> 0:29:09.040
<v Speaker 1>everyone is fine until they get back together again. Then

0:29:09.080 --> 0:29:13.120
<v Speaker 1>you have subverted the trope. But that you're you're depending

0:29:13.120 --> 0:29:15.920
<v Speaker 1>on the audience being aware that there is a trope,

0:29:16.240 --> 0:29:20.320
<v Speaker 1>that you have subverted their expectations. But the reason they

0:29:20.320 --> 0:29:23.000
<v Speaker 1>have the expectations is because the trope existed in the

0:29:23.040 --> 0:29:27.520
<v Speaker 1>first place. So techno speak is one of those devices

0:29:27.680 --> 0:29:30.880
<v Speaker 1>used by writers to create what sounds like a sophisticated

0:29:31.000 --> 0:29:35.400
<v Speaker 1>explanation of a technology but tends to be total nonsense,

0:29:35.920 --> 0:29:39.600
<v Speaker 1>or the very least is overly complicated and verbose. So

0:29:39.640 --> 0:29:42.360
<v Speaker 1>I thought I would include some of my favorite examples

0:29:42.680 --> 0:29:46.240
<v Speaker 1>and include a little context as well, and I don't

0:29:46.280 --> 0:29:49.200
<v Speaker 1>want to cast too much shade here. It is really

0:29:49.280 --> 0:29:53.680
<v Speaker 1>challenging to write science fiction in a believable way because

0:29:53.680 --> 0:29:57.760
<v Speaker 1>you're typically describing things that don't exist in our real world.

0:29:58.760 --> 0:30:01.440
<v Speaker 1>Maybe they exist in some warm but you're talking about

0:30:01.480 --> 0:30:04.160
<v Speaker 1>a more advanced version, or maybe you're talking about a

0:30:04.160 --> 0:30:07.360
<v Speaker 1>brand new technology that has no basis in reality as

0:30:07.520 --> 0:30:10.240
<v Speaker 1>as it stands right now, and you have to find

0:30:10.240 --> 0:30:12.480
<v Speaker 1>words to describe it. And you don't want it to

0:30:12.520 --> 0:30:15.880
<v Speaker 1>sound like Caveman trying to describe television. You want to

0:30:15.960 --> 0:30:19.440
<v Speaker 1>sound like it exists within the time and place that

0:30:19.520 --> 0:30:22.520
<v Speaker 1>you have set your story. So you have to have

0:30:22.600 --> 0:30:26.160
<v Speaker 1>that balance. How do you create words and phrases that

0:30:26.400 --> 0:30:30.840
<v Speaker 1>have meaning within your world and aren't just seen as

0:30:30.880 --> 0:30:34.320
<v Speaker 1>being complete nonsense to everybody else. I don't have the

0:30:34.320 --> 0:30:36.440
<v Speaker 1>answer to that question, By the way. This is a

0:30:36.480 --> 0:30:40.640
<v Speaker 1>hard thing to do. So there's some stiff competition around

0:30:40.720 --> 0:30:45.360
<v Speaker 1>various franchises for the most frequent use of techno speak. Now,

0:30:45.440 --> 0:30:48.880
<v Speaker 1>I personally would give the trophy over to the Star

0:30:48.960 --> 0:30:53.840
<v Speaker 1>Trek franchise, not the original series so much because I

0:30:53.920 --> 0:30:56.480
<v Speaker 1>believe it or not, Star Trek the original series wasn't

0:30:56.560 --> 0:31:00.760
<v Speaker 1>quite so flagrant about throwing around jargon. You got some,

0:31:01.280 --> 0:31:04.600
<v Speaker 1>but not tons of it. It wasn't like it was really,

0:31:05.280 --> 0:31:08.680
<v Speaker 1>you know ingrained in every single episode. The show did

0:31:08.760 --> 0:31:15.400
<v Speaker 1>feature fictional technologies like warp drives, phasers, transporters, those sort

0:31:15.440 --> 0:31:18.360
<v Speaker 1>of things, but you didn't get a lot of techno

0:31:18.400 --> 0:31:21.440
<v Speaker 1>babble about those things. You might just get fire the phasers.

0:31:22.600 --> 0:31:26.960
<v Speaker 1>Then Star Trek the Next Generation debuted, and initially it

0:31:27.040 --> 0:31:30.120
<v Speaker 1>was similar to the original series, and it was fairly

0:31:30.240 --> 0:31:34.520
<v Speaker 1>light on techno speak. But then after the series creator

0:31:34.600 --> 0:31:38.240
<v Speaker 1>Gene Roddenberry passed away, and after the Star Trek Technical

0:31:38.280 --> 0:31:43.680
<v Speaker 1>Manual came out. The technical manual attempted to give valid

0:31:43.720 --> 0:31:46.760
<v Speaker 1>explanations for how all the technology and Star Trek the

0:31:46.760 --> 0:31:51.360
<v Speaker 1>Next Generation actually worked, which meant it was largely a

0:31:51.440 --> 0:31:54.560
<v Speaker 1>work of speculative fiction in of itself. Once those two

0:31:54.640 --> 0:31:58.120
<v Speaker 1>things happened, writers began to insert more and more techno

0:31:58.160 --> 0:32:01.800
<v Speaker 1>babble into the show. And, like I said, it's a

0:32:01.800 --> 0:32:04.440
<v Speaker 1>pretty tough gig. You They had to describe technology that

0:32:04.480 --> 0:32:08.440
<v Speaker 1>would exist centuries from today. It's hard enough to predict

0:32:08.480 --> 0:32:11.200
<v Speaker 1>what's going to happen in five years. Anyone who's listened

0:32:11.240 --> 0:32:15.880
<v Speaker 1>to my technology prediction episodes. Know that it's hard enough

0:32:15.920 --> 0:32:18.040
<v Speaker 1>to describe what's going to happen in the next year,

0:32:18.160 --> 0:32:21.440
<v Speaker 1>let alone three hundred years from now, and so there

0:32:21.520 --> 0:32:25.280
<v Speaker 1>was some imaginative use of terminology that was necessary, but

0:32:25.280 --> 0:32:27.560
<v Speaker 1>the writers kind of went a little nutty with it

0:32:27.640 --> 0:32:30.240
<v Speaker 1>in the later seasons of the Next Generation and then

0:32:30.240 --> 0:32:34.440
<v Speaker 1>the following Star Trek series. I haven't gone through every

0:32:34.520 --> 0:32:37.040
<v Speaker 1>episode of the Next Generation to keep it tally, but

0:32:37.120 --> 0:32:39.440
<v Speaker 1>the example that always leaps to my mind with Star

0:32:39.480 --> 0:32:44.080
<v Speaker 1>Trek the Next Generation is the ubiquitous reverse the polarity.

0:32:44.400 --> 0:32:46.880
<v Speaker 1>The phrase was used as sort of a get out

0:32:46.920 --> 0:32:51.080
<v Speaker 1>of crisis free card on episodes where the usual approach,

0:32:51.160 --> 0:32:54.960
<v Speaker 1>whatever that might be, wasn't working. So, for example, if

0:32:54.960 --> 0:32:59.160
<v Speaker 1>the Enterprise encountered an enemy Borg vessel that was attacking,

0:32:59.520 --> 0:33:02.720
<v Speaker 1>the bridge, crew might try to reverse the polarity on

0:33:02.760 --> 0:33:05.920
<v Speaker 1>the ship's shields to help repel the attack. Now, to

0:33:06.000 --> 0:33:09.640
<v Speaker 1>be fair, the Star Trek writers didn't invent the idea

0:33:09.760 --> 0:33:13.400
<v Speaker 1>of reversing the polarity. It had already had a distinguished

0:33:13.520 --> 0:33:18.520
<v Speaker 1>run on the venerable UK series Doctor Who. Fans of

0:33:18.680 --> 0:33:21.880
<v Speaker 1>classic Doctor Who, I'm talking about Doctor Who before the

0:33:21.960 --> 0:33:25.840
<v Speaker 1>reboot with Eccleston and Tennant and all the rest. You

0:33:25.920 --> 0:33:30.320
<v Speaker 1>might remember John Pertwee, who played the third doctor in

0:33:30.320 --> 0:33:34.920
<v Speaker 1>the series. Reverse the polarity and later on, reverse the

0:33:34.960 --> 0:33:39.120
<v Speaker 1>polarity of the neutron flow became a common phrase in

0:33:39.240 --> 0:33:43.880
<v Speaker 1>Doctor Who episodes, finding its way across multiple doctors as

0:33:43.920 --> 0:33:48.600
<v Speaker 1>the series continued, including doctors after the reboot. Peter Capaldi's

0:33:48.640 --> 0:33:51.960
<v Speaker 1>doctor even subverted this trope in an episode in which

0:33:52.000 --> 0:33:55.240
<v Speaker 1>he said, quote, reverse the polarity of the neutron flow.

0:33:55.560 --> 0:33:59.000
<v Speaker 1>I bet that means something. It sounds great end quote.

0:33:59.320 --> 0:34:01.480
<v Speaker 1>One of the critics is ms I've seen about Star

0:34:01.600 --> 0:34:05.479
<v Speaker 1>Trek in general was that the reliance on meaningless techno

0:34:05.560 --> 0:34:09.600
<v Speaker 1>speak acted as sort of a dios x makina literally

0:34:09.800 --> 0:34:12.440
<v Speaker 1>in this sense, to get the crew out of danger

0:34:12.760 --> 0:34:15.279
<v Speaker 1>without actually coming up with an approach that has any

0:34:15.360 --> 0:34:19.279
<v Speaker 1>relevant meaning to the audience. Essentially, it was saying, the

0:34:19.360 --> 0:34:22.080
<v Speaker 1>thing you're doing isn't working. Do the thing you're doing,

0:34:22.120 --> 0:34:25.640
<v Speaker 1>but do it differently. I did the thing differently, it worked,

0:34:26.160 --> 0:34:29.160
<v Speaker 1>we got away. That's not very satisfying once you strip

0:34:29.200 --> 0:34:31.799
<v Speaker 1>away the techno babble. The techno babble helped kind of

0:34:31.880 --> 0:34:37.880
<v Speaker 1>hide the weakness of that resolution. Other examples included routing

0:34:37.880 --> 0:34:41.000
<v Speaker 1>an inverse takeion pulse through the main deflector dish that

0:34:41.040 --> 0:34:44.440
<v Speaker 1>makes no sense of Tachyon is a hypothetical particle that

0:34:44.480 --> 0:34:46.360
<v Speaker 1>can move faster than the speed of light. I have

0:34:46.600 --> 0:34:51.040
<v Speaker 1>no idea what an inverse tachion would be, but that's

0:34:51.480 --> 0:34:53.920
<v Speaker 1>one of the big examples that I tend to think

0:34:54.000 --> 0:34:58.120
<v Speaker 1>about Star Trek. However, science fiction is not the only

0:34:58.280 --> 0:35:02.240
<v Speaker 1>source of techno babble. There are others. Thrillers and procedurals

0:35:02.320 --> 0:35:06.520
<v Speaker 1>also revel in techno babble. From time to time. Characters

0:35:06.560 --> 0:35:10.680
<v Speaker 1>like Chloe O'Brien in twenty four or Abbey And in

0:35:10.800 --> 0:35:14.640
<v Speaker 1>c I S frequently speak in techno babble, only to

0:35:14.719 --> 0:35:16.920
<v Speaker 1>have someone else in the scene asked them to repeat

0:35:16.960 --> 0:35:21.000
<v Speaker 1>what they said, quote unquote in English. Now frequently the

0:35:21.040 --> 0:35:24.279
<v Speaker 1>English translation for the techno speak doesn't actually match up

0:35:24.320 --> 0:35:27.640
<v Speaker 1>with whatever the techno speak was, which means the tech

0:35:27.800 --> 0:35:31.400
<v Speaker 1>speak was totally superfluous. Though you could argue the writers

0:35:31.400 --> 0:35:34.160
<v Speaker 1>were including it to try and create some sort of

0:35:34.160 --> 0:35:37.279
<v Speaker 1>credibility for the character as an expert in his or

0:35:37.320 --> 0:35:40.760
<v Speaker 1>her field, and not actually meant to move the story along.

0:35:41.160 --> 0:35:44.239
<v Speaker 1>But to me, it's almost like you're treading water. You're

0:35:44.239 --> 0:35:49.120
<v Speaker 1>having a character say, at least reportedly, say the same

0:35:49.160 --> 0:35:52.840
<v Speaker 1>thing two different ways, except in reality they're saying nonsense

0:35:52.920 --> 0:35:55.839
<v Speaker 1>one way and then something that makes sense the other way.

0:35:55.840 --> 0:35:58.440
<v Speaker 1>Why would they not just use plain English in the

0:35:58.480 --> 0:36:02.319
<v Speaker 1>first place? Now? Pretty sure that Shannon Morse and I

0:36:02.480 --> 0:36:06.200
<v Speaker 1>Shannon Morse of Hack five covered some atrocious examples of

0:36:06.200 --> 0:36:09.919
<v Speaker 1>techno babble in our episode about hacking in Hollywood. In fact,

0:36:10.000 --> 0:36:12.160
<v Speaker 1>I remember that we specifically covered this one, but I

0:36:12.200 --> 0:36:14.480
<v Speaker 1>want to talk about it again. One of my favorite

0:36:14.480 --> 0:36:19.440
<v Speaker 1>examples of techno babble and hacking Hollywood style would be

0:36:19.520 --> 0:36:22.040
<v Speaker 1>from c s I New York. It was from an

0:36:22.040 --> 0:36:26.120
<v Speaker 1>episode called Taxi in which a character named Lindsay says,

0:36:26.760 --> 0:36:29.920
<v Speaker 1>I'll create a g uy Actually, she says gooey. I'll

0:36:29.960 --> 0:36:33.680
<v Speaker 1>create a gooey interface using visual basic see if I

0:36:33.719 --> 0:36:39.319
<v Speaker 1>can track an IP address. So that's so wrong, It

0:36:39.480 --> 0:36:44.160
<v Speaker 1>is hilariously wrong. This clip is available to watch on YouTube.

0:36:44.160 --> 0:36:46.400
<v Speaker 1>If you're so inclined, you can just see that in

0:36:46.440 --> 0:36:50.799
<v Speaker 1>this brief moment it lasts less than three seconds. I'll

0:36:50.800 --> 0:36:53.080
<v Speaker 1>create a gooey interface using visual basics, see if I

0:36:53.080 --> 0:36:57.239
<v Speaker 1>can track an IP address. It is so silly. Let's

0:36:57.280 --> 0:36:59.240
<v Speaker 1>go through it step by step to kind of see

0:36:59.280 --> 0:37:03.720
<v Speaker 1>how ridiculous this techno babble is. First of all, Lindsay

0:37:03.800 --> 0:37:07.480
<v Speaker 1>says she's going to create a gooey interface that's already repetitive.

0:37:07.719 --> 0:37:10.520
<v Speaker 1>It's like saying a T M machine or pen number.

0:37:11.040 --> 0:37:14.320
<v Speaker 1>Gooey is g u I and it stands for graphical

0:37:14.560 --> 0:37:18.440
<v Speaker 1>user interface. So she's going to create a graphical user

0:37:18.560 --> 0:37:23.759
<v Speaker 1>interface interface, according to what she says. Also, a gooey

0:37:23.920 --> 0:37:26.680
<v Speaker 1>is just a way to interact with the device. That's

0:37:26.800 --> 0:37:32.239
<v Speaker 1>what interface means. It's the way you interface with your technology.

0:37:32.280 --> 0:37:36.239
<v Speaker 1>It facilitates computer commands. It doesn't do anything special. It

0:37:36.320 --> 0:37:39.719
<v Speaker 1>just allows you to do whatever you need to do

0:37:39.960 --> 0:37:42.520
<v Speaker 1>on a device. But it itself is just a facilitator.

0:37:42.600 --> 0:37:47.000
<v Speaker 1>So Windows is a gooey mac Os is a gooey.

0:37:47.440 --> 0:37:52.279
<v Speaker 1>Smartphone user interfaces are gooey's because your your programs are

0:37:52.320 --> 0:37:55.680
<v Speaker 1>represented by icons their pictures. Then you can click or

0:37:55.760 --> 0:37:59.520
<v Speaker 1>press on the pictures and activate them and it launches

0:37:59.560 --> 0:38:02.000
<v Speaker 1>into a program. But that's all it is. That's what

0:38:02.080 --> 0:38:04.600
<v Speaker 1>the interface is. This is in contrast, by the way,

0:38:04.640 --> 0:38:07.200
<v Speaker 1>with text based interfaces, in which you would have to

0:38:07.239 --> 0:38:09.759
<v Speaker 1>type in commands and file names to get stuff done.

0:38:10.000 --> 0:38:12.719
<v Speaker 1>So you might have to say run such and such

0:38:12.800 --> 0:38:16.080
<v Speaker 1>dot e x c, and that would send a command

0:38:16.120 --> 0:38:18.640
<v Speaker 1>to your computer to find that e x C file

0:38:19.239 --> 0:38:22.960
<v Speaker 1>and to initiate it, whereas on a gooey you just

0:38:23.040 --> 0:38:25.839
<v Speaker 1>click on whatever the icon is that represents that that

0:38:26.040 --> 0:38:30.120
<v Speaker 1>particular program. As for visual Basic, that's the next part

0:38:30.160 --> 0:38:33.960
<v Speaker 1>of Lindsay's line. Visual Basic was a programming language. I

0:38:33.960 --> 0:38:36.120
<v Speaker 1>guess you could say it is a programming language, but

0:38:36.160 --> 0:38:39.560
<v Speaker 1>we'll get to that. So I guess you could argue

0:38:39.560 --> 0:38:44.160
<v Speaker 1>that that part of her statement made some sense, I suppose.

0:38:44.440 --> 0:38:48.279
<v Speaker 1>But visual Basic relies on a gooey visual Basic. The

0:38:48.280 --> 0:38:52.000
<v Speaker 1>reason why it's called visual is because it's a gooey

0:38:52.040 --> 0:38:56.400
<v Speaker 1>interface to be repetitive again, to do programming. So a

0:38:56.400 --> 0:39:00.800
<v Speaker 1>programmer would use visual Basic to create code, choosing snippets

0:39:00.840 --> 0:39:04.359
<v Speaker 1>of code that was written in the basic programming language.

0:39:04.520 --> 0:39:07.839
<v Speaker 1>Thus the name visual basic. Basic was designed as an

0:39:07.960 --> 0:39:12.440
<v Speaker 1>educational tool primarily, and it made the transition to legacy

0:39:12.480 --> 0:39:15.520
<v Speaker 1>status Visual Basic did in two thousand eight. So, in

0:39:15.560 --> 0:39:19.520
<v Speaker 1>other words, this was a pretty limited programming language. It

0:39:19.600 --> 0:39:21.960
<v Speaker 1>was a good tool for learning the basics of programming,

0:39:21.960 --> 0:39:25.360
<v Speaker 1>but it wasn't exactly the most sophisticated or versatile programming

0:39:25.440 --> 0:39:28.359
<v Speaker 1>language out there. Also, the c s I New York

0:39:28.400 --> 0:39:31.800
<v Speaker 1>episode aired in two thousand eight, the same year Visual

0:39:31.840 --> 0:39:35.520
<v Speaker 1>Basic was sunsetted as a legacy programming language. So now

0:39:35.560 --> 0:39:37.760
<v Speaker 1>you've got Lindsay saying she's going to make a gooy

0:39:37.840 --> 0:39:41.360
<v Speaker 1>with an outdated programming language. And by now it should

0:39:41.360 --> 0:39:45.000
<v Speaker 1>be pretty obvious that an interface, even one so amazing

0:39:45.040 --> 0:39:48.120
<v Speaker 1>that it was built in Visual Basic, wouldn't be able

0:39:48.160 --> 0:39:51.720
<v Speaker 1>to track an IP address at all. It's just an interface.

0:39:51.760 --> 0:39:55.960
<v Speaker 1>It doesn't do anything other than act as a facilitator. Moreover,

0:39:56.520 --> 0:39:59.560
<v Speaker 1>there's no shortage of ways to track I P addresses

0:39:59.719 --> 0:40:03.600
<v Speaker 1>at Just looking at a server that's being contacted is enough,

0:40:03.640 --> 0:40:06.840
<v Speaker 1>because the incoming traffic has to have an IP address

0:40:06.840 --> 0:40:11.080
<v Speaker 1>associated with it, because that's how data communication works. Now,

0:40:11.280 --> 0:40:14.080
<v Speaker 1>you might not have an accurate IP address. Someone might

0:40:14.120 --> 0:40:19.120
<v Speaker 1>be using proxies but or VPNs and thus hiding their

0:40:19.160 --> 0:40:23.040
<v Speaker 1>true IP addresses. But that's different. So that one throway

0:40:23.080 --> 0:40:25.799
<v Speaker 1>line and c s I has led to tons of

0:40:25.920 --> 0:40:29.520
<v Speaker 1>jokes on the Internet, including various attempts to build out

0:40:29.560 --> 0:40:32.080
<v Speaker 1>what would be a gooey in Visual basics. So there

0:40:32.080 --> 0:40:34.840
<v Speaker 1>are a lot of visual gags out there. If you

0:40:34.920 --> 0:40:38.480
<v Speaker 1>just do a search for CSI, New York g u I,

0:40:38.520 --> 0:40:41.319
<v Speaker 1>you're gonna see a ton of them. Now, sometimes the

0:40:41.320 --> 0:40:44.840
<v Speaker 1>techno speak that a character says actually does mean something

0:40:44.960 --> 0:40:49.160
<v Speaker 1>or almost mean something. So, for example, in the series Arrow,

0:40:49.440 --> 0:40:52.319
<v Speaker 1>the character Felicity in one episode says, I have to

0:40:52.360 --> 0:40:56.320
<v Speaker 1>break through the processor's protective firewall to stop cadence virus

0:40:56.680 --> 0:40:59.640
<v Speaker 1>and the fact that the processor is exponentially overclocking and

0:40:59.680 --> 0:41:03.120
<v Speaker 1>he's disabled the cooling system. And then she's interrupted by

0:41:03.160 --> 0:41:06.680
<v Speaker 1>Green Arrow, who says he didn't understand any of that. Well,

0:41:06.760 --> 0:41:11.440
<v Speaker 1>that particular sentence at least has some elements that makes sense.

0:41:12.560 --> 0:41:15.279
<v Speaker 1>All of the things she says are real things, but

0:41:15.480 --> 0:41:19.640
<v Speaker 1>the exponential overclocking would have to be an exaggeration. Processors

0:41:19.680 --> 0:41:23.640
<v Speaker 1>have limits they cannot go beyond, even with overclocking. Um

0:41:23.680 --> 0:41:27.520
<v Speaker 1>a processor has clock cycles essentially means how many instructions

0:41:27.600 --> 0:41:31.360
<v Speaker 1>can this processor complete within a given amount of time,

0:41:32.040 --> 0:41:36.600
<v Speaker 1>and and processor manufacturers create limits, like they make a

0:41:36.640 --> 0:41:40.560
<v Speaker 1>hard limit for the number of processes per second that

0:41:40.680 --> 0:41:44.719
<v Speaker 1>a clock can handle. But you can remove those limits

0:41:44.719 --> 0:41:47.680
<v Speaker 1>with processors. That's what you call overclocking. You can make

0:41:47.719 --> 0:41:52.120
<v Speaker 1>processors actually uh fulfill more instructions per second than they

0:41:52.120 --> 0:41:55.440
<v Speaker 1>were rated for, at least up to a point. Eventually

0:41:55.440 --> 0:41:58.399
<v Speaker 1>you reach whatever the maximum is that that processor can

0:41:58.440 --> 0:42:02.920
<v Speaker 1>handle even with overclocking. So exponential is likely not the

0:42:03.000 --> 0:42:06.160
<v Speaker 1>right word that would they'll be way too much. I

0:42:06.239 --> 0:42:10.080
<v Speaker 1>doubt that any microprocess or manufacturer out there builds in

0:42:10.360 --> 0:42:14.319
<v Speaker 1>enough capacity and then limits it enough for you to

0:42:14.320 --> 0:42:18.800
<v Speaker 1>have exponential overclocking. Also, you wouldn't really have a firewall

0:42:18.800 --> 0:42:22.960
<v Speaker 1>around a processor. Firewalls fit between internal and external networks.

0:42:23.040 --> 0:42:26.320
<v Speaker 1>It's meant to protect the internal network from harmful forces

0:42:26.400 --> 0:42:28.800
<v Speaker 1>from the outside, so like from the Internet. So a

0:42:28.880 --> 0:42:32.440
<v Speaker 1>firewall would sit on a connection between machines and the Internet,

0:42:32.480 --> 0:42:35.520
<v Speaker 1>but not so far down as the processor level. Still,

0:42:35.880 --> 0:42:38.759
<v Speaker 1>I would say that this was a decent attempt at

0:42:38.840 --> 0:42:43.200
<v Speaker 1>making a meaningful statement. It didn't fully hit the target,

0:42:43.320 --> 0:42:46.839
<v Speaker 1>but again close, which is not great for a guy

0:42:46.880 --> 0:42:51.000
<v Speaker 1>who uses arrows as his main means of weaponry. Anyway,

0:42:51.200 --> 0:42:54.120
<v Speaker 1>there were two reasons I really wanted to talk about

0:42:54.160 --> 0:42:57.680
<v Speaker 1>the turbo encabulator and techno babble. The first is I

0:42:57.719 --> 0:43:00.400
<v Speaker 1>think the turbo encabulator is a pretty funny joe that

0:43:00.480 --> 0:43:02.640
<v Speaker 1>pokes fun at the very human trade of trying to

0:43:02.640 --> 0:43:06.880
<v Speaker 1>make stuff sound important. The second is that it reminds

0:43:06.920 --> 0:43:09.640
<v Speaker 1>us this sort of language is used all the time,

0:43:09.920 --> 0:43:13.480
<v Speaker 1>and not just an entertainment, not just to create things

0:43:13.520 --> 0:43:16.239
<v Speaker 1>that make people sound smart. We run into it in

0:43:16.360 --> 0:43:20.840
<v Speaker 1>marketing materials all the time, real world marketing materials aimed

0:43:21.040 --> 0:43:24.720
<v Speaker 1>at selling stuff to us. So it's good to remember

0:43:25.320 --> 0:43:27.480
<v Speaker 1>this sort of stuff is meant to dazzle us while

0:43:27.480 --> 0:43:31.000
<v Speaker 1>not actually saying anything of substance. It's another example of

0:43:31.040 --> 0:43:34.600
<v Speaker 1>why we should practice critical thinking whenever we can, because

0:43:34.600 --> 0:43:37.520
<v Speaker 1>it could help us avoid making a really dumb decision

0:43:38.239 --> 0:43:40.840
<v Speaker 1>because we were so impressed with what sounded like a

0:43:40.840 --> 0:43:44.280
<v Speaker 1>sophisticated description that we never looked into it any further.

0:43:44.840 --> 0:43:48.080
<v Speaker 1>This teaches us to learn what the actual definitions for

0:43:48.160 --> 0:43:53.280
<v Speaker 1>words are, both the official definitions and the contextual definitions,

0:43:53.960 --> 0:43:56.759
<v Speaker 1>and we know what they mean and what they do

0:43:56.800 --> 0:44:01.239
<v Speaker 1>not mean. So words like quantum, which is forly overused

0:44:01.280 --> 0:44:04.920
<v Speaker 1>and misused to a criminal level, is a dead giveaway

0:44:04.920 --> 0:44:07.680
<v Speaker 1>that you need to pay really close attention. Or words

0:44:07.719 --> 0:44:12.160
<v Speaker 1>like organic or natural. Heck, words like smart when applied

0:44:12.160 --> 0:44:15.560
<v Speaker 1>to technology or other products, those are all things that

0:44:15.640 --> 0:44:18.399
<v Speaker 1>mean you should probably take a closer look. It doesn't

0:44:18.440 --> 0:44:21.080
<v Speaker 1>necessarily mean that the people who make that thing are

0:44:21.120 --> 0:44:24.400
<v Speaker 1>out to fool you, but they might be taking some

0:44:24.480 --> 0:44:27.840
<v Speaker 1>shortcuts when they're describing whatever it is they do, and

0:44:27.960 --> 0:44:29.920
<v Speaker 1>you it's it's good to take that extra step to

0:44:29.960 --> 0:44:33.560
<v Speaker 1>find out what is actually meant by that language. Being

0:44:33.560 --> 0:44:36.359
<v Speaker 1>aware of techno babble makes it more challenging for other

0:44:36.400 --> 0:44:39.319
<v Speaker 1>people to take advantage of you. It does not make

0:44:39.360 --> 0:44:42.239
<v Speaker 1>you bulletproof, but it might mean you could sidestep a

0:44:42.280 --> 0:44:45.160
<v Speaker 1>lie or a prank that might otherwise take you in.

0:44:45.719 --> 0:44:47.920
<v Speaker 1>And I think that's a pretty valuable lesson for an

0:44:47.960 --> 0:44:51.000
<v Speaker 1>April Fool's Day. And well, that wraps up this episode

0:44:51.120 --> 0:44:54.160
<v Speaker 1>of tech Stuff. I hope you guys enjoyed it. If

0:44:54.200 --> 0:44:56.680
<v Speaker 1>you have any suggestions for future episodes, you can get

0:44:56.680 --> 0:44:58.680
<v Speaker 1>in touch with me send me an email. The address

0:44:58.760 --> 0:45:02.120
<v Speaker 1>is tech stuff at how stuff works dot com, or

0:45:02.239 --> 0:45:04.359
<v Speaker 1>you can pop on over to our website that's tech

0:45:04.440 --> 0:45:08.000
<v Speaker 1>stuff podcast dot com. You'll find links to our social

0:45:08.040 --> 0:45:10.640
<v Speaker 1>media presence over there, as well as a link to

0:45:10.680 --> 0:45:13.319
<v Speaker 1>our online store. Every purchase you make goes to help

0:45:13.360 --> 0:45:15.960
<v Speaker 1>the show, and we greatly appreciate it. And I'll talk

0:45:16.000 --> 0:45:24.400
<v Speaker 1>to you again. Release soon. For more on this and

0:45:24.480 --> 0:45:27.040
<v Speaker 1>thousands of other topics, is it how stuff Works dot

0:45:27.040 --> 0:45:37.040
<v Speaker 1>com