Might Delete Later Quotes

Since emotions have to be programmed into robots from the outside, manufacturers may offer a menu of emotions carefully chosen on the basis of whether they are necessary, useful, or will increase bonding with the owner. In all likelihood, robots will be programmed to have only a few human emotions, depending on the situation. Perhaps the emotion most valued by the robot’s owner will be loyalty. One wants a robot that faithfully carries out its commands without complaints, that understands the needs of the master and anticipates them. The last thing an owner will want is a robot with an attitude, one that talks back, criticizes people, and whines. Helpful criticisms are important, but they must be made in a constructive, tactful way. Also, if humans give it conflicting commands, the robot should know to ignore all of them except those coming from its owner. Empathy will be another emotion that will be valued by the owner. Robots that have empathy will understand the problems of others and will come to their aid. By interpreting facial movements and listening to tone of voice, robots will be able to identify when a person is in distress and will provide assistance when possible. Strangely, fear is another emotion that is desirable. Evolution gave us the feeling of fear for a reason, to avoid certain things that are dangerous to us. Even though robots will be made of steel, they should fear certain things that can damage them, like falling off tall buildings or entering a raging fire. A totally fearless robot is a useless one if it destroys itself. But certain emotions may have to be deleted, forbidden, or highly regulated, such as anger. Given that robots could be built to have great physical strength, an angry robot could create tremendous problems in the home and workplace. Anger could get in the way of its duties and cause great damage to property. (The original evolutionary purpose of anger was to show our dissatisfaction. This can be done in a rational, dispassionate way, without getting angry.) Another emotion that should be deleted is the desire to be in command. A bossy robot will only make trouble and might challenge the judgment and wishes of the owner. (This point will also be important later, when we discuss whether robots will one day take over from humans.) Hence the robot will have to defer to the wishes of the owner, even if this may not be the best path. But perhaps the most difficult emotion to convey is humor, which is a glue that can bond total strangers together. A simple joke can defuse a tense situation or inflame it. The basic mechanics of humor are simple: they involve a punch line that is unanticipated. But the subtleties of humor can be enormous. In fact, we often size up other people on the basis of how they react to certain jokes. If humans use humor as a gauge to measure other humans, then one can appreciate the difficulty of creating a robot that can tell if a joke is funny or not.

We need to be humble enough to recognize that unforeseen things can and do happen that are nobody’s fault. A good example of this occurred during the making of Toy Story 2. Earlier, when I described the evolution of that movie, I explained that our decision to overhaul the film so late in the game led to a meltdown of our workforce. This meltdown was the big unexpected event, and our response to it became part of our mythology. But about ten months before the reboot was ordered, in the winter of 1998, we’d been hit with a series of three smaller, random events—the first of which would threaten the future of Pixar. To understand this first event, you need to know that we rely on Unix and Linux machines to store the thousands of computer files that comprise all the shots of any given film. And on those machines, there is a command—/bin/rm -r -f *—that removes everything on the file system as fast as it can. Hearing that, you can probably anticipate what’s coming: Somehow, by accident, someone used this command on the drives where the Toy Story 2 files were kept. Not just some of the files, either. All of the data that made up the pictures, from objects to backgrounds, from lighting to shading, was dumped out of the system. First, Woody’s hat disappeared. Then his boots. Then he disappeared entirely. One by one, the other characters began to vanish, too: Buzz, Mr. Potato Head, Hamm, Rex. Whole sequences—poof!—were deleted from the drive. Oren Jacobs, one of the lead technical directors on the movie, remembers watching this occur in real time. At first, he couldn’t believe what he was seeing. Then, he was frantically dialing the phone to reach systems. “Pull out the plug on the Toy Story 2 master machine!” he screamed. When the guy on the other end asked, sensibly, why, Oren screamed louder: “Please, God, just pull it out as fast as you can!” The systems guy moved quickly, but still, two years of work—90 percent of the film—had been erased in a matter of seconds. An hour later, Oren and his boss, Galyn Susman, were in my office, trying to figure out what we would do next. “Don’t worry,” we all reassured each other. “We’ll restore the data from the backup system tonight. We’ll only lose half a day of work.” But then came random event number two: The backup system, we discovered, hadn’t been working correctly. The mechanism we had in place specifically to help us recover from data failures had itself failed. Toy Story 2 was gone and, at this point, the urge to panic was quite real. To reassemble the film would have taken thirty people a solid year. I remember the meeting when, as this devastating reality began to sink in, the company’s leaders gathered in a conference room to discuss our options—of which there seemed to be none. Then, about an hour into our discussion, Galyn Susman, the movie’s supervising technical director, remembered something: “Wait,” she said. “I might have a backup on my home computer.” About six months before, Galyn had had her second baby, which required that she spend more of her time working from home. To make that process more convenient, she’d set up a system that copied the entire film database to her home computer, automatically, once a week. This—our third random event—would be our salvation. Within a minute of her epiphany, Galyn and Oren were in her Volvo, speeding to her home in San Anselmo. They got her computer, wrapped it in blankets, and placed it carefully in the backseat. Then they drove in the slow lane all the way back to the office, where the machine was, as Oren describes it, “carried into Pixar like an Egyptian pharaoh.” Thanks to Galyn’s files, Woody was back—along with the rest of the movie.

Henry faltered not for an instant; but rising to a loftier attitude, and fixing on the speaker an eye of the most determined fire, he finished his sentence with the firmest emphasis) ‘may profit by their example. If this be treason, make the most of it’… “I had frequently heard the above anecdote of the cry of treason, but with such variations of the concluding words, that I began to doubt whether the whole might not be fiction. With a view to ascertain the truth, therefore, I submitted it to Mr. Jefferson, as it had been given to me by judge Tyler, and this is his answer. ‘I well remember the cry of treason, the pause of Mr. Henry at the name of George the III. and the presence of mind with which he closed his sentence, and baffled the charge vociferated.’" The last sentence proved to be too much for the other burgesses to stomach, and they later deleted it from the bill.

Tharion finished Sofie’s inbox, checked the junk folder, and then finally the trash. It was mostly empty. He clicked open her sent folder, and groaned at the tally. But he began reading again. Click after click after click. His phone chimed with an alert: thirty minutes until he needed to get into the water. He could reach the air lock in five minutes, if he walked fast. He could get through another few emails before then. Click, click, click. Tharion’s phone chimed again. Ten minutes. But he’d halted on an email dated three years ago. It was so simple, so nonsensical that it stood out. Subject: Re: Dusk’s Truth The subject line was weird. But the body of her email was even weirder. Working on gaining access. Will take time. That was it. Tharion scanned downward, toward the original message that Sofie had replied to. It had been sent two weeks before her reply. From: BansheeFan56 Subject: Dusk’s Truth Have you gotten inside yet? I want to know the full story. Tharion scratched his head, opened another window, and searched for Dusk’s Truth. Nothing. No record of a movie or book or TV show. He did a search on the email system for the sender’s name: BansheeFan56. Another half-deleted chain. This one originating from BansheeFan56. Subject: Project Thurr Could be useful to you. Read it. Sofie had replied: Just did. I think it’s a long shot. And the Six will kill me for it. He had a good feeling he knew who “the Six” referred to: the Asteri. But when Tharion searched online for Project Thurr, he found nothing. Only news reports on archaeological digs or art gallery exhibits featuring the ancient demigod. Interesting. There was one other email—in the drafts folder. BansheeFan56 had written: When you find him, lie low in the place I told you about—where the weary souls find relief from their suffering in Lunathion. It’s secure. A rendezvous spot? Tharion scanned what Sofie had started to reply, but never sent. Thank you. I’ll try to pass along the info to my She’d never finished it. There were any number of ways that sentence could have ended. But Sofie must have needed a place where no one would think to look for her and her brother. If Sofie Renast had indeed survived the Hind, she might well have come here, to this very city, with the promise of a safe place to hide. But this stuff about Project Thurr and Dusk’s Truth … He tucked those tidbits away for later. Tharion opened a search field within Declan’s program and typed in the sender’s address. He started as the result came in. Danika Fendyr.