Yash Barve

Introduction

Today, computing technology is not just a peripheral tool but the fundamental infrastructure of global society. Hence, the role of a computing professional has evolved from being purely technical into one of significant social and ethical impact. Professional bodies have established frameworks like the Association of Computing Machinery’s Code of Ethics and Professional Conduct (the Code) to serve as a moral compass. However, applying these ideals in practice often creates friction in today’s high-stakes industry. The need for rapid innovation, significant competitive advantage, and aggressive growth cycles often requires professionals to redefine their ethical and moral responsibilities.

This essay will examine the core tenets of the ACM Code, focusing on its commitment to public well-being and professional integrity. Following this summary, I will outline my own ethical standards, and discuss how they align with the Code and the ethical practices followed in today’s computing organizations.

The ACM Code of Ethics

The Code serves as the definitive moral framework for the computing profession. The Code is designed to express the conscience of the profession. It is structured into four distinct sections, beginning with broader moral principles and narrowing down to professional responsibilities and leadership obligations.

The foundational section 1 outlines General Ethical Principles. The core objective of all principles is the “public good.” This section requires professionals to contribute to human well-being, avoid harm, and be honest and trustworthy. It emphasizes social justice through fairness and avoidance of discrimination. Specifically, principle 1.6 describes the responsibility of respecting privacy and principle 1.7 highlights the duty to honor confidentiality. This is particularly critical in today’s era of pervasive data collection.

Section 2 transitions to Professional Responsibilities, and is the most significant for individual employees or practitioners. It insists on high-quality processes and products, while maintaining professional competence. The two especially significant principles in this section are principles 2.5 and 2.6. Principle 2.5 emphasizes the need for comprehensive evaluations of risks, and principle 2.6 emphasizes accepting work only when it can be performed competently, seeking training, review, or expert guidance when needed. This section also underpins the necessity of designing systems that are “robust and usably secure.” Security breaches are not just a technical failure, but are also capable of causing real-world harm from an ethical point of view.

Section 3 addresses Professional Leadership Principles. It highlights that those in positions of influence bear a heightened responsibility of enhancing the quality of working life and creating opportunities for professional growth. Finally, section 4 focuses on compliance. The principles in this section primarily encourage professionals to uphold and promote the Code as a condition of professional membership. To summarize, the Code establishes that technical excellence is inseparable from ethical excellence.

My Ethical Standards - Pragmatic Excellence

My personal ethical standards are grounded in a philosophy that I call ‘Pragmatic Excellence.’ While I share the Code’s view that all computing actions must ultimately contribute to societal well-being, I believe that the path to that well-being requires a more nuanced approach. My views slightly differ from that of the Code in terms of the boundaries and corporate transparency.

Supervised Stretching

First, regarding professional development, I believe in Supervised Stretching. The Code’s Principle 2.6 emphasizes that professionals should accept work only when they can perform it competently, and that they should seek training, review, or expert guidance when needed. In fast-moving fields, professionals often have to learn several skills on the go. For example, in several of my co-op terms at different organizations, I have rarely possessed the complete skill set required at work on the first day of my employment. It has always been expected of me to pick up new skills and get up to speed with the processes and practices at the organization. However, ethically, it is important to ensure that learning does not create unmanaged risk. Therefore, I believe that employees should be encouraged to push beyond their current skills to solve newer problems. However, they should be supervised by a domain expert. By balancing the drive for innovation with oversight of experienced mentors, a professional can fulfill their duty to improve their competence without violating the ethical responsibility of avoiding harm through ignorance.

Strategic Secrecy

Second, I hold a nuanced view about Strategic Secrecy. Principle 1.3 in the Code requires honesty and trustworthiness. However, ethical practice does not necessarily require that every proprietary detail be public. In a competitive market, a company’s proprietary algorithms or unique system architectures are often what allow it to build a superior product that serves the customer better than its competitors. This is the software equivalent of a restaurant’s “secret sauce” or a food brand’s “trade secrets” that are kept hidden to maintain a market edge. However, I do draw a line at malpractice. Secrecy is a legitimate competitive right, provided there is reasonable assurance and frequent audits in place to ensure that no consumer harassment or deceptive practices are occurring. A great example of strategic secrecy is Anthropic, an AI company that calls itself a Public Benefit Corporation. Anthropic maintains a ‘closed-source’ model for its weights and parameters, arguing that absolute transparency could lead to the misuse of powerful AI. However, they negotiate this by being transparent about their AI Constitution, which is the ethical framework that governs their models’ behaviours. (Anthropic, 2026) To summarize, a computing professional’s goal must be to ensure the integrity of the outcome rather than the transparency of the process.

Shared Commitment

Finally, I believe that the ethical health of an organization depends on the degree of shared commitment among its employees. Principle 3.3 tasks leaders with enhancing the quality of working life. I would like to highlight that this “quality” is subjective and tied to a company’s mission and competition. While some organizations thrive on a standard “9-to-5” schedule, others - especially those in early stages of their lifecycles - require a mindset where employees are ready to sacrifice a portion of their personal time for the company. Ethically, it is the organization's responsibility to be transparent about these expectations during the hiring process. When a team is aligned in their dedication, “sacrifice” becomes voluntary rather than being a violation.

Alignment With the Code and Industry Reality

When reflecting on my personal ethical standards, I find that I align fundamentally with the core mission of the Code. Specifically, I hold Principle 1.1 - the obligation to contribute to societal well-being - as the highest priority for computing professionals. Software is capable of scaling quickly. Even a single decision can affect millions of people. So, ethics must be treated as part of the job rather than an add-on. I also support the mandate for robust and usable security (Principle 2.9). As a software developer, I treat the process of building secure systems not just as a technical requirement, but more as a moral duty. It is a crucial step towards being trustworthy and reliable.

Equally, I believe that the Code acts like a strong foundation for companies to base their ethical principles on. In practice, market competition and aggressive timelines force companies to reinterpret these principles. For example, business models can incentivize broad data collection even when users do not fully understand the trade-offs. This does not however invalidate the Code, but explains why applying it consistently is difficult without supporting processes and accountability. My ethical standards lie somewhere in the middle, trying to bridge the gap between the Code’s ideals and the constraints of real-world practice. Whether the profession lives up to the Code depends less on individual talent, but more on whether teams and leaders build environments where doing the right thing is feasible under pressure.