Tuesday, March 27, 2018

Looking at Facebook's perspective - EthicalCS - Day 2

Continuing on what we did yesterday, I had students turn in their research.  Students had a good range of different articles they read from their options.  I tried to give them a mix of topics for different interest areas.  I was concerned they would find the 3 shortest articles and call it a day, but for the most part students seemed to pick questions that interested them.

Here were their choices:


Students filled out this reading guide that asked them to raise their own ethical questions from what they read and also think about who was at fault and who had responsibility to build off what we talked about yesterday.

From there, we listened The Daily podcast of the day which reported on an interview with Facebook's Mark Zuckerberg. 

It was a nice complement to the previous day's podcast which talked about the Cambridge Analytica side of things more.  

Once again, I created a listening guide to help students stay engaged.  It worked.  It is so clear that you need to put a relevant question that is in the last 15 seconds of what you want students to listen to - as soon as they "get" the last question, they tune out.




One thing I realized is that I listened to these podcasts multiple times to make the reading guide and just to preview them.  Students only heard them once, and while I made the listening guide to help them through the story, it is a complicated story.  At the end of the listening guide, students needed to create a list of "players" or "characters" in this story.  They were eager to put down Mark Zuckerberg, which was fair, but I wanted them to think about who was the individual AT Facebook who actually did something in this story - what types of job titles did they have?

From there we made a character web with how people are connected.  Here was my rough draft.



I wanted student to think about what ethical responsibilities/roles each of these people played.  While I think I talked a bit too much here, I think there would have been an opportunity to have students think about this more themselves.  The tricky thing is that it is a bit of a creative writing exercise - they don't know how companies are typically organized - that there are thousands of departments in Facebook and most likily several of them played a part in this (from sales, to legal, to ad revenue, to the engineers who decide how much data developers have access to... it's a lot).

Finally, I wanted students to see that "using data" has happened forever - in fact, the wise use of data is how Obama was able to put together such amazing campaigns.  They got their data legally, but they used it in similar ways to Cambridge Analyitca.  There is this great MIT Technology Review issue that talks about how big data has "put the soul back into politics" from 2013 after Obama got re-elected.  I showed it to students to A) make the story a bit more balanced, and B) drive home that this has been brewing for a while.  While we were praising big data before, now we are questioning if it is the right thing to do.



On Day 3, I am going to pull away from the data side of ethics and try to put a nice end on the #EthicalCS detour. 

Friday, March 23, 2018

An EthicalCS Attempt - Day 1

Inspired by this tweet (which, BTW, the whole thread is worth reading)...



...and by Saber Khan's #EthicalCS chats on Twitter, I decided to take on a "EthicalCS" detour.  I think it ties directly into AP CSP's global impact piece and seems super timely with the Cambridge Analytica thing going on.

My goals were as follows:
  • Bring in real-world situations
  • Challenge students' assumptions about ethics in computing
  • Show how programmers (and others) are responsible for privacy
  • Demonstrate trade-offs with technology

To be honest, I could have made this go in 100 different directions.  There are SO MANY connections to be made here.

Big picture, over the course of 3 days, it ended up looking like this:

  1. Listsen to a podcast (then discuss)
  2. Have students read articles related to ethics in CS
  3. Listen to another podcast (then discuss)
  4. Watch a video (then discuss)
  5. Develop a "Code of Ethics" of Computer Scientists

I have been listening to The Daily podcast and they had an episode about the Cambridge Analyica story that was concise and, I thought, engaging.  Also learning from videos I have shown, I needed to have a way to hold students accountable to listening.  I gave them a "Listening Guide" where I came up with questions which could be directly answered from listening to the podcast.  We did this in class too which helped with actual completion.

SO... here is how it went.

Day 1: Introduce the Ideas of Ethical CS

On day 1 we listened to The Daily podcast from 3/21.  It talks a bit more about the logistics of the story.  Specifically, it covers how the news broke and who the key players are.  Listen to it, if you don't know the story!

I also had students fill out this reading guide (shown below).  The first questions are all directly answerable from the podcast but I also wanted to give students some lingering questions to think about.





I talked a bit about the difference between "fault" and "responsibility" at the beginning of class.  This was actually something that was raised in my church one week and it really resonated with me.  Will Smith also has a bit on it too, but they take it in more of a personal direction, which, while still good, isn't the direction I wanted to take it.  I described it as, if I find a baby in the middle of a street, it is not my fault the baby is there, but it is my responsibility to do something about it.  I suppose if I knew more about laws I could talk about legal fault, but... I don't.  I asked students to keep in mind "Who is at fault and who has responsibility?" in this story.

For the most part the listening went well with the guide.  After it was done, students discussed the last two questions:

  • What was Facebook’s “fault” in this story?
  • What was/is Facebook’s “responsibility” in this story?
When reading student responses, it was fascinating to see that most students felt like the only thing Facebook did wrong was not tell the public immediately when the learned that someone had this information that shouldn't have that information.  From most students' perspectives, had Facebook just said "hey, this happened" right away, then they would be in the clear. 

This reminds me a lot of student thinking.  "If I am honest about a bad thing I did, I won't have any consequences".  They were applying that same logic to this situation.  I needed to push back more on this idea of what "bad thing" happened. So, I asked, what was "bad" about this story.  Here were their responses in order:
  • Not alerting people their data was stolen
  • Selling data after it had been used for academic purposes 
  • Not being clear about how the data was going to be used
  • Playing on people's fears 
    • Note: This was an interesting side conversation about would "playing on people's hopes be any better" - we decided no.
So, we were getting closer to some important ideas. 

That took about 30 minutes total and then I had students take a test.

After the test, students had to choose from 8 different CS-ethics-related articles and fill out a short worksheet on them.

NEXT... reviewing what students researched...