Ethics teaching arrives too late in technical education
A final-year ethics module teaches students that ethics is what you consider after the engineering is finished. That lesson is learned more thoroughly than the syllabus.
Most engineering and computing programmes now include ethics. It is usually a single module, usually late in the degree, usually taught separately from technical work and frequently by someone from another department. Students pass it and proceed.
The syllabus is often good. The structural message is not, and it is the structural message that is retained: ethics is a distinct subject, addressed after the real work, by a different kind of specialist, with no bearing on whether your code compiles or your design is approved.
What integration looks like
The alternative is not more ethics teaching. It is the same amount, distributed differently, so that ethical reasoning appears as a component of technical competence rather than an adjacent subject.
- A data structures assignment where the specification omits a population, and the omission is part of the mark.
- A systems design brief that includes a decommissioning plan, assessed as rigorously as the architecture.
- A code review exercise where the defect is a defensible-looking default with a distributional consequence.
- A capstone project required to state what it would take to withdraw the system.
Why it rarely happens
Integration requires the technical faculty to teach it, which requires them to be confident in material they were not trained in and are not assessed on. A standalone module requires one member of staff and no change to anyone else’s course. Institutions choose accordingly, and reasonably, given the incentives they face.
Our educational programme releases integrated assignment material for reuse and adaptation, specifically so that the marginal cost to a technical lecturer is close to zero. That is the only version of this argument that has ever changed a curriculum.
