From caac3d2b36932c8cea9b323537e523846279f472 Mon Sep 17 00:00:00 2001 From: Andy Ko Date: Tue, 30 Apr 2019 11:15:53 -0700 Subject: [PATCH] Cited Beller et al. --- debugging.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debugging.html b/debugging.html index 4e08f6a..beddfe3 100644 --- a/debugging.html +++ b/debugging.html @@ -32,6 +32,7 @@ Somewhere in its implementation there's a line of code, or multiple lines of code, that, given a particular set of inputs, causes the program to fail. How do you find those defective lines of code? You debug, and when you're doing debugging right, you do it systematically (Zeller 2009). + And yet, despite decades of research and practice, most developers have weak debugging skills, don't know how to property use debugging tools, and still rely in basic print statements (Beller et al. 2018).

Finding the defect

@@ -95,6 +96,7 @@

Jorge Aranda and Gina Venolia. 2009. The secret life of bugs: Going past the errors and omissions in software repositories. In Proceedings of the 31st International Conference on Software Engineering (ICSE '09). IEEE Computer Society, Washington, DC, USA, 298-308.

+

Beller, M., Spruit, N., Spinellis, D., & Zaidman, A. (2018, May). On the dichotomy of debugging behavior among programmers. In 2018 IEEE/ACM 40th International Conference on Software Engineering (ICSE) (pp. 572-583).

Nicolas Bettenburg, Sascha Just, Adrian Schröter, Cathrin Weiss, Rahul Premraj, and Thomas Zimmermann. 2008. What makes a good bug report? In Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering (SIGSOFT '08/FSE-16). ACM, New York, NY, USA, 308-318.

Gilmore, D. (1991). Models of debugging. Acta Psychologica, 78, 151-172.

Andrew J. Ko and Brad A. Myers. 2008. Debugging reinvented: asking and answering why and why not questions about program behavior. In Proceedings of the 30th international conference on Software engineering (ICSE '08). ACM, New York, NY, USA, 301-310.