In this course we will aim to understand computing's potential for good (and harm) in the context of monumental ecological, social, economic, and other forces that are reshaping our world today. This semester will have a specific emphasis on sustainability and its connection to broader notions of social good. In teams of two, you will do a self-defined, concrete, semester-long independent project with a goal of real impact. We will examine national- and global-scale challenges and more specific subproblems, and relevant technology projects. Many of the hardest ecological and social problems are intertwined in complex ways, as we will explore. While we will examine a few conventional engineering ethics topics, our aim is much broader: we will start with fundamental ecological and social challenges and then consider what role, if any, technology might play in responding to them. One of our aims will be to differentiate between nice-sounding-but-ineffective tech-for-good solutions and those that have a chance for real impact. As a result, we will take a systems perspective -- to trace root causes and find the right place(s) to make lasting change.
The course will involve discussion, presentation, and group work during class.
The reading spans a wide range of topics and provides diverse perspectives on technology, social good, and global change. A number of assigned readings and videos also examine societal challenges to provide context and deepen our understanding of the role of technology in society; these assigned readings and videos can be of an unsettling nature as they discuss problematic aspects of society. Each is accompanied by a short response assignment, due by 7pm the day before each class meeting so that everyone is prepared for in-class discussion (for example, the reading response for a Wed is due 7pm Tue). Each student will maintain a Google Doc for their reading responses, and should add each reading response to that document, with newer responses at the top of the doc; the doc should be placed within the shared Google folder and shared only with the professor.
It's highly recommended that you read each week's readings in the order listed -- each reading builds on previous ones.
In teams of two, you'll work on a semester-long independent project, culminating in a system that your team will build, test, and demonstrate to the class. You will scope out a real-world challenge that you want to address; articulate what makes solving this challenge important to society; examine possible avenues for addressing the challenge; identify key human, non-human, technological, and non-technological elements and factors in the challenge; define metrics and evaluation criteria for a possible response; and lay out milestones for the project you will develop to address the challenge. While it will be up to your team of two to meet the milestones, others in the course will be your sounding boards, beta testers, and partners in building something real, with an aim of having the project live on after the semester is over.
Projects won't have a particular form or use any specific technology -- each project will be problem dependent and it will be up to you to explore options, learn relevant technologies, and implement your project. At a high level, the first milestone will require deeply understanding and then describing the problem being solved and carving out a specific piece where computing/technology will be useful. Later milestones will depend on the project, but may include an initial prototype of software and/or hardware for the project, alpha tests with others in the class, beta tests with real users outside of class, engagement with community groups, policymakers, nonprofits, businesses, and/or other stakeholders, etc. If things go well, each project could be the kernel of something much bigger, such as a new organization (for example, a nonprofit, startup, B corp, or community group) or research initiative through which the work will live on and grow in impact.
Details of grading will be provided in class. Grades will be determined based upon the project and weekly responses to readings as follows:
60% Project (10% for each of 4 milestones, 20% for final deliverable)
40% Weekly responses
|Date||Reading Due||Assignment Due|
|M 2/14||Project Updates||Milestone 1: Progress update.|
|W 2/23||Project Updates||Milestone 2: Progress update.|
|W 3/9||Project updates||Milestone 3: Progress update.|
Guest: Jay Chen
|M 3/28||Project Checkins||-|
|M 4/4||Project Updates||Milestone 4: Progress update.|
|M 4/11||Project Updates||-|
|M 4/18||The Thing from the Future||-|
Guest: Elina Eriksson
|M 4/25||Project presentations||-|
|W 4/27||Project presentations||-|