Last night as I was reading the magazine "software development", I came across something that made me giggle. In the magazine, there was a profile of a man named Rusty Pease who "programs amusement park atractions" for the Walt Disney parks.
The last question and answer in the article is as follows:
sd: "Do you ride the roller coasters yourself?"
RP: "I do. They get tiring after awhile. When I'm working on one, I end up riding it so much. For example, Space Mountain in Paris has an on-board audio system that's synchronized with where you are on the track. How do you test the synchronization? You've got to ride it."
How's that for an interesting part of one's job? Imagine installing the audio system...then testing it out only to discover that it's off by a large margin...then fiddling with the configuration...then testing it out again...and repeating the process until everything is "just right".
I know that game testing has made its way occasionally through the forum...but the above seems like it would take things to the next level.
Cyberentomological Detection, Prevention, and Eradication Specialist
Okay, the worst would be those simulators where you ride the roller coaster, fly through the air or such. If you have ever ridden on of those that has been off by a couple of seconds, it can make you kind of quesy.