DEV Community 👩‍💻👨‍💻

Cover image for DevDiscuss S2E4: Ethics in Code
Jess Lee for The DEV Team

Posted on

DevDiscuss S2E4: Ethics in Code

We always say that the DevDiscuss podcast is about tackling the burning questions in tech that affect all our lives as developers. This week’s topic is one that fits that description to a T: Ethics. Ethical challenges and triumphs, which have been especially visible and centered in tech news over the past few years, and rightfully so. I’m sure you can think of quite a few ethical dilemmas that you, your team, or various high-profile companies have faced throughout your experience in an increasingly technical world.

play pause DevDiscuss

@ben and I were joined by two guests for this episode:

  • Nashlie Sephus is the CTO of Partpic, which was acquired by Amazon in 2016. They are now an Applied Science Manager at Amazon Web Services.
  • Abram Walton is the Director of the Center for Lifecycle Innovation Management and former Director for the Center of Ethics and Leadership at the Florida Institute of Technology.

In this episode, Ben, Nashlie, Abram, and I discuss

  • Fairness and bias in AI
  • Ethical considerations in tech leadership
  • The role of regulation in technology

... and much more!

Listen to S2E4 of DevDiscuss: today! If you enjoy it, please consider leaving us a review on the podcast platform of your choice. We’ll mail you a FREE pack of DEV stickers if you send us a screenshot of your review! All you have to do is fill out this form 🦄⚡🎨


Quick Listening Links


Huge thanks to @levisharpe for producing & mixing the show, and @peter and @saronyitbarek for their editorial oversight.

Thank you to our Season 2 sponsors who help make this show possible. If you're in the market for any of their services, please check out:

Top comments (0)

Timeless DEV post...

How to write a kickass README

Arguably the single most important piece of documentation for any open source project is the README. A good README not only informs people what the project does and who it is for but also how they use and contribute to it.

If you write a README without sufficient explanation of what your project does or how people can use it then it pretty much defeats the purpose of being open source as other developers are less likely to engage with or contribute towards it.