Tuesday, October 29, 2013
Responsible Software Development
I'm certain that a fair amount of people would consider the nuts and bolts of software design to be the basis for ethical discussion in the field, but I'd like to posit the idea that the majority of the responsibility for the development of an ethically appropriate product falls to the developers instead of the designers.
Designers come up with frameworks, workflow, ideas, things that in their infancy are completely intangible, and the way those ideas in their gestation become functioning products sometimes leaves the mind less grandeur, and more disappointment. The designers mean well, but in an environment where the people with the plans are not the same people doing the building, inevitably the plan will have to change; and in a well conditioned work environment, that system of change should be easy. The developers on the ground level of the project should be able to speak about the functionality, feasibility, and efficacy of the product at any point in its construction. In this way, deadlines can be kept, profit margins can be maintained, and, most importantly, the product that is being developed will be as ethically sound in its engineering as it is in its design. Preservation of this type of communication is key to being able to responsibly function in a software-based workspace, as without it the flaws that are discovered to be inherent to the nature of the project cannot be discussed, and as such, a product will be produced that does not work as it was intended to work, and that is irresponsible.
Outside of the communication about the design process, developers also must maintain their integrity in their individual work. The final outcome of the project rests on the trust that the team has in their ability to complete the task to the best of their ability, and to be honest about its flaws. The individual developer must be willing to work through the most difficult problems in a project, and not take shortcuts that would hurt the product but increase his efficiency. He must keep the goal of having as near to a perfect product in his mind at all times. With that mindset, he can go about his work ensuring that the bugs and issues that he finds will be rectified, and that at the end of the project, he has completed his work to the absolute best of his ability.
With these two key points in mind, we can imagine the perfect marriage of design and development. An environment in which communication is open, individuals maintain their integrity and moral compass, and everyone involved in the project is working their hardest to see the task fulfilled exceptionally. It is a hard standard to try to hold to, but if it could be achieved, the quality of the products coming out of that team would be only limited to the capabilities of the people working in it, and there would be no need for concern about whether or not the product meets ethical standards.
Subscribe to:
Posts (Atom)