It was July in 1991 or 1992, and my cousin Megan and I were riding in the back seat of our grandparents' Pontiac Bonneville, on our way home from the annual 4th of July Picnic/Family Reunion.
It was late, and dark, and we were zooming (or what we thought was zooming) along on a dirt road in the middle of farm land, and listening to AM radio. The topic of conversation that evening was cirrhosis of the liver.
At one point in the segment, Megan and I swore, and still do to this day, that the guy talking on the radio slipped and said cirrhosis of the bliver. We looked at each other like, "No, that's not right...is it?" And immediately broke out into a giggle fit, as 12 year old girls are wont to do. There was some stern talking to from our grandpa, and our giggles were a little more quiet.
After that, we referred to ourselves as The Bliver Cousins. Nobody else really understood why, but we did, and that's all that matters.
Fast forward 16 years and we still call ourselves The Bliver Cousins, which always makes us laugh. It's our own little secret society. Our own version of the Ya-Ya Sisterhood.
It's amazing how something so small, so seemingly insignificant when it happens, sticks around.
We are a far cry from those two girls, with bad mall hair, and even worse earrings, one living in California, one living in Texas.
We're now both almost 30, both at that pivotal point in our lives where we really start to question who we are and why we're here and what is the next step from here, and more importantly, how do we get there from here? Careers, further education, marriage, babies...where does it all fit?
We speak daily via profuse amounts of email, and almost daily via phone, and usually once a week, one will say to the other, "Get out of my head!", as our thoughts are often so similar it's eerie.
Even after a time where we weren't in each others lives, it didn't matter. We picked right back up as if we never missed a beat. There was no readjustment period. It was just BAM! here we are. The Bliver Cousins ride again!
She is my rock, my ground, and has a fabulous knack for hanging pictures in precarious places. I am her geek, who she lovingly listens as I go on and on about the latest gadget or car thing, when she could really could care less. Our paths, while completely different in some cases, will always cross in others.
I'm not sure how it always happens, but we don't have to go looking for trouble, trouble usually finds us first, and when it does, we usually break out into the giggles like 12 year old girls.
Why? Because we're the Bliver Cousins.
Monday, March 10, 2008
Things That Make Things Move
I have one of those fabulous careers where no one really understands what it is that you do every day.
"And what is it that you do at work?"
"I'm an engineer."
"Oh, what kind? Mechanical? Electrical?"
"Well, electrical, kinda. I'm a controls engineer."
"Oh that's nice. What does that mean?"
And then, usually what results, is a long dissertation, given by me, to whomever is asking, about what it is that I do, in language that most normal people don't understand.
After 11 years in my industry, I have finally come up with an answer that usually appeases everyone.
I make things that make things move. More specifically, I make the things that build cars and trucks, move.
Not the robots, the robot guys do that, but everything else, and by everything else, I mean conveyors, clamps, welders, metal presses, turntables, and just about everything else in an assembly plant that moves any amount of distance, for any amount of time.
I don't actually build the tooling I work on, that's the mechanical guys' job. They design the tool to fit a process, say building up the doors of a vehicle, and they set up a sequence of operations, and that's where we come in.
It starts with the hardware end of things, the stuff you can actually touch: control panels that most commonly contain a processor with inputs and outputs, relays, fuses, circuit breakers, terminals, and a ton of wire. There are smaller panels that serve different purposes, and a slew of cables and cords that connect it all together. On top of all of this, you have air systems for valves that move cylinders back and forth; water systems to keep the welders cool; hydraulic systems to move the real heavy stuff that air isn't powerful enough to; and safety systems to keep the morons out of harm's way. All of this has to be sized and investigated to make sure that you have enough juice, air, water, or oil to do what you need to, and that it will stop when it's supposed to.
Once that's established, the software comes in. (Note that I say established, because as I have come to learn, nothing is ever really finished. There are always changes that get made, in various stages of the game, and just when you think you're done...you're really not.)
The software is quite literally the brains of the operation. Using the sequence that the mechanical guys set out, we go about putting the steps in, one by one. When it gets dumped into the processor, after a few trials and errors (and sometimes dumb luck), when you hit the go button, everything functions the way it's supposed to, when it's supposed to, all just a series of 1's and 0's that turn signals on and off.
Put those two elements together, add a whole lot of time, frustration, and very long days in an environment that is always noisy, usually pretty dirty, located in states and cities in some of the strangest locations...and poof!
Before I got into this business, vehicles just showed up at the dealerships on carriers from assembly plants. I had absolutely no idea what it took to build a car from sheet metal till it rolled off the end of the line, how many people it took, how many moving parts are involved, and just what happens when any of those things stop working. There are days when I wish it was still that way. :)
"And what is it that you do at work?"
"I'm an engineer."
"Oh, what kind? Mechanical? Electrical?"
"Well, electrical, kinda. I'm a controls engineer."
"Oh that's nice. What does that mean?"
And then, usually what results, is a long dissertation, given by me, to whomever is asking, about what it is that I do, in language that most normal people don't understand.
After 11 years in my industry, I have finally come up with an answer that usually appeases everyone.
I make things that make things move. More specifically, I make the things that build cars and trucks, move.
Not the robots, the robot guys do that, but everything else, and by everything else, I mean conveyors, clamps, welders, metal presses, turntables, and just about everything else in an assembly plant that moves any amount of distance, for any amount of time.
I don't actually build the tooling I work on, that's the mechanical guys' job. They design the tool to fit a process, say building up the doors of a vehicle, and they set up a sequence of operations, and that's where we come in.
It starts with the hardware end of things, the stuff you can actually touch: control panels that most commonly contain a processor with inputs and outputs, relays, fuses, circuit breakers, terminals, and a ton of wire. There are smaller panels that serve different purposes, and a slew of cables and cords that connect it all together. On top of all of this, you have air systems for valves that move cylinders back and forth; water systems to keep the welders cool; hydraulic systems to move the real heavy stuff that air isn't powerful enough to; and safety systems to keep the morons out of harm's way. All of this has to be sized and investigated to make sure that you have enough juice, air, water, or oil to do what you need to, and that it will stop when it's supposed to.
Once that's established, the software comes in. (Note that I say established, because as I have come to learn, nothing is ever really finished. There are always changes that get made, in various stages of the game, and just when you think you're done...you're really not.)
The software is quite literally the brains of the operation. Using the sequence that the mechanical guys set out, we go about putting the steps in, one by one. When it gets dumped into the processor, after a few trials and errors (and sometimes dumb luck), when you hit the go button, everything functions the way it's supposed to, when it's supposed to, all just a series of 1's and 0's that turn signals on and off.
Put those two elements together, add a whole lot of time, frustration, and very long days in an environment that is always noisy, usually pretty dirty, located in states and cities in some of the strangest locations...and poof!
Before I got into this business, vehicles just showed up at the dealerships on carriers from assembly plants. I had absolutely no idea what it took to build a car from sheet metal till it rolled off the end of the line, how many people it took, how many moving parts are involved, and just what happens when any of those things stop working. There are days when I wish it was still that way. :)
Subscribe to:
Posts (Atom)