W. D. Gray and J. R. Anderson. Change episodes in coding: When and how do programmers change their code? In G. M. Olson, S. Sheppard, and E. Soloway, editors, Empirical Studies of Programmers: Second Workshop, pages 185--197. Ablex Publishing Corporation, Norwood, NJ, 1987. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Supporting the Restructuring of Data Abstractions through.. - Bowdidge (1995) (16 citations) (Correct)
....control [Bentley et al. 92] subway control [Heath Luff 92] and shipboard navigation [Hutchins 90] Observational techniques have also been used to understand how programmers work. Approaches range from using analysis of video and transcripts to answer a very specific research hypothesis [Gray Anderson 87, Ericsson Simon 93] to using verbal data for exploratory understanding of planning, behavior, and problem solving. The exploratory studies can be divided into observations in the workplace and 120 observations in an experimental setting. Walz, Elam, and Curtis s case study of a software ....
W. D. Gray and J. R. Anderson. Change episodes in coding: When and how do programmers change their code? In G. M. Olson, S. Sheppard, and E. Soloway, editors, Empirical Studies of Programmers: Second Workshop, pages 185--197. Ablex Publishing Corporation, Norwood, NJ, 1987.
Usability Analysis of Visual Programming Environments: a.. - Green (1996) (25 citations) (Correct)
....and then adds code to the construct, it may turn out subsequently that the construct is the wrong one (e.g. while should be changed 31 to for) Therefore, programmers may prefer to postpone commitment to a particular construct until the code has been further developed. Gray and Anderson [25] noted novices problems in the construction of Lisp conditionals. Lisp conditionals sometimes require the programmer to make an early commitment to a particular form, and they found that many instances of change episodes were cases where the programmer s first guess was wrong and had to be ....
Gray, W. and Anderson, J. R. (1987) Change-episodes in coding: when and how do programmers change their code? In G. M. Olson, S. Sheppard and E. Soloway (Eds), Empirical Studies of Programmers: Second Workshop. pp 185-197. Norwood, N.J.: Ablex.
Natural Programming: Project Overview and Proposal - Myers (1998) (1 citation) (Correct)
....simple primitives requires the user to synthesize higher level operations. This is one of the great difficulties in programming [Lewis 1987] When there are many different choices, more planning is required, and this increases the likelihood of backtracking and revision, which slows the programmer [Gray 1987]. Therefore, the language should provide highlevel operations. The object oriented style seems to be harder to learn for novice programmers, and a full inheritance hierarchy has been shown to be too complex for novices, but a fixed two level inheritance hierarchy is understandable [Pausch ....
W. Gray and J.R. Anderson. "Change-Episodes in Coding: When and How Do Programmers Change Their Code." Empirical Studies of Programmers: Second Workshop. G. M. Olson, S. Sheppard and E. Soloway. 1987: Norwood, NJ, Ablex. pp. 185-197.
How Software Engineering Tools Organize Programmer Behavior .. - Bowdidge, Griswold (1997) (3 citations) (Correct)
No context found.
W. D. Gray and J. R. Anderson. Change episodes in coding: When and how do programmers change their code? In G. M. Olson, S. Sheppard, and E. Soloway, editors, Empirical Studies of Programmers: Second Workshop, pages 185--197. Ablex, Norwood, NJ, 1987.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC