Sucks to Be Dave Foley...

Main > Everything Else

<< < (69/78) > >>

Howard_Casto:
You aren't going to believe this, but honestly I prefer the latter explanation. I would suggest you designate them as container a, container b, and container c to alleviate confusion. Believe it or not, terms like drain pan and jug can be regional, especially if you have some workers that weren't originally from the US.

Then again I'm a programmer, and we have our own issues.

Vigo:
I'm sure you are used to having subsets of the same name as a programmer. Technicians tend to need to be handed terms or they make up their own thing, which is funny because we deal with regional terms as part of our training problems. One of our training technicians just recently got called out for referring to epoxy as "Wet tape". There are references in our tech manuals to attaching cabling using "batmen" thanks to regional lingo.

The problem in this case was that they are wildly different things. One is a chemical bottle, similar to a bleach bottle. Another is an internal component and the third is a remote, large metal basin. If they were 3 similar things, I would have been much cooler about calling them the same thing.

Titchgamer:
That made me chuckle lol

But yeah like Howard said some of those terms are regional.

A jug for instance is a small hand held measuring device over here.

My advice to you would be call it what it is.
A apple is a apple ya know.

If when you built the thing your guys called it a chemical bottle call it that no need to change the name unless its inaccurate.

I understood your first terms but the second lot confused me lol

BadMouth:

--- Quote from: Vigo on February 16, 2018, 06:37:16 pm ---So his proposal is that I train technicians to connect the container to the container that drains into the other container.

--- End quote ---

One time I had to travel to set up shop and train some people due to a dept being relocated to different city. The job was basically just repackaging items from bulk for individual sale. Had a woman who insisted on referring to everything as a "unit". "Put a gauge and a pack of hardware in the plastic shell, then insert that into the box and put a label on it". She'd reply "so I take this unit and that unit and put it in this unit". It was even more weird when she announced that she ran out of units and then had to further explain which unit she was talking about. She would also ask whether she should use this unit or that unit while holding up identical boxes at a distance. I don't know if she was trying to sound technical or had worked in a factory where they called every damn thing units.

lilshawn:

--- Quote from: Titchgamer on February 17, 2018, 01:51:28 am ---My advice to you would be call it what it is.
A apple is a apple ya know.

--- End quote ---

except when you are a programmer.

in a failsafe system, to differentiate NO data from ZERO data.
because if you have a sensor failure or disconnect, the input reads continuously low, you need to be able to differentiate that..

00000000 = no data incoming opposed to it having an actual value of zero, otherwise on failure the system would continue to operate as if the value was "zero" instead of halting.

so you can't count from "zero". so you need to count from one.

00000001 = 0
00000010 = 1
00000011 = 2
.
.
.
11111110 = 253
11111111 = 254

but knowing this, leads to some interesting conversations with people who have no idea.

"what is the current data of the X sensor?"

"nothing"

"nothing or ZERO"

"I don't know... it's nothing it's showing nothing"

"so it showing as blank?"

"no it has 3 zeros"

:dizzy:

okay the sensor value IS zero then.

"what is the value of Y sensor then?"

"nothing"

:banghead:

*Disheartened sigh*

".........nothing....... or ZERO"

"nothing"

".....like blank?"

"yeah, like blank"

"HALLELUJAHHHHHH"

Navigation

 Message Index

Go to full version