9 papers:
ICEIS-v1-2015-Mocker #complexity #how- Complexity in the Digital Age — How can IT Help, not Hurt (MM), p. IX.
ICSE-2014-WagstromD #development #scalability- Does latitude hurt while longitude kills? geographical and temporal separation in a large scale software development project (PW, SD), pp. 199–210.
CHI-2013-LeeH #consistency #online- Does slacktivism hurt activism?: the effects of moral balancing and consistency in online activism (YHL, GH), pp. 811–820.
- CHI-2011-SauroL #design #question #usability
- When designing usability questionnaires, does it hurt to be positive? (JS, JRL), pp. 2215–2224.
ICML-2011-LiZ #towards- Towards Making Unlabeled Data Never Hurt (YFL, ZHZ), pp. 1081–1088.
ISSTA-2007-TzorefUY #automation #concurrent #debugging- Instrumenting where it hurts: an automatic concurrent debugging technique (RT, SU, EYT), pp. 27–38.
SPLC-2004-Krueger #product line #what- Product Line Binding Times: What You Don?t Know Can Hurt You (CWK), pp. 305–306.
DAC-2002-BrodersenHKKLK #design #question #what- Nanometer design: what hurts next...? (RWB, AMH, JK, DK, MAL, MK), p. 242.
KDD-2001-PadmanabhanZK #personalisation #semistructured data #what- Personalization from incomplete data: what you don’t know can hurt (BP, Z(Z, SOK), pp. 154–163.
