Tag #harmful
18 papers:
SCAM-2019-PaixaoM #code review #empirical #overview #scalability- Rebasing in Code Review Considered Harmful: A Large-Scale Empirical Investigation (MP, PHMM), pp. 45–55.
ICSME-2016-XiaBLL #automation #case study #debugging #fault #locality #scalability #user study #using- “Automated Debugging Considered Harmful” Considered Harmful: A User Study Revisiting the Usefulness of Spectra-Based Fault Localization Techniques with Professionals Using Real Bugs from Large Systems (XX0, LB, DL0, SL), pp. 267–278.
Haskell-2016-MokhovMJM #recursion #scalability- Non-recursive make considered harmful: build systems at scale (AM, NM, SPJ, SM), pp. 170–181.
IFL-2014-KoopmanPJ #data type #encoding #functional #implementation- Church Encoding of Data Types Considered Harmful for Implementations: Functional Pearl (PWMK, RP, JMJ), p. 4.
LCT-NLE-2014-PurgathoferL #architecture #layout- Layout Considered Harmful: On the Influence of Information Architecture on Dialogue (PP, NL), pp. 216–225.
ICSE-2013-KocaguneliZBNM #development #distributed #question- Distributed development considered harmful? (EK, TZ, CB, NN, TM), pp. 882–890.
ASPLOS-2013-ParkBCLN #manycore #memory management- Regularities considered harmful: forcing randomness to memory accesses to reduce row buffer conflicts for multi-core, multi-bank systems (HP, SB, JC, DL, SHN), pp. 181–192.
OSDI-2010-XiongPZZM #ad hoc- Ad Hoc Synchronization Considered Harmful (WX, SP, JZ, YZ, ZM), pp. 163–176.
CHI-2009-CrabtreeRTB - Ethnography considered harmful (AC, TR, PT, GB), pp. 879–888.
ICSM-2008-BettenburgPZK #debugging #question- Duplicate bug reports considered harmful ... really? (NB, RP, TZ, SK), pp. 337–345.
CHI-2008-GreenbergB #evaluation #usability- Usability evaluation considered harmful (some of the time) (SG, WB), pp. 111–120.
WCRE-2006-KapserG - “Cloning Considered Harmful” Considered Harmful (CK, MWG), pp. 19–28.
OSDI-2004-WalfishSKBMS - Middleboxes No Longer Considered Harmful (MW, JS, MNK, HB, RM, SS), pp. 215–230.
OOPSLA-2001-AlpernCFGL #implementation #interface #java #performance- Efficient Implementation of Java Interfaces: Invokeinterface Considered Harmless (BA, AC, SJF, DG, DL), pp. 108–124.
TOOLS-EUROPE-1999-Simons #case study- Use Cases Considered Harmful (AJHS), pp. 194–203.
IWPC-1998-BrandSV #legacy #parsing- Current Parsing Techniques in Software Renovation Considered Harmful (MvdB, MPAS, CV), pp. 108–117.
ECHT-1990-Young - Linking Considered Harmful (LDY), pp. 238–249.
SEI-1989-Friedman #education #re-engineering- A Separate Undergraduate Software Engineering Curriculum Considered Harmful (FLF), pp. 267–270.