| 2013 | ||
|---|---|---|
| c19 | Beth Simon, Julian Parris, Jaime Spacco: How we teach impacts student learning: peer instruction vs. lecture in CS0. SIGCSE 2013: 41-46 | |
| c18 | David Hovemeyer, Matthew Hertz, Paul Denny, Jaime Spacco, Andrei Papancea, John Stamper, Kelly Rivers: CloudCoder: building a community for creating, assigning, evaluating and sharing programming exercises (abstract only). SIGCSE 2013: 742 | |
| 2012 | ||
| c17 | Hannah Fidoten, Jaime Spacco: What do computer scientists do?: a survey of CS and non-CS liberal arts faculty. ITiCSE 2012: 279-284 | |
| c16 | Hannah Fidoten, Jaime Spacco: Do faculty recognize the difference between computer science and information technology?: a survey of liberal arts faculty (abstract only). SIGCSE 2012: 665-666 | |
| 2009 | ||
| c15 | Jaime Spacco, Chadd C. Williams: Lightweight Techniques for Tracking Unique Program Statements. SCAM 2009: 99-108 | |
| 2008 | ||
| c14 | Chadd C. Williams, Jaime Spacco: SZZ revisited: verifying when changes induce fixes. DEFECTS 2008: 32-36 | |
| c13 | ||
| 2006 | ||
| c12 | Jaime Spacco, David Hovemeyer, William Pugh, Fawzi Emad, Jeffrey K. Hollingsworth, Nelson Padua-Perez: Experiences with marmoset: designing and using an advanced submission and testing system for programming courses. ITiCSE 2006: 13-17 | |
| c11 | Jaime Spacco, David Hovemeyer, William Pugh: Tracking defect warnings across versions. MSR 2006: 133-136 | |
| c10 | Jaime Spacco, William Pugh, Nathaniel Ayewah, David Hovemeyer: The Marmoset project: an automated snapshot, submission, and testing system. OOPSLA Companion 2006: 669-670 | |
| c9 | Jaime Spacco, William Pugh: Helping students appreciate test-driven development (TDD). OOPSLA Companion 2006: 907-913 | |
| 2005 | ||
| j2 | Jaime Spacco, Jaymie Strecker, David Hovemeyer, William Pugh: Software repository mining with Marmoset: an automated programming project snapshot and testing system. ACM SIGSOFT Software Engineering Notes 30(4): 1-5 (2005) | |
| j1 | Jaime Spacco, William Pugh: RUBiS Revisited: Why J2EE Benchmarking is Hard. Stud. Inform. Univ. 4(1): 25-30 (2005) | |
| c8 | Jaime Spacco, Jaymie Strecker, David Hovemeyer, William Pugh: Software repository mining with Marmoset: an automated programming project snapshot and testing system. MSR 2005 | |
| c7 | David Hovemeyer, Jaime Spacco, William Pugh: Evaluating and tuning a static analysis to find null pointer bugs. PASTE 2005: 13-19 | |
| 2004 | ||
| c6 | Jaime Spacco, David Hovemeyer, William Pugh: An Eclipse-based course project snapshot and submission system. ETX 2004: 52-56 | |
| c5 | William Pugh, Jaime Spacco: RUBiS revisited: why J2EE benchmarking is hard. OOPSLA Companion 2004: 204-205 | |
| c4 | Polyvios Pratikakis, Jaime Spacco, Michael W. Hicks: Transparent proxies for java futures. OOPSLA 2004: 206-223 | |
| 2003 | ||
| c3 | Konstantin Berlin, Jun Huan, Mary Jacob, Garima Kochhar, Jan Prins, William Pugh, P. Sadayappan, Jaime Spacco, Chau-Wen Tseng: Evaluating the Impact of Programming Language Features on the Performance of Parallel Applications on Cluster Architectures. LCPC 2003: 194-208 | |
| c2 | William Pugh, Jaime Spacco: MPJava: High-Performance Message Passing in Java Using Java.nio. LCPC 2003: 323-339 | |
| 2002 | ||
| c1 | ||
Data released under the ODC-BY 1.0 license — See also our legal information page