12 papers:
PLDI-2015-SiekTW- Blame and coercion: together again for the first time (JGS, PT, PW), pp. 425–435.
ICFP-2015-KeilT #contract #higher-order- Blame assignment for higher-order contracts with intersection and union (MK, PT), pp. 375–386.
- ICFP-2013-Garcia
- Calculating threesomes, with blame (RG), pp. 417–428.
SOSP-2013-XuZHZSYZP- Do not blame users for misconfigurations (TX, JZ, PH, JZ, TS, DY, YZ, SP), pp. 244–259.
ICST-2012-ChenLYS #question #testing #user interface #what- When a GUI Regression Test Failed, What Should be Blamed? (JC, ML, KY, BS), pp. 467–470.
POPL-2011-AhmedFSW- Blame for all (AA, RBF, JGS, PW), pp. 201–214.
- POPL-2011-DimoulasFFF #contract
- Correct blame for contracts: no more scapegoating (CD, RBF, CF, MF), pp. 215–226.
- POPL-2010-SiekW
- Threesomes, with and without blame (JGS, PW), pp. 365–376.
ESOP-2009-WadlerF #source code- Well-Typed Programs Can’t Be Blamed (PW, RBF), pp. 1–16.
OCSC-2009-OganAKJ #education #game studies #learning #question #social- Antecedents of Attributions in an Educational Game for Social Learning: Who’s to Blame? (AO, VA, JK, CJ), pp. 593–602.
FSE-2008-KingJJS #data flow #effectiveness- Effective blame for information-flow violations (DK, TJ, SJ, SAS), pp. 250–260.
ML-1991-WeintraubB #fault #generative #knowledge base- Generating Error Candidates for Assigning Blame in a Knowledge Base (MAW, TB), pp. 33–37.
