-
Notifications
You must be signed in to change notification settings - Fork 8
/
sectionwhattoexpect.html
247 lines (218 loc) · 15.3 KB
/
sectionwhattoexpect.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
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />
<title>What to Expect for Section</title>
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css"
integrity="sha384-Vkoo8x4CGsO3+Hhxv8T/Q5PaXtkKtu6ug5TOeNV6gBiFeWPGFN9MuhOf23Q9Ifjh" crossorigin="anonymous" />
<link rel="stylesheet" href="https://cdn.rawgit.com/afeld/bootstrap-toc/v1.0.1/dist/bootstrap-toc.min.css" />
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@9.18.1/build/styles/default.min.css">
<link rel="stylesheet" href="faqstyles.css" />
</head>
<body>
<div class="container">
<div class="row" style="height: 15px;"></div>
<div class="row">
<div class="col-sm-3">
<nav id="toc" class="sticky-top"></nav>
</div>
<div class="col-sm-9">
<h1>What to Expect for Section</h1>
<p> </p>
<hr />
<div align="right"><i>All times listed on this handout are in Pacific Time.</i></div>
<!-- Section Description -->
<h3><a name='Description'></a>What is Section?</h3>
<p>
You will be attending a weekly 40-minute discussion section in small groups with a member of our teaching team. For short, we just call this part of the class “section.”
</p>
<ul>
<li>Your section is when you’ll <b>get practice with the new concepts you learned in lecture.</b></li>
<li>In section, we’ll <b>answer questions, go over common errors or misconceptions, and discuss sample problems</b> in more detail than we can in lecture.</li>
</ul>
<p>
We have a large team of wonderful volunteer section leaders, whose jobs are to facilitate each of these sections. One of them will specifically be your section leader for the entire course. You and a group of about 10 other students will attend their section every week. We hope you will all get to know each other throughout the course.
</p>
<hr />
<h3><a name='Description'></a>When and Where is Section?</h3>
<p><b>When:</b> You can find your section time on the course home page. Get ready at least 10 minutes before:<br/>
<p><img src="img/yoursection.png" width="250px"/>
<p><b>I don't have a section: </b> Some people signed up late, or didn't get section time preferences in on time. That is fine. See the section on "<a href='#Swap'>permanently changing my section time</a>" below. That applies to you.
<p><b>Where: </b>The link for the section video conference will be posted by your section leader in the section "Ed".
<hr/>
<!-- Section Structure -->
<h3>Section Structure</h3>
<p>
Here’s how a standard section might work:
</p>
<ol>
<li>Your section leader gives a <b>recap of the important concepts</b> from that week’s lectures.</li>
<li>Your section leader <b>introduces the sample problems</b> you’ll be working on in section.</li>
<li>You and your fellow students <b>collaboratively come up with solutions to the problems</b>, one step at a time, with the guidance of your section leader.</li>
<li>You all help <b>turn these solutions into actual Python code</b>, which your section leader will type on their computer while showing you what’s on their screen.</li>
<li>During your entire section, you and your classmates should <b>ask any questions you have</b> so you can all understand everything better.</li>
</ol>
<p>
<b>Section works best when everybody participates and interacts with each other.</b> If you have an idea for how to solve part of a problem or have a question about anything, please share it during your section. Our goal with section is to make sure you understand everything as well as you can.
</p>
<hr />
<!-- Getting the most out of section -->
<h3>Getting the most out of section</h3>
<p>
<b>Staying up to date on the course material</b> will help you get the most out of your discussion sections. That way, you’ll all be able to spend more time working on sample problems. Section will cover material from the previous three lectures. Please refer to the <a href='https://compedu.stanford.edu/codeinplace/v1/#/course/schedule'>course schedule</a> to visualize this. Before attending your section each week, please do your best to:
</p>
<ul>
<li>Watch that week’s lectures (including that week’s Wednesday lecture)</li>
<li>Do the reading for that week</li>
<li>Be excited and prepared to participate in section :-)</li>
</ul>
<p>
And of course, please be respectful and considerate throughout this course, including (and especially) during your section. Code in Place is a diverse and wonderful community.
</p>
<p>
These are just our general guidelines. During your first section, your section leader will describe their own specific section norms and goals that they’d like to focus on with all of you.
</p>
<hr />
<!-- Section Communications -->
<h3><a name='Communications'></a>Section Communications</h3>
<p>
You will be added to <b>an Ed group specifically for your section</b>. This group will include you, your section leader, and about 10 of your classmates. You’ll all meet each other in your first section.
</p>
<ul>
<li>Your section leader will use your section’s Ed group to <b>post announcements related to section.</b></li>
<li>Feel free to post in this Ed group to <b>connect more with the other students in your section.</b></li>
<li>For posts not directly related to section, use the main Code in Place Ed group.</li>
</ul>
<p>
If you need to get in touch specifically with your section leader, make a private post (to staff only) in this group. Your section leader is a volunteer and as such might take a while to answer your question. Please be patient with them. Do not expect your section leader to debug your assignment code, for example.
</p>
<hr />
<!-- Attending Section -->
<h3><a name='Attending'></a>Attending Section</h3>
<p>
Most sections will be held as a group video call over Zoom. Download the <b>"Zoom Client for Meetings" version 4.6.10</b> here: <a href='https://zoom.us/download'>https://zoom.us/download</a>
</p>
<p>
See your section’s Ed page for the specifics about how to attend your section from your computer (e.g. a Zoom link to your section’s video call). <b>You should get an announcement from your section leader on Ed with these details.</b> If your section is not using Zoom, their announcement will include this information, too.
</p>
<hr />
<!-- Section Scheduling -->
<h3><a name='Scheduling'></a>Section Scheduling</h3>
<p>
You will attend the same section at the same time every week. Section time assignments will be released by 11:59pm Monday, April 13 PDT. All sections take place between the second and third lectures of each week (Wednesday-Friday).
</p>
<!-- Where do I find my section time? -->
<h4><u>Where do I find my section time?</u></h4>
<p>
We will post it on the website before 11:59 PDT.
</p>
<!-- When do sections start? -->
<h4><u>When do sections start?</u></h4>
<p>
<b>Sections start the first week of the course (this week!).</b> Your first section will be between Wednesday, April 15 and Friday April, 17, depending on your assigned section time.
</p>
<hr />
<!-- What to do if you can’t make it to section -->
<h3><a name='Absences'></a>What to do if you can’t make it to section</h3>
<!-- I can’t make it to my section for one week -->
<h4><u>I can’t make it to my section for one week</u></h4>
<p>
If for some reason you miss your section, everything is going to be alright: there is a recorded section. For more details see <a href='https://codeinplace2020.github.io/faqs/coursefaqs.html#section'>https://codeinplace2020.github.io/faqs/coursefaqs.html#section</a>
</p>
<!-- I need to permanently change my section time -->
<h4><a name='Swap'></a><u>I need to permanently change my section time</u></h4>
<p>
If you were assigned to a section time that doesn’t work for you, please let us know by filling out <a href='https://docs.google.com/forms/d/e/1FAIpQLScCWxU7zOxkqABUi8pcbsB9e-BBldZ24tAzKKI-xl12oH-6eQ/viewform'> this form</a>.
</p>
<p>
Changing section times is hard. We only process section changes one time in the week. We will process all section swaps submitted during the first week of the course around 11:59pm on Sunday April 19, PDT. We will accept section swap requests through the first two weeks of the course.
</p>
<p>
While waiting try attending your section (if you have one) and or watch the recorded section which will be released on Friday 10pm PDT!
</p>
<hr />
<!-- I haven't gotten a section time -->
<h3>I haven't gotten my section time</h3>
<p>
We have posted section times for everybody who is currently assigned to a section. Once we post it, you can find it on the course website and on Ed. For the course website:
</p>
<ul>
<li>Go to the course website and refresh the page.</li>
<li>Try a hard refresh (Control+F5 on Windows, Cmd+Shift+R on Mac).</li>
</ul>
<p>
For Ed:
</p>
<ul>
<li>Go to Ed and click on the home button on the top-right of the screen. Refresh the page.</li>
</ul>
<p>
You should then see your section time listed on the left side of the course website, and you should be a part of an Ed group called “Section ### - Code in Place”.
</p>
<p>
<b>If you still do not see a section time anywhere,</b> then you are not assigned to a section yet. Some people signed up late, or didn't get section time preferences in on time. That is fine. See the section on "<a href='#Swap'>permanently changing my section time</a>" above. That applies to you.
</p>
<hr />
<!-- Personal Privacy in Section -->
<h3>Personal Privacy and Safety in Section</h3>
<p>
We want to make sure that everybody in Code in Place is in an environment that they feel comfortable in. This includes during section. To protect your privacy, you are not required to disclose any personal information in section that you don't want to share. If you feel comfortable sharing more about yourself during section, we leave that choice up to you.
</p>
<p>
Finally, while we hope this will not be the case for anyone at any point during this course, if you encounter any misconduct during section or otherwise, please refer to the "process for reporting misconduct" outlined at the bottom of the <a href='https://compedu.stanford.edu/codeinplace/v1/#/handout/info.html'>general course information handout</a>. Creating and maintaining a safe and open community is of utmost importance to us.
</p>
<hr />
<!-- FAQs -->
<h3><a name='FAQ'></a>Additional Questions</h3>
<!-- My section leader didn’t show up to section -->
<h4><u>My section leader didn’t show up to section, what should I do?</u></h4>
<p>
This is going to be a very rare occurrence, but recall that we have already had a few section leaders get sick! If you can't find your section leader, please fill out this form: <a href='https://forms.gle/RBd7avY165cm9WQ7A'>https://forms.gle/RBd7avY165cm9WQ7A</a>
</p>
<p>
We’ll help you find a solution here. Or, you may watch the recorded section, if you prefer.
</p>
<h4><u>Other Questions</u></h4>
<p>
We will answer your questions as they come up. <br />
Please see: <a href='https://codeinplace2020.github.io/faqs/coursefaqs.html#section'>https://codeinplace2020.github.io/faqs/coursefaqs.html#section</a>
</p>
<br />
</div>
</div>
</div>
<script src="https://code.jquery.com/jquery-3.4.1.slim.min.js"
integrity="sha384-J6qa4849blE2+poT4WnyKhv5vZF5SrPo0iEjwBvKU7imGFAV0wwj1yYfoRSJoZ+n"
crossorigin="anonymous"></script>
<script src="https://cdn.jsdelivr.net/npm/popper.js@1.16.0/dist/umd/popper.min.js"
integrity="sha384-Q6E9RHvbIyZFJoft+2mJbHaEWldlvI9IOYy5n3zV9zzTtmI3UksdQRVvoxMfooAo"
crossorigin="anonymous"></script>
<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js"
integrity="sha384-wfSDF2E50Y2D1uUdj0O3uMBJnjuUD4Ih7YwaYd1iqfktj0Uod8GCExl3Og8ifwB6"
crossorigin="anonymous"></script>
<script src="https://cdn.rawgit.com/afeld/bootstrap-toc/v1.0.1/dist/bootstrap-toc.min.js"></script>
<script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@9.18.1/build/highlight.min.js"></script>
<script type="text/javascript">
$(function () {
var navSelector = "#toc";
var $myNav = $(navSelector);
Toc.init($myNav);
$("body").scrollspy({
target: navSelector
});
// Trim whitespace around code blocks.
$("pre>code").each(function (index, element) {
var $elem = $(element);
$elem.html($.trim($elem.html()));
});
$("pre").each(function (index, element) {
var $elem = $(element);
$elem.html($.trim($elem.html()));
});
});
hljs.initHighlightingOnLoad();
</script>
</body>
</html>