4:50 The reason Engineering became a profession in Canada was because of disasters that had happened and the need for governance around ethics and standards. This is currently missing in software development

5:20 Discussing some recent examples of unethical behaviour in software development

5:40 The software development is judged in the eyes of the public because of unethical behaviour and this erodes the trust

6:15 Does building a line of business or point of sale software product need the same level of governance as software that can cause injury or death?

6:36 The impact of software extends into the socio-economic institutions of society and the borders become very unclear around where a software product can cause harm

6:55 Examples of software products which could be used to cause public harm

7:15 Machine learning systems that entrench and amplify racial and other biases into such things as hiring processes

7:55 Unlike the failure of a bridge or a physical construct, these effects from software will be less visible and more insidious

8:10 An example of a machine learning system used in hiring that was deployed and built with a bias against the CVs of people who had an African American name

8:40 The importance of running the tests and experiments to expose the bias in machine learning systems

8:45 The software professional needs to be aware of the consequences of how the program will be used

8:57 The need and the challenge to include this in the training of software professionals globally

9:12 The goal of Chris and Sean’s talk is to start the conversation – they don’t claim to have the answers

10:05 Discussing the content of the code of professional ethics of the Association of Professional Engineers and Geoscientists of Alberta

10:09 Hold paramount the public interest and regard for the environment – this may be in conflict with the interests of our employers

10:35 The way the Engineering profession includes and emphasizes this right from the first year of training

11:25 The way the engineering profession prepares engineers to be able to stand up for what is right over what is expedient

11:50 The requirement on the professional to “uphold the dignity and honour of the profession” and what that means

12:25 The importance of continued education and representing the profession well

12:47 Discussing how this could impact on entry into the software profession – where do you draw the line between needing professional accreditation and being a hobbyist or self-taught developer?

13:25 What steps can we take within our organisations to instil a sense of responsibility that is beyond getting the product out the door quickly?

14:15 Discussing different examples that came up in the conversations around their talk

15:03 What about the situation where some or all of a product development is outsourced to a third party – who carries the responsibility for the ethical aspects of that product?

15:45 The need to move towards an agile approach which has total ownership of the outcomes become the team’s responsibility

15:52 A core tenant of professionalism is we cannot detach our actions from the outcomes – ignorance is not an excuse

16:10 Bad ethical outcomes are a result of the culture of the organisation – they don’t happen in isolation

17:12 Where there is an external authorizing body the consequences of unethical behaviour are such that people are more likely to say “no” when faced with an unethical choice (go to prison vs lose your job)

More about our podcasts

You can keep up to date with the podcasts via our RSS Feed, and they are available via SoundCloud and iTunes. From this page you also have access to our recorded show notes. They all have clickable links that will take you directly to that part of the audio.

Is your profile up-to-date? Please take a moment to review and update.

Email Address

Note: If updating/changing your email, a validation request will be sent

Company name:

Keep current company name

Update Company name to:

Company role:

Keep current company role

Update company role to:

Company size:

Keep current company Size

Update company size to:

Country/Zone:

Keep current country/zone

Update country/zone to:

State/Province/Region:

Keep current state/province/region

Update state/province/region to:

Subscribe to our newsletter?

Subscribe to our architect newsletter?

Subscribe to our industry email notices?

You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.

We notice you're using an ad blocker

We understand why you use ad blockers. However to keep InfoQ free we need your support. InfoQ will not provide your data to third parties without individual opt-in consent. We only work with advertisers relevant to our readers. Please consider whitelisting us.