Star Trek Problems: With the Beeping and the Booping

Star Trek Problems 80 - Picard makes all monitors beep

Vincent’s Comments: The idea for this Star Trek Problems strip came to me the other day when I was playing Star Trek sound effects at work. It was a weird experience hearing beeps and bloops when our computers are otherwise silent. Why would every interface have audible noises in Star Trek, especially Star Trek: The Next Generation. Because it sounds cool on TV, that’s why.

  • Anthony Hita

    “Life forms–beep, beep, beep, boop–you precious little life forms–boop, boop, boop, boop–you tiny little life forms–boop, beep, boop, boop–where are you?–boop, beep, beep, beep, beep, boop.”

  • Arch Stanton

    How could anyone take being on an 8 hour shift siting in the command seat on the bridge?
    8 hours of nothing but a view screen of deep space where there is nothing and listening to 8 hours of beep, whoop and flashing lights.

    No one gave any thought to the whole concept.

    Not only that, looking at the view screen with the before mentioned nothingness yet having a cascade of lights of no purpose moving along the bottom of the screen.

    If you think about it, other than maintenance, the Doctor is the only one who has a real job on the ship. Command does absolutely nothing but sign forms until something major happens.

    Which brings me to another point, who in their right mind of a crew consisting of 400 would send the top leadership on a dangerous away mission?

    This would never happen in reality so once again, Kirk would never have anything to do but sit around and be bored.

  • Andrew Williams

    “Again with the Klingons…”

  • Andrew Williams

    How would we know if someone is mastor haxoring into the mainframe? Or zooming and enhancing grid epsilon 5?

    It’d be nice if they used one of those beeps to say “This terminal is going to asplode. You may wish to stand clear.”