Fancy Pants Loves Binita

So far in my internship I’ve had an easy time. I’ve sat in on mostly car-accident depositions, which were as simple as pie for the court reporters I was there with. Some of the court reporters were 10-year veterans and others were in their first year of work. Still, none had any difficulties.

Then during one deposition, a lawyer told about a time when he was with a client for a deposition in a medical malpractice case. Lots of jargon invovled. About halfway through the deposition, the court reporter stood, declared that she couldn’t continue, and then left the room. The end.

Similarly I found the following post by a IT fellow in Australia. Except this time the court reporter didn’t get up and walk out. So the question is, is it better to do your best and produce an error-ridden transcript? Or simply abadon ship?

The Computer-Illiterate Stenographer

A few months ago at very short notice we had to pull in a temporary stenographer to record an important meeting that discussed the technical issues of replacing a legacy Datapoint system with a networked Unix system of some sort.

Unfortunately our temporary stenographer had some difficulty with the buzzwords and terms used in that discussion. Here are a few gems extracted from the transcript:

Selection criteria: High availability systems such as right technology, redundant systems and fork tolerance.

Base on the scale ability we nailed it down to either an HP 9000 or a Sun Micro Systems Sports Centre 2000.

The Sports Centre is based on the Texas instruments Super Sports 40 mega hertz chip.

Today we’ve got Romans sitting here and in the future environment we’re going to swing over to Terminal Servers. We are not going to EX.25 initially.

. . . a little bit later on we’ll swing over to the EX.25 network and these terminal servers can compound at that point in time as long as we understand that as competent.

Once we go to EX.25 we go direct into the Unix box in Lagret mode rather than through the Yot Misser … above and through the Unix Motorola box into the east of our curve.

Now if this confirms a bottleneck at any point, we do have the ability to use a black box interface to the interdatum.

Question: Between the Motorola box and the Ethen that hog is the connection between lures likely to be a log jam?

Question: What’s the physical means of transferring?

Answer: I think you had better talk to Peter about that. It’s subject to walls which will ruffle if the ISO fall?

The trouble is the current machine writes the exercise in a particular format, which is why I’m saying why can’t this thing have multiple exabyte feeding?

Can we talk a little bit about the current configuration? Don’t we have some capacity on the Sports selectors?

It may have the ability to have or connect onto the X.25 crowd. The concepts that we’re going to use today … into your remote locations we’ll probably leave that as a dial in. Is it connected to your X.25 clowns?

Looking at the current system architecture for a minute… This is the Motorola machine, the production machine coming into the arc of, and then you’ve got your Crowd processors around here. Then the brown processors, your ear plugs and over here where your transactions are coming through the 8600 vaults. I believe that this is the tester.

Okay, I think that gives us the most cost effective solution in today’s environment. Sam, why don’t you talk about the frozen cams?

We think we know what a “fork tolerant” computer is and we speculate that an “Ethen that hog” is actually an Ethernet hub, but the Romans, ear plugs, lures and frozen cams have us well and truly stumped.

What I’d really like to know though is what the stenographer thought we’re all planning to do with our “crowd processors” and “X.25 clowns”.

I think whatever option keeps me from being ridiculed on the internet is the best choice.