CS 2340 (Objects and Design) - Ensure that before trying to build something considering whether one SHOULD build it. Then, constantly revisiting how this software could cause harm in the software development life cycle
-
-
or somehow affects the actual *content*. For example, is a particular algorithm, proof technique, or concept inherently "militaristic"? I sometimes hear people implying the latter, but have not come across a convincing case (I don't know that any such case ever is offered).
-
By the way, I'm not a theorist (at all), so have no emotional commitment to defending theoretical approaches in CS. I simply would like to understand the criticisms that are floating around at their best.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.