2008
DOI: 10.1080/08993400802114698
|View full text |Cite
|
Sign up to set email alerts
|

Common sense computing (episode 4): debugging

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

1
11
0

Year Published

2009
2009
2021
2021

Publication Types

Select...
4
3
1

Relationship

2
6

Authors

Journals

citations
Cited by 25 publications
(12 citation statements)
references
References 12 publications
1
11
0
Order By: Relevance
“…To prove the finding in the literature suggesting that novices usually tinkered the code randomly [14], students were asked whether they planned how to carry out the debugging before starting it. However, the student 5 replied no and said that he always modify the code directly without any plan.…”
Section: ) Modifying the Program By Trial And Errormentioning
confidence: 99%
See 2 more Smart Citations
“…To prove the finding in the literature suggesting that novices usually tinkered the code randomly [14], students were asked whether they planned how to carry out the debugging before starting it. However, the student 5 replied no and said that he always modify the code directly without any plan.…”
Section: ) Modifying the Program By Trial And Errormentioning
confidence: 99%
“…However, most novices could not apply debugging techniques effectively. Some of them even tinkered aimlessly [14]. Therefore, addressing the importance of developing students' tracking and debugging skills is needed [2].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…In other words, students have rich preconceptions about computer science when they enter college and, since their learning will build from these preconceptions, a deeper understanding of these preconceptions should allow for more effective teaching and learning. Earlier commonsense computing projects probed novice computing students' pre-existing knowledge of sorting, debugging, concurrency, and algorithm analysis [14,4,13,7,6]. These studies found that students did possess knowledge that translated well to computer science; for example, 69% of students could describe a coherent algorithm to sort a list of numbers [14], and 97% of students could identify a significant problem associated with concurrency [6].…”
Section: Introductionmentioning
confidence: 98%
“…Many used iteration; to our surprise, most iteration involved posttest loops. In 2008, 13 we described our investigation of students' commonsense knowledge of debugging, giving beginners one of four questions designed to elicit their knowledge of debugging strategies. The questions asked them to describe the advice they would give people whose lights did not turn on when they flipped the switch; how they would locate the moment things go wrong in the children's game "telephone"; how they would find a Starbucks if they were in a strange city where they did not speak the language; or an experience of their own involving troubleshooting.…”
Section: Introductionmentioning
confidence: 99%