Ethics in computing asks what engineers owe to the people their systems touch. It does not hand out answers; it gives tools for seeing who is affected, which values pull against each other and how to justify a choice. Cultures and traditions weigh these values differently, so the aim is sound reasoning, not one verdict.
Key concepts
- Stakeholders: everyone affected by a system, including those who never use it.
- Competing values: privacy, safety, fairness, autonomy, transparency and utility often conflict.
- Ethical frameworks: consequences, duties and rights, virtues and care each highlight different questions.
- Professional codes: published statements of duty that professional bodies ask members to follow.
- Foreseeable harm: thinking through misuse and failure before release, not after.
Vocabulary
- Dual use: a technology that serves both beneficial and harmful ends.
- Informed consent: agreement given with a real understanding of what is being agreed to.
- Accountability: being answerable for a system's effects.
- Value-sensitive design: designing with the affected parties' values in mind from the start.
What to study, in order
- Read a professional code of ethics for engineers and list the duties it names.
- Take a past system failure and name its stakeholders, harms and the decisions that led to it.
- Analyse one design choice through two different frameworks and note where they disagree.
- Practise writing a short impact assessment before building a feature.
- Discuss a dilemma with colleagues, stating the strongest case for each side before concluding.