Richard G. Epstein, Westchester University of Pennsylvania
Mike Melamed, CWRU 2000
The Case of the Killer Robot is a detailed scenario that combines elements of software engineering and computer ethics.
The scenario consists of fictitious articles that touch on specific issues in software engineering and computer ethics. The articles discuss programs such as programmer psychology, team dynamics, user interfaces, software process models, software testing, the nature of requirements, software theft, and privacy. A major consideration is "when is the software good enough?"
The articles in the scenario begin with the indictment for manslaughter of a programmer who wrote faulty code that caused the death of a robot operator. Slowly, over the course of many articles, students are introduced to factors within the software company that also contributed to the accident. They are shown software development as a social process. It is hoped that students will begin to realize the complexity of the task of building real-world software and to see some of the ethical issues intertwined in that complexity.
This scenario is about 70 pages long and includes some tongue-in-cheek humor.
For permission see author information.
Special to the Silicon Valley Sentinel-Observer
Silicon Valley, USA
Randy Samuels, the former Silicon Techtronics programmer who was indicted for writing the software responsible for the gruesome "killer robot" incident last May, was apparently a prima donna who found it very difficult to accept criticism, several of his co-workers claimed today.
In a freewheeling interview with several of Samuels' co-workers on the Robbie CX30 robot project, the Sentinel-Observer was able to gain important insights into the psyche of the man who may have been criminally responsible for the death of Bart Matthews, a robot operator and father of three small children.
With the permission of those interviewed, the Sentinel-Observer allowed Professor Sharon Skinner of the department of software psychology at Silicon Valley University to listen to a recording of the interview. Skinner studies the psychology of programmers and other psychological factors that have an impact on software development.
Skinner said, "I would agree with the woman who called him a prima donna. This is a term used to refer to a programmer who just cannot accept criticism, or more accurately, cannot accept his or her own fallibility."
"Randy Samuels has what we software psychologists call a task-oriented personality, bordering on self-oriented. He likes to get things done, but his ego is heavily involved in his work. In the programming world this is considered a no-no," Skinner added, sitting in her book-lined office.
Skinner went on to explain more about programming teams and programmer personalities: "Basically, we have found that a good programming team requires a mixture of personality types, including a person who is interaction-oriented, who derives a lot of satisfaction from working with other people, someone who can help keep the peace and keep things moving in a positive direction. Most programmers are task-oriented, and this can be a problem if one has a team in which everyone is task-oriented."
Samuels' co-workers were very reluctant to lay blame for the robot disaster at his feet, but several important facts emerged when the co-workers were pressed to comment on Samuels' personality and work habits. Samuels worked on a team that consisted of a dozen analysts, programmers and software testers. (This does not include twenty programmers who were later hired and who never became actively involved in the development of the robotics software.) Although individual team members had definite specialties, almost all were involved in the entire software process from beginning to end.
Referring to the manager of the Robbie CX30 project, one of the team members said, "Sam Reynolds has a background in data processing. He's managed several software projects of that nature, but his role in this project was mostly managerial. He attended all important meetings and he kept Ray (Ray Johnson, the robotics division chief) off our backs as much as possible."
It was reported in yesterday's Sentinel-Observer that Sam Reynolds was under severe pressure to deliver a working Robbie CX30 robot by January 1 of this year. Reynolds could not be reached for comment about his own role in the incident or about Samuels and his work habits.
"We were a democratic team, except for the managerial guidance provided by Sam," another team member observed. In the world of software development, a democratic team is a team in which all members have an equal say in the decision-making process. The team member continued, "Unfortunately, we were a team of very ambitious, very talented -- if I must say so myself -- and very opinionated individualists. Randy (Samuels) was just the worst of the lot. I mean we have two guys and one gal with masters degrees from C.M.U. who weren't as arrogant as Randy." C.M.U. refers to Carnegie Mellon University, a national leader in software engineering education.
One co-worker told of an incident in which Samuels stormed out of a quality-assurance meeting. This meeting involved Samuels and three "readers" of a software module he had designed and implemented. Such a meeting is called a code review. One of the readers mentioned that Samuels had used a very inefficient algorithm (program) for achieving a certain result and Samuels "turned beet red." He then yelled a stream of obscenities before he left the meeting and never returned.
"We sent him a memo about the faster algorithm, and he eventually did use the more efficient algorithm in his module," the co-worker added.
The software module in the quality-assurance incident was the very one found to be at fault in the death of robot operator Bart Matthews. However, this co-worker was quick to point out that the efficiency of the algorithm was not an issue in the malfunctioning of the robot:
"It's just that Randy made it very difficult for people to communicate their concerns to him. He took everything very personally. He graduated tops in his class at college and later graduated with honors in software engineering from Purdue. He's definitely very bright."
"Randy had this big computer-generated banner on his wall," this co-worker continued. "It said, 'You give me the specification and I'll give you the computation.' That's the kind of arrogance he had, and it also shows that he had little patience for developing and checking the specifications. He loved the problem-solving aspect, the programming itself."
"It doesn't seem that Randy Samuels caught on to the spirit of egoless programming," Professor Skinner observed upon hearing this part of the interview with Samuels' co-workers. "The idea of egoless programming is that a software product belongs to the team and not to the individual programmers. The idea is to be open to criticism and to be less attached to one's work. Code reviews are certainly consistent with this overall philosophy."
A female co-worker spoke of another aspect of Samuels' personality -- his helpfulness. She said, "Randy hated meetings, but he was pretty good one on one. He was always eager to help. I remember one time when I ran into a serious roadblock and instead of just pointing me in the right direction, he took over the problem and solved it himself. He spent nearly five entire days on my problem."
"Of course, in retrospect, it might have been better for poor Mr. Matthews and his family if Randy had stuck to his own business," she added after a long pause.
The site is updating and expanding and is currently in beta form. Please fill out our questionnaire to provide your feedback. It should take no more than 15 minutes to complete.
If you would like to fill out the form later, you can return to this page http://www.onlineethics.org/feedback.aspx
If you need help finding a specific resource, please contact us via email at firstname.lastname@example.org.