Ethics are important in any which way you look at stuff. They’re there to make sure people behave in a certain standard, to help us see what’s good and bad, to let us regulate our actions to other people and ourselves. I think that it goes without saying that in software engineering there exist a code of ethics to fulfill what was previously mentioned. One of the most prominent, and well developed code is the ACM code. Now, before I go into the code of ethics I would also like to add that this is not the only code that has been developed in order to maintain a correct management of work done by software engineers. However, it is the code that has maintain quite a bit of relevance throughout the years. Now, how about we get right to it:
1st Principle: The Public
Now it’s also important to have the public in your mind. A software engineer also needs to ensure that even when acting towards the best interest of their client, they should also have a consistence with the public interest.
2nd Principle: Client and employer
Kind of goes along with the previous principle. There must be a stated relationship between client and employer that ensures that the employer will do the best for the interest of its client. Without affecting in a negative way the public of course.
3rd Principle: The Product
When you buy something you tend to expect a certain standard of quality. Doesn’t matter if it’s apples or a brand new computer. You expect for the person producing or providing the service you’re paying for will be of acceptable quality for all the parties involve. In software engineering is pretty much the same. A software engineer needs to make sure there’s
4rth Principle: The Judgment
Judgment is important for any action that is made. In software engineering, the person developing the product must maintain its integrity and independence of their own professional judgment.
5th Principle: Management (This one doesn’t have “The” because it would look weird)
In software engineering is really important for supervisors, managers, and leaders make sure to endure, and promote a proper representation of the ethics code. This is so that the employers can have a clear understanding of how to act in a professional way. Monkey sees; monkey does. Just kidding, but it is important.
6th Principle: Profession
Software engineers should aim to improve in the integrity and reputation of the profession, or at least keep it in the state that it is. Basically try to give the profession a good reputation. Shouldn’t be that hard. Right?
7th Principle: The Colleagues
A software engineer should helpful, supportive, and fair with its colleagues and the people involved in its work place. Be nice. It’s not that hard, guys.
8th Principle: Self
A very important thing about ethics that a few people seem to forget sometimes is that ethics are there to help YOU out too, not only others. As a software engineer it’s important to stay up to date with papers and articles related to the practice, and to promote the ethics code.
That’s it, well, at least the short version. If you want to check out the full, and detailed ethics code you can check it right here. Also if you want to check out the blogs of the nice people that also worked in the beautiful diagram you saw at the beginning here’s their links: Carlos Rueda, Adler Zamora, Juan Carlos Sanchez, and Alfoso Iraí
