How do you build tech you won't regret? Who is responsible for the code that is released? How do you make tech ethics considerations, including privacy, security, accessibility and inclusion, a part of your regular agile feedback and review processes?
Some slides transferred poorly from keynote to powerpoint so here are the blanks filled in:
Slide 6: “We kill people based on metadata.” — Michael Hayden (former NSA and CIA director)
Slide 21: "“The most dangerous phrase in the language is, ‘We’ve always done it this way’.” —Grace Hopper (computer scientist, candidate for Most Badass American Award)
Slide 31: “Don’t build something if you don’t have the budget to build the security infrastructure properly. Knowing your limits is also important to behave ethically.” — Ádám Sándor (cloud tech consultant)
Slide 32: "Whose problem is it if data gets stolen? Was it devs not thinking, ops not securing or management not giving enough budget? In these situations, it’s very easy to think ‘This isn’t my own problem, I’m just a cog in the machine.'” — Ádám Sándor (cloud tech consultant)