--

This is an excellent starting point! While I can respect your intention here, and I certainly agree with the intents of your modified Hippocratic oath, I sadly don't believe that such an oath would make much difference even if it were to be adopted.

In practice, the output of most software engineering is determined not by the developers who write the code, but by the employers and customers who dictate the requirements and timelines.

All engineering is compromise, you have a problem to solve with limited resources and, one way or another, it's almost impossible to produce a product without making trade-offs.

What we need, in my opinion, is a licensing body just like other engineering disciplines have. One in which your oath could form the basis of the requirements to obtain a license, one which would only accredit engineers who have been trained accordingly, one which would have the authority to revoke one's license should one contravene any of the principles embodied in it.

This would provide a mechanism not just to demand adherence to best practices on the part of the developers acting on their own initiative, but also to encourage and empower them to refuse to cooperate with any employer or client demanding that they violate their commitment to quality ethical coding for whatever reason. Anyone using software produced by licensed engineers could expect the professional levels of quality and safety, and any developer being pushed to cut corners would be putting their license on the line and hurting their reputation and career.

--

--

Adam Fisher / fisher king (@therightstuff)
Adam Fisher / fisher king (@therightstuff)

Written by Adam Fisher / fisher king (@therightstuff)

Software developer and writer of words, currently producing a graphic novel adaptation of Shakespeare's Sonnets! See http://therightstuff.bio.link for details.

No responses yet