Entry Simon:2008:FYS from jeric.bib
Last update: Sun Oct 15 02:29:09 MDT 2017
Top |
Symbols |
Math |
A |
B |
C |
D |
E |
F |
G |
H |
I |
J |
K |
L |
M |
N |
O |
P |
Q |
R |
S |
T |
U |
V |
W |
Y |
Z
BibTeX entry
@Article{Simon:2008:FYS,
author = "Beth Simon and Brian Hanks",
title = "First-year students' impressions of pair programming
in {CS1}",
journal = j-JERIC,
volume = "7",
number = "4",
pages = "5:1--5:??",
month = jan,
year = "2008",
CODEN = "????",
DOI = "https://doi.org/10.1145/1316450.1316455",
ISSN = "1531-4278",
bibdate = "Fri Jun 20 10:12:59 MDT 2008",
bibsource = "http://www.acm.org/pubs/contents/journals/jeric/;
http://www.math.utah.edu/pub/tex/bib/jeric.bib",
abstract = "Pair programming, as part of the Agile Development
process, has noted benefits in professional software
development scenarios. These successes have led to a
rise in use of pair programming in educational
settings, particularly in Computer Science 1 (CS1).
Specifically, McDowell et al. [2006] has shown that
students using pair programming in CS1 do better in a
CS2 class (with solo programming) than students who
don't pair in CS1. This paper seeks to address a
similar question, but from a qualitative,
student-focused approach. How do students define,
experience, and value the pair programming experience?
How do they experience and value it compared to solo
programming? Does pairing in CS1 impact their
confidence in their abilities?\par
We report on semi-structured interviews with 11
subjects from two institutions where pair programming
was used in CS1, and solo programming was used in the
CS2. Many of the responses met our expectations;
students get stuck less and explore more ideas while
pairing, and believe that pair programming helped them
in CS1. Other responses were more surprising. Students
reported that when solo programming they were more
confident and understood their programs better. Many
students also said that they started work on their
assignments earlier when soloing. Students also
continue to use other students as resources even when
working 'solo.'",
acknowledgement = ack-nhfb,
articleno = "5",
keywords = "CS1; debugging; interview; novice; pair programming;
qualitative",
}
Related entries
- address,
7(1)2,
8(1)3,
8(4)10
- al.,
7(4)2
- approach,
4(3)1,
5(4)1,
5(4)2,
6(3)2,
6(3)6,
6(4)1,
7(1)1,
7(1)2,
7(3)1,
7(4)3,
8(1)2,
8(2)4,
8(3)9
- assignments,
5(3)z-1,
6(4)4
- believe,
7(1)2
- benefit,
8(1)1
- better,
6(2)1,
6(4)6,
8(3)7,
8(4)12
- class,
1(4)46,
5(4)1,
6(1)2,
6(2)2,
6(3)5,
7(1)2,
7(1)3,
7(4)3,
7(4)4,
7(4)6
- computer, 1-2es-z-z,
1(4)18,
1(4)31,
1(4)46,
1(4)60,
1(4)81,
2(1)1,
2(1)17,
2(1)131,
2(4)1,
3(2)1,
3(2)1,
3(3)1,
4(1)1,
4(1)1-1,
4(2)3,
4(2)4,
5(2)1,
5(4)1,
5(4)2,
5(4)3,
6(2)2,
6(3)1,
6(3)3,
6(3)4,
6(3)5,
6(3)6,
6(4)1,
6(4)2,
6(4)3,
6(4)4,
6(4)5,
6(4)6,
7(2)1,
7(2)2,
7(4)2,
7(4)4,
7(4)6,
8(1)2,
8(1)3,
8(2)5,
8(2)6,
8(3)7,
8(3)8,
8(4)11
- continue,
6(3)1,
6(3)2,
8(4)11
- CS1,
5(4)2,
7(4)2
- CS2,
5(4)2,
7(4)6
- development,
5(1)1,
6(1)1,
6(3)2,
6(4)4,
7(4)3,
8(1)2
- educational, 1-1es-z-z-7, 1-1es-z-z-8,
1(4)111,
5(4)1,
6(2)1,
6(4)2,
7(3)1
- et,
7(4)2
- even,
6(3)2,
7(4)6
- experience,
5(1)1,
5(3)z-3,
5(3)z-6,
6(1)2,
6(3)3,
6(3)5,
6(4)4,
7(1)3,
7(4)4,
8(1)2,
8(1)3,
8(4)11
- explore,
8(3)9,
8(4)12
- get,
7(4)6
- Hanks, Brian,
4(1)1,
7(4)2
- has,
5(4)1,
6(1)3,
6(3)2,
6(4)3,
6(4)5,
7(4)6,
8(1)3,
8(3)8,
8(4)12
- have,
5(4)1,
5(4)2,
6(1)3,
6(3)2,
6(3)5,
6(4)2,
6(4)3,
6(4)4,
7(1)2,
8(1)3,
8(2)6,
8(3)7,
8(4)11,
8(4)12
- how,
2(1)17,
3(3)1,
6(4)5,
7(4)1,
7(4)6,
8(1)2
- idea,
6(2)1,
6(3)2,
6(3)3,
8(2)6
- impact,
5(4)3
- institutions,
6(4)2
- interview,
5(4)3
- led,
7(4)2
- many,
5(4)1,
6(3)4,
6(3)6,
6(4)6,
7(4)3
- more,
6(1)1,
6(1)2,
6(4)1,
7(4)2,
8(1)1,
8(2)4,
8(3)9
- novice,
5(4)1,
6(1)1,
7(4)2
- other,
6(3)3,
6(3)4,
6(4)1,
6(4)6,
7(1)1,
7(1)2,
7(4)3,
7(4)4
- pair,
7(4)2
- pairing,
7(4)2
- paper,
6(4)5,
7(3)2,
7(4)1
- part,
5(4)2,
6(1)1,
6(1)2,
8(4)10
- process,
6(1)1,
6(1)2,
6(2)2,
6(3)3,
6(3)6,
7(2)1,
7(3)2,
8(2)5,
8(2)6,
8(3)9
- professional,
6(4)2,
6(4)3,
7(4)4,
7(4)6
- program,
2(1)17,
3(3)1,
4(2)3,
5(4)1,
6(1)1,
6(3)2,
7(4)3,
8(2)6
- programming,
2(2)1,
2(3)1,
3(1)1,
3(1)1,
3(4)1,
4(1)1,
4(3)1,
4(4)1,
5(1)1,
5(3)z,
5(3)z-1,
5(3)z-3,
5(4)1,
5(4)3,
6(1)1,
7(4)2,
7(4)3,
7(4)6
- qualitative,
8(4)11
- question,
6(3)3,
7(4)1,
8(4)10
- report,
5(4)2,
7(4)4,
7(4)6
- reported,
5(4)2
- resource, 1-1es-z-z-1, 1-1es-z-z-7, 1-1es-z-z-8,
1(4)18,
6(3)1,
6(3)5,
6(4)1,
7(4)1
- responses,
7(4)4
- scenarios,
6(3)3
- science, 1-2es-z-z,
1(4)31,
2(4)1,
3(3)1,
4(1)1,
4(1)1-1,
4(2)3,
4(2)4,
5(2)1,
5(4)1,
5(4)2,
6(3)3,
6(4)4,
7(2)1,
7(2)2,
7(3)2,
7(4)2,
7(4)6,
8(1)3,
8(2)5,
8(2)6,
8(4)11
- seek,
7(4)2
- setting,
8(2)5
- similar,
7(4)2
- software,
2(4)1,
2(4)1,
4(1)1,
5(2)1,
5(4)1,
6(1)1,
6(2)2,
6(4)6,
7(1)2,
7(4)4,
8(1)2,
8(2)6
- solo,
7(4)2
- specifically,
6(1)1
- started,
6(3)5
- student,
3(1)1,
3(1)1-1,
3(3)1,
4(1)1,
5(4)1,
5(4)2,
5(4)3,
6(1)2,
6(2)1,
6(3)1,
6(3)2,
6(3)3,
6(3)6,
6(4)1,
6(4)3,
6(4)4,
6(4)5,
7(1)2,
7(1)3,
7(2)1,
7(4)2,
7(4)3,
7(4)4,
7(4)6,
8(1)2,
8(1)3,
8(2)4,
8(2)5,
8(3)8,
8(3)9,
8(4)11,
8(4)12
- subjects,
7(4)2
- success,
6(3)2
- than,
6(1)2,
6(1)3,
7(4)6,
8(2)6
- two,
6(4)5,
7(1)3,
7(4)3,
7(4)4,
8(1)1,
8(3)7
- use,
2(1)17,
3(1)1-1,
5(4)1,
5(4)3,
6(1)2,
6(3)4,
6(3)6,
6(4)2,
6(4)5,
7(1)1,
7(1)2,
7(1)3,
7(3)2,
7(4)3,
7(4)6,
8(2)4,
8(2)5,
8(3)9,
8(4)11
- used,
2(1)17,
5(4)1,
6(2)1,
6(2)2,
6(3)2,
6(3)4,
6(3)5,
6(4)2,
6(4)3,
7(3)2,
7(4)1,
7(4)3,
7(4)4,
8(1)2,
8(3)8
- using, 1-1es-z-z-2, 1-1es-z-z-4,
1(4)111,
2(1)17,
4(2)4,
4(3)1,
4(3)1-1,
6(3)3,
6(4)5,
7(1)3,
7(4)4,
8(1)3,
8(2)4,
8(3)8,
8(4)11,
8(4)12
- value,
7(4)4
- was,
5(4)1,
6(1)2,
6(3)5,
7(1)3,
7(4)2,
7(4)3,
8(3)9
- were,
6(3)5,
7(4)1,
7(4)2,
7(4)3,
7(4)4,
8(2)6
- when,
6(1)1,
7(1)2
- where,
7(4)3
- while,
5(4)1,
6(1)3,
6(3)2,
6(3)6,
7(1)1,
7(1)2,
7(1)3
- who,
6(4)3,
7(1)1,
8(2)4
- work,
5(4)1,
6(3)5,
6(4)5,
7(1)2