Technology Ethics in Action: Critical and Interdisciplinary Perspectives
📖 Description
SPECIAL ISSUE ON TECHNOLOGY ETHICS IN ACTION: CRITICAL AND INTERDISCIPLINARY PERSPECTIVES Editorial i ?ii The Contestation of Tech Ethics: A Sociotechnical Approach to Technology Ethics in Practice Ben Green 209?225 Framing and Language of Ethics: Technology, Persuasion, and Cultural Context Jasmine E. McNealy 226?237 Tech Ethics: Speaking Ethics to Power, or Power Speaking Ethics? Lily Hu 238?248 Data Science as Political Action: Grounding Data Science in a Politics of Justice Ben Green 249?265 From Ethics Washing to Ethics Bashing: A Moral Philosophy View on Tech Ethics Elettra Bietti 266?283 The Promise and Limits of Lawfulness: Inequality, Law, and the Techlash Salom ? Viljoen 284?296 Vol.?2,?No.?3,?September?2021? CONTENTS? Apologos: A Lightweight Design Method for Sociotechnical Inquiry Luke Stark 297?308 Creating Technology Worthy of the Human Spirit Aden Van Noppen 309?322 Real Estate Politik: Democracy and the Finan...
📊 Game Impacts
Not verified in gameWhich variables this event was proposed to move, and in which direction. The magnitudes are held in the corpus but are not shown here, because they have not been verified against the shipped game. They come from pdoom-data. They describe what an event was proposed to do, not what the shipped game does with it. Most events in the corpus are flavour: they are shown for colour and do not move any game variable. Only a small minority reach the systems below, and several of the variables listed here are not read by the game at all yet. Treat this table as a design proposal under review, not as a measurement of play. Corrections and arguments are welcome — the suggestion links at the foot of this page go straight to the data repo.
| Variable | Direction | Condition |
|---|---|---|
| Research | proposed: up | Always |
| Papers | proposed: up | Always |
| Vibey Doom | proposed: up | Always |
💭 Reactions
🔗 Sources
🤝 Found an Issue?
This event data is sourced from the pdoom-data repository. If you notice errors or want to suggest improvements:
GitHub Issue (Preferred) 📧 Email (No GitHub)