Why the ACM Code of Ethics Matters More Than Ever
During my time studying Computing at Sheffield Hallam University, one of my tutors introduced me to the ACM Code of Ethics. At first, it felt like one of those documents that sits in the background, important in theory, but easy to overlook when you’re focused on building projects and learning technical skills. But the more I worked on real systems, especially those involving data and IoT, the more I realised how relevant it actually is.
The ACM Code of Ethics puts a strong emphasis on doing work that benefits society and contributes to human well-being. That idea has stuck with me. It sounds simple, but in a world where technology can be used in so many different ways, it’s actually a powerful filter for decision-making. Just because something can be built doesn’t always mean it should be built. The question becomes: who does this help, and is it genuinely improving things?
All of my projects so far have been guided by that mindset, even before I fully understood where it came from. For example, I’ve worked on systems designed to test water quality and help monitor environmental conditions. I’ve also been involved in projects aimed at supporting an organic farming co-op, using IoT devices to collect and analyse data that can help improve crop management. These kinds of applications feel worthwhile because they solve real problems for real people.
One thing I’ve become increasingly certain about is what I don’t want to work on. I have no interest in collecting biometric data from random strangers or even from people I know, especially without a very clear, ethical justification. There is a growing trend in tech to gather as much data as possible simply because it’s valuable, but that approach raises serious questions about privacy, consent, and long-term impact. The ACM Code of Ethics makes it clear that these concerns shouldn’t be an afterthought they should be central to the design process.
What excites me about technology is its potential to improve everyday life in practical, meaningful ways. IoT, embedded systems, and software development can be used to make systems more efficient, reduce waste, and save people time. For example, improving energy efficiency through better monitoring systems can reduce both costs and environmental impact. Optimising workflows can help workers spend less time on repetitive tasks and more time on meaningful work. Even something as simple as reducing unnecessary travel through better data and coordination can have a significant cumulative effect.
There’s also a huge opportunity to make services more accessible and cost-effective. With the right systems in place, it’s possible to deliver better outcomes using fewer resources. That’s not just good engineering, it’s good for society. It means that more people can benefit from services that might otherwise be too expensive or inefficient to provide.
The ACM Code of Ethics reinforces the idea that as developers and engineers, we have a responsibility that goes beyond just writing code. We are shaping systems that people rely on, often without even realising it. That comes with a level of accountability. It means thinking carefully about the impact of our work, not just in the short term, but in the long term as well.
For me, the goal is straightforward: use technology to make things better. That could mean improving efficiency, reducing environmental impact, or helping people make better decisions through access to data. It doesn’t have to be complicated or ground breaking, it just has to be useful and ethical.
Looking back, being introduced to the ACM Code of Ethics was more important than I realised at the time. It provided a framework for thinking about the kind of work I want to do and the kind of developer I want to be. In an industry that moves quickly and often prioritises innovation above all else, having that kind of grounding is essential.
Comments