forked from jpabico/phase_0_unit_1
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathgps1.1.html
109 lines (97 loc) · 3.37 KB
/
gps1.1.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
<!--
Write your names here:
1. Brennon Williams
2. Ariel Fogel
Order of business: wireframe -> html -> css
content: Define terms. Why PP is important micro (this project) -> DBC -> macro level -> reflect
PSEUDO CODE / WIREFRAME
HEADER
<div> Container
<h1> Title (GPS 1.1)
<h2> Names
</div>
BODY
<div>
<h3>Terms
<p> Definition of terms
<h3>PP for this project
<p>Talk about experience and importance
<h3>PP for DBC
<p>Talk about benefits to DBC
<h3>PP in general
<p> Benefits in "real world"
<h3> Reflect
<p> What was the experience like
</div>
-->
<!DOCTYPE html>
<html lang="en">
<head>
<link rel="stylesheet" href="p0_gps1.1.css">
<title>GPS 1.1</title>
<style>
#introduction {
background-color: #bdc3c7;
text-align:center;
}
#introduction h1 {
color: #ea4a3c;
}
#introduction h2{
color: #333;
}
#content{
background-color: #bdc3c7;
}
#content h3{
color: #ea4a3c;
}
</style>
</head>
<body>
<div id="introduction">
<h1>GPS 1.1 - Introduction to Paired Programming</h1>
<h2>Brennon Williams and Ariel Fogel</h2>
</div>
<div id="content">
<h3>Terms of Pair Programming</h3>
<h4>Paired Programming</h4>
<p>Two programmers collaborating on the same project, with one "driving"
and the other "navigating".</p>
<h4>Driver</h4>
<p>The person who is writing the code.</p>
<h4>Navigator</h4>
<p>The person who directs the code-writing.
Basically, the navigator tells the driver what to write.</p>
<h3>Paired Programming for GPS 1.1</h3>
<p>Each student can fill in the knowledge gaps of the other.
A quick introduction to the process and dynamic of paired programming.</p>
<h3>Paired Programming for DBC</h3>
<p>Preparing for real world collaboration through multiple opportunities
to use the skills.
</p>
<h3>Real world Paired Programming</h3>
<p>Applying the skills we've developed to collaborate on live projects.
Increasing our abilities to function well within the context of team programming.
</p>
<h3>Reflection</h3>
<p>Brennon reflection: It was fun! It was a weird dynamic at first, but
over time I came to see how valuable it was and how useful it will be in a
professional setting. I enjoyed it and it took a little bit more time...
I think the driver-nagivator relationship works really well, and I'm pretty
proud of what we've done, so I don't think anything didn't work.
</p>
<p>
Ariel's reflection: It was a little bit challenging at the very beginning to
negotioate the roles and get a sense of how each person works. But I really
enjoyed pairing with Brennon, and I felt as though as time went on there was
definitely a very strong team dynamic that helped speed up the process where
it might have taken me way longer to make trivial decisions. I though that
dealing with the different roles did work. What didn't work was figuring out
what would work within the style tag and what wouldn't. But, overall I look
forward to many future opportunities to pair with others. Honestly, this was
way less painful than I anticipated it would be.
</p>
</div>
</body>
</html>