6) Conclusions and Reflections
Our individual conclustions:
Jack: dependent on the probability of causing an error. since faa had a backup system that should have worked, it was a reasonable decision to go forward. Additionally, the FAA should be partially at fault as well because their backup system is not properly operational.
Adam: Another scenario would be that even if the backup system worked and the FAA came across the bug, the company would still get in trouble. Yet another is that it's not like the faa will pay another contractor for it. the get tough policy
Zach: Will lose the larger contract since this is an initial prototype. Emmett should have told someone
Angela: Emmett should have told someone. Although a lot of his coworkers worked really hard they should prioritize the lives of the pilot testers.
Jonathan: On principle, I would not sign off on a product with a defect that I know could have such widespread negative consequences.
John: I would have signed off on it. After hearing that the testing would be small scale enough and the backup system would be in place, the risk should have been small enough.
Ultimate consensus:
The majority of us have concluded that if we were in the same position as Emmett, we would have decided to not go forward with signing off on the software. While we do not know the probability of the error showing up, we would rather lean towards putting out a product that is sound and we can stand by.
Problems we encountered (most difficult aspects of the project):
One problem that we encountered was that our decision came from a pretty detached point of view. It took quite a bit of time to put ourselves in Emmett's shoes and try to empathize with his burden of guilt and factors that weigh him down.
Another problem that we encountered was it took a bit of time to understand the prompt, as we thought it was poorly formatted. It was also difficult to determine the probability of each outcome which was definitely important for certain ethical frameworks.
Jack: dependent on the probability of causing an error. since faa had a backup system that should have worked, it was a reasonable decision to go forward. Additionally, the FAA should be partially at fault as well because their backup system is not properly operational.
Adam: Another scenario would be that even if the backup system worked and the FAA came across the bug, the company would still get in trouble. Yet another is that it's not like the faa will pay another contractor for it. the get tough policy
Zach: Will lose the larger contract since this is an initial prototype. Emmett should have told someone
Angela: Emmett should have told someone. Although a lot of his coworkers worked really hard they should prioritize the lives of the pilot testers.
Jonathan: On principle, I would not sign off on a product with a defect that I know could have such widespread negative consequences.
John: I would have signed off on it. After hearing that the testing would be small scale enough and the backup system would be in place, the risk should have been small enough.
Ultimate consensus:
The majority of us have concluded that if we were in the same position as Emmett, we would have decided to not go forward with signing off on the software. While we do not know the probability of the error showing up, we would rather lean towards putting out a product that is sound and we can stand by.
Problems we encountered (most difficult aspects of the project):
One problem that we encountered was that our decision came from a pretty detached point of view. It took quite a bit of time to put ourselves in Emmett's shoes and try to empathize with his burden of guilt and factors that weigh him down.
Another problem that we encountered was it took a bit of time to understand the prompt, as we thought it was poorly formatted. It was also difficult to determine the probability of each outcome which was definitely important for certain ethical frameworks.
Comments
Post a Comment