jekyll-theme-csu-cs 0.1.1 → 0.1.5
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/LICENSE.txt +21 -21
- data/README.md +456 -451
- data/_includes/clone.html +11 -0
- data/_includes/disqus_comments.html +20 -20
- data/_includes/footer.html +71 -71
- data/_includes/google-analytics.html +11 -11
- data/_includes/grading/wholeGradesOnly.html +30 -30
- data/_includes/head.html +29 -29
- data/_includes/header.html +75 -75
- data/_includes/helpdesk.html +109 -109
- data/_includes/icon-github.html +1 -1
- data/_includes/icon-github.svg +1 -1
- data/_includes/icon-twitter.html +1 -1
- data/_includes/icon-twitter.svg +1 -1
- data/_includes/policies/cheating.html +66 -66
- data/_includes/policies/copyrighted.html +6 -6
- data/_includes/policies/daca.html +4 -4
- data/_includes/policies/diversityStatement.html +2 -2
- data/_includes/policies/honorPledge.html +11 -11
- data/_includes/policies/netiquette.html +2 -2
- data/_includes/policies/policiesAll.html +99 -99
- data/_includes/policies/religious.html +13 -13
- data/_includes/policies/thirdParty.html +4 -4
- data/_includes/policies/title9.html +17 -17
- data/_includes/policies/universalDesign.html +34 -34
- data/_includes/resources/canvasTech.html +17 -17
- data/_includes/resources/counseling.html +4 -4
- data/_includes/resources/eclipse.html +27 -27
- data/_includes/resources/intelliJ.html +9 -9
- data/_includes/resources/randomJavaLinks.html +9 -9
- data/_includes/resources/teams.html +7 -7
- data/_includes/resources/tilt.html +7 -7
- data/_includes/resources/university.html +11 -11
- data/_includes/social.html +15 -15
- data/_layouts/default.html +22 -22
- data/_layouts/home.html +12 -12
- data/_layouts/lab.html +2 -2
- data/_layouts/page.html +20 -20
- data/_layouts/post.html +32 -32
- data/_sass/csu-default.scss +46 -44
- data/_sass/parts/_base.scss +535 -520
- data/_sass/parts/_calendar.scss +137 -134
- data/_sass/parts/_cloneInclude.scss +16 -0
- data/_sass/parts/_contactcard.scss +78 -78
- data/_sass/parts/_labs.scss +46 -46
- data/_sass/parts/_syntax-highlighting.scss +81 -81
- data/assets/img/ducky.png +0 -0
- data/assets/img/signature-mobile.svg +1 -1
- data/assets/img/signature-oneline.svg +1 -1
- data/assets/img/signature-stacked.svg +1 -1
- data/assets/main.scss +7 -7
- data/assets/minima-social-icons.svg +38 -38
- metadata +29 -28
data/_includes/helpdesk.html
CHANGED
@@ -1,110 +1,110 @@
|
|
1
|
-
<p>The TAs will be posting hours in which they will be available on the <a href="https://www.acns.colostate.edu/microsoft-teams-students/">Microsoft Team</a>
|
2
|
-
for the class.</p>
|
3
|
-
|
4
|
-
<p>In general, we ask that you contact us (both TAs, and the instructor) on Microsoft Teams
|
5
|
-
(don’t use email / canvas - unless it is a long message), this can be via direct message or general channel for open
|
6
|
-
questions.</p>
|
7
|
-
|
8
|
-
<p>We also will be running a virtual help desk over Microsoft Teams. As the MS Teams is not designed
|
9
|
-
to be a help desk queue, we have developed the following procedure for asking for help.</p>
|
10
|
-
|
11
|
-
<ol>
|
12
|
-
<li>In general chat, you should ask general questions (do NOT post your code)
|
13
|
-
<ul>
|
14
|
-
<li>You should do this <em>first</em>, as talking through a problem often helps you solve it!</li>
|
15
|
-
<li>Good questions to ask are “I am looking at problem X, and I think the algorithm is as follows…
|
16
|
-
(English line by line). What are your thoughts?”</li>
|
17
|
-
<li>A bad question is “I am stuck on problem X.”, as it leaves people to guess what is going on instead of helping directly.</li>
|
18
|
-
<li>This allows anyone in the class to help answer your question, not just TAs, building both the community
|
19
|
-
and larger response time.</li>
|
20
|
-
<li>While we say don’t post <em>your</em> code, posting algorithms is fine, or provided code from lecture / labs. It is also
|
21
|
-
fine to post links to help sites, as long as this is not abused.</li>
|
22
|
-
</ul>
|
23
|
-
</li>
|
24
|
-
<li>Coding questions
|
25
|
-
<ol>
|
26
|
-
<li>Post in general chat (during TA hours): “I have a coding question on (lab x:step y, practical x, etc)”</li>
|
27
|
-
<li>TAs will be going through them in order, putting a :thumbs up: emote on questions they are helping with</li>
|
28
|
-
<li>They will then direct message you, asking for your question
|
29
|
-
<ul>
|
30
|
-
<li>note: response times can vary, but if you are not around when they respond, they will have to move on.</li>
|
31
|
-
</ul>
|
32
|
-
</li>
|
33
|
-
<li>You will then respond with your question + code.
|
34
|
-
<ul>
|
35
|
-
<li>For a better response, don’t just send code. Instead, send a <strong>question with what you have tried</strong>, along with
|
36
|
-
the code. Try explaining your code in your message.</li>
|
37
|
-
<li>Remember your <a href="https://support.microsoft.com/en-ie/office/use-markdown-formatting-in-teams-4d10bd65-55e2-4b2d-a1f3-2bebdcd2c772">formatting options</a>,
|
38
|
-
especially the format code option </> <br />
|
39
|
-
<img src="{{ "/assets/img/msteamsformat.png" | relative_url }}" alt="MS Teams Format Banner" /></li>
|
40
|
-
<li>Also, if you just paste the code into Teams from your IDE, it automatically formats the code - so pretty easy to make code look nice.</li>
|
41
|
-
<li>This means there is no reason to send screenshots of your code! Please don’t, they are hard to work with.</li>
|
42
|
-
<li>Depending on your question, your TA may ask you to go into Teams videochat, and screen share with them. Please
|
43
|
-
make sure this is <a href="https://support.office.com/en-us/article/show-your-screen-during-a-meeting-90c84e5a-b6fe-4ed4-9687-5923d230d3a7">setup correctly</a>.</li>
|
44
|
-
</ul>
|
45
|
-
</li>
|
46
|
-
<li>After your question is answered, your TA will put a smiley face next to the “I have a coding question…” message
|
47
|
-
in general chat. Please note, the answer to your question could be to try a few things, and then come back. They
|
48
|
-
may still put a smiley face for tracking purposes, and if they direct you to message them directly
|
49
|
-
after that, it is fine.</li>
|
50
|
-
<li>After your question is answered, we ask that you wait a bit before posting “I have a coding question” again, and if you
|
51
|
-
immediately continue to do that - they may move you to the bottom of the ‘queue’ in order to help other students.</li>
|
52
|
-
</ol>
|
53
|
-
</li>
|
54
|
-
<li>During non-standard lab times, feel free to send a direct message. TAs will answer during their office hours. TAs
|
55
|
-
are tagged with the TA tag.</li>
|
56
|
-
</ol>
|
57
|
-
|
58
|
-
<p>As a last reminder, the more you can have a general question, as compared to a coding question - the more
|
59
|
-
you will learn! We encourage general questions to all students to see and discuss.</p>
|
60
|
-
|
61
|
-
<h2 id="live-sessions">Live Sessions</h2>
|
62
|
-
<p>The TAs and Instructor will be having live sessions each week. The live session time will be scheduled in Microsoft Teams.
|
63
|
-
All live sessions are <strong>optional</strong>.</p>
|
64
|
-
|
65
|
-
<p>Our plan is to record the stream, so you can look at it later if you are unable to make the session. This doesn’t
|
66
|
-
always work as we expect, but for the most part, it works fine.</p>
|
67
|
-
|
68
|
-
<p>Make sure you check Teams for the scheduled times each week.</p>
|
69
|
-
|
70
|
-
<h2 id="additional-debugging-advice">Additional Debugging Advice</h2>
|
71
|
-
<p>When coding, there is a lot of debugging. We suggest the following to help / try before asking coding questions. Please
|
72
|
-
note that if you have general / insight question, these don’t apply. However, trying these debugging techniques before
|
73
|
-
asking coding questions will help you become a better programmer.</p>
|
74
|
-
|
75
|
-
<ul>
|
76
|
-
<li>Design before you code
|
77
|
-
<ul>
|
78
|
-
<li>the best developers build a plan before coding. They figure out what they want to do, either by writing it
|
79
|
-
in comments or using paper. It makes a major difference.</li>
|
80
|
-
</ul>
|
81
|
-
</li>
|
82
|
-
<li>Talk through your code / algorithm (see ducky below)</li>
|
83
|
-
<li>Write code in small segments (one or two lines at a time)
|
84
|
-
<ul>
|
85
|
-
<li>make sure it compiles</li>
|
86
|
-
<li>toss in a System.out.println() to make sure it is doing what you think</li>
|
87
|
-
<li>this may mean adding extra variables</li>
|
88
|
-
</ul>
|
89
|
-
</li>
|
90
|
-
<li>Have a bug, use printlns liberally to figure out what is going on
|
91
|
-
<ul>
|
92
|
-
<li>this may mean commenting out sections of your code, and slowly stepping through it</li>
|
93
|
-
<li>we suggest using “TESTING” or “DEBUG” in whatever you print. That way, you don’t accidentally leave a print in there
|
94
|
-
when you submit for grading.</li>
|
95
|
-
</ul>
|
96
|
-
</li>
|
97
|
-
</ul>
|
98
|
-
|
99
|
-
<h3 id="before-asking-questions-talk-to-the-ducky">Before asking questions, talk to the ducky!</h3>
|
100
|
-
|
101
|
-
<p><img src="{{"/assets/img/ducky.png" | relative_url }}" style="float:right;width:125px;padding-right:10px;padding-left:10px;padding-bottom:50px;" /></p>
|
102
|
-
|
103
|
-
<p>Often the best thing you can do is explain what you are attempting to do to a friend. In the process of explaining it,
|
104
|
-
you usually figure out your errors, and it helps give you a direction to go from there.</p>
|
105
|
-
|
106
|
-
<p>Sometimes in companies, this can be a time-cost for other developers so thus the introduction of a
|
107
|
-
<a href="https://en.wikipedia.org/wiki/Rubber_duck_debugging">Rubber Duck</a> for
|
108
|
-
testing. This gives you an object for you to talk to just like you would a friend. The object doesn’t have to give feedback
|
109
|
-
(just like a friend doesn’t), but instead, the process of talking through the code out loud will often provide
|
1
|
+
<p>The TAs will be posting hours in which they will be available on the <a href="https://www.acns.colostate.edu/microsoft-teams-students/">Microsoft Team</a>
|
2
|
+
for the class.</p>
|
3
|
+
|
4
|
+
<p>In general, we ask that you contact us (both TAs, and the instructor) on Microsoft Teams
|
5
|
+
(don’t use email / canvas - unless it is a long message), this can be via direct message or general channel for open
|
6
|
+
questions.</p>
|
7
|
+
|
8
|
+
<p>We also will be running a virtual help desk over Microsoft Teams. As the MS Teams is not designed
|
9
|
+
to be a help desk queue, we have developed the following procedure for asking for help.</p>
|
10
|
+
|
11
|
+
<ol>
|
12
|
+
<li>In general chat, you should ask general questions (do NOT post your code)
|
13
|
+
<ul>
|
14
|
+
<li>You should do this <em>first</em>, as talking through a problem often helps you solve it!</li>
|
15
|
+
<li>Good questions to ask are “I am looking at problem X, and I think the algorithm is as follows…
|
16
|
+
(English line by line). What are your thoughts?”</li>
|
17
|
+
<li>A bad question is “I am stuck on problem X.”, as it leaves people to guess what is going on instead of helping directly.</li>
|
18
|
+
<li>This allows anyone in the class to help answer your question, not just TAs, building both the community
|
19
|
+
and larger response time.</li>
|
20
|
+
<li>While we say don’t post <em>your</em> code, posting algorithms is fine, or provided code from lecture / labs. It is also
|
21
|
+
fine to post links to help sites, as long as this is not abused.</li>
|
22
|
+
</ul>
|
23
|
+
</li>
|
24
|
+
<li>Coding questions
|
25
|
+
<ol>
|
26
|
+
<li>Post in general chat (during TA hours): “I have a coding question on (lab x:step y, practical x, etc)”</li>
|
27
|
+
<li>TAs will be going through them in order, putting a :thumbs up: emote on questions they are helping with</li>
|
28
|
+
<li>They will then direct message you, asking for your question
|
29
|
+
<ul>
|
30
|
+
<li>note: response times can vary, but if you are not around when they respond, they will have to move on.</li>
|
31
|
+
</ul>
|
32
|
+
</li>
|
33
|
+
<li>You will then respond with your question + code.
|
34
|
+
<ul>
|
35
|
+
<li>For a better response, don’t just send code. Instead, send a <strong>question with what you have tried</strong>, along with
|
36
|
+
the code. Try explaining your code in your message.</li>
|
37
|
+
<li>Remember your <a href="https://support.microsoft.com/en-ie/office/use-markdown-formatting-in-teams-4d10bd65-55e2-4b2d-a1f3-2bebdcd2c772">formatting options</a>,
|
38
|
+
especially the format code option </> <br />
|
39
|
+
<img src="{{ "/assets/img/msteamsformat.png" | relative_url }}" alt="MS Teams Format Banner" /></li>
|
40
|
+
<li>Also, if you just paste the code into Teams from your IDE, it automatically formats the code - so pretty easy to make code look nice.</li>
|
41
|
+
<li>This means there is no reason to send screenshots of your code! Please don’t, they are hard to work with.</li>
|
42
|
+
<li>Depending on your question, your TA may ask you to go into Teams videochat, and screen share with them. Please
|
43
|
+
make sure this is <a href="https://support.office.com/en-us/article/show-your-screen-during-a-meeting-90c84e5a-b6fe-4ed4-9687-5923d230d3a7">setup correctly</a>.</li>
|
44
|
+
</ul>
|
45
|
+
</li>
|
46
|
+
<li>After your question is answered, your TA will put a smiley face next to the “I have a coding question…” message
|
47
|
+
in general chat. Please note, the answer to your question could be to try a few things, and then come back. They
|
48
|
+
may still put a smiley face for tracking purposes, and if they direct you to message them directly
|
49
|
+
after that, it is fine.</li>
|
50
|
+
<li>After your question is answered, we ask that you wait a bit before posting “I have a coding question” again, and if you
|
51
|
+
immediately continue to do that - they may move you to the bottom of the ‘queue’ in order to help other students.</li>
|
52
|
+
</ol>
|
53
|
+
</li>
|
54
|
+
<li>During non-standard lab times, feel free to send a direct message. TAs will answer during their office hours. TAs
|
55
|
+
are tagged with the TA tag.</li>
|
56
|
+
</ol>
|
57
|
+
|
58
|
+
<p>As a last reminder, the more you can have a general question, as compared to a coding question - the more
|
59
|
+
you will learn! We encourage general questions to all students to see and discuss.</p>
|
60
|
+
|
61
|
+
<h2 id="live-sessions">Live Sessions</h2>
|
62
|
+
<p>The TAs and Instructor will be having live sessions each week. The live session time will be scheduled in Microsoft Teams.
|
63
|
+
All live sessions are <strong>optional</strong>.</p>
|
64
|
+
|
65
|
+
<p>Our plan is to record the stream, so you can look at it later if you are unable to make the session. This doesn’t
|
66
|
+
always work as we expect, but for the most part, it works fine.</p>
|
67
|
+
|
68
|
+
<p>Make sure you check Teams for the scheduled times each week.</p>
|
69
|
+
|
70
|
+
<h2 id="additional-debugging-advice">Additional Debugging Advice</h2>
|
71
|
+
<p>When coding, there is a lot of debugging. We suggest the following to help / try before asking coding questions. Please
|
72
|
+
note that if you have general / insight question, these don’t apply. However, trying these debugging techniques before
|
73
|
+
asking coding questions will help you become a better programmer.</p>
|
74
|
+
|
75
|
+
<ul>
|
76
|
+
<li>Design before you code
|
77
|
+
<ul>
|
78
|
+
<li>the best developers build a plan before coding. They figure out what they want to do, either by writing it
|
79
|
+
in comments or using paper. It makes a major difference.</li>
|
80
|
+
</ul>
|
81
|
+
</li>
|
82
|
+
<li>Talk through your code / algorithm (see ducky below)</li>
|
83
|
+
<li>Write code in small segments (one or two lines at a time)
|
84
|
+
<ul>
|
85
|
+
<li>make sure it compiles</li>
|
86
|
+
<li>toss in a System.out.println() to make sure it is doing what you think</li>
|
87
|
+
<li>this may mean adding extra variables</li>
|
88
|
+
</ul>
|
89
|
+
</li>
|
90
|
+
<li>Have a bug, use printlns liberally to figure out what is going on
|
91
|
+
<ul>
|
92
|
+
<li>this may mean commenting out sections of your code, and slowly stepping through it</li>
|
93
|
+
<li>we suggest using “TESTING” or “DEBUG” in whatever you print. That way, you don’t accidentally leave a print in there
|
94
|
+
when you submit for grading.</li>
|
95
|
+
</ul>
|
96
|
+
</li>
|
97
|
+
</ul>
|
98
|
+
|
99
|
+
<h3 id="before-asking-questions-talk-to-the-ducky">Before asking questions, talk to the ducky!</h3>
|
100
|
+
|
101
|
+
<p><img src="{{"/assets/img/ducky.png" | relative_url }}" style="float:right;width:125px;padding-right:10px;padding-left:10px;padding-bottom:50px;" /></p>
|
102
|
+
|
103
|
+
<p>Often the best thing you can do is explain what you are attempting to do to a friend. In the process of explaining it,
|
104
|
+
you usually figure out your errors, and it helps give you a direction to go from there.</p>
|
105
|
+
|
106
|
+
<p>Sometimes in companies, this can be a time-cost for other developers so thus the introduction of a
|
107
|
+
<a href="https://en.wikipedia.org/wiki/Rubber_duck_debugging">Rubber Duck</a> for
|
108
|
+
testing. This gives you an object for you to talk to just like you would a friend. The object doesn’t have to give feedback
|
109
|
+
(just like a friend doesn’t), but instead, the process of talking through the code out loud will often provide
|
110
110
|
insights into both development and errors.</p>
|
data/_includes/icon-github.html
CHANGED
@@ -1 +1 @@
|
|
1
|
-
<a href="https://github.com/{{ include.username }}"><span class="icon icon--github">{% include icon-github.svg %}</span><span class="username">{{ include.username }}</span></a>
|
1
|
+
<a href="https://github.com/{{ include.username }}"><span class="icon icon--github">{% include icon-github.svg %}</span><span class="username">{{ include.username }}</span></a>
|
data/_includes/icon-github.svg
CHANGED
@@ -1 +1 @@
|
|
1
|
-
<svg viewBox="0 0 16 16" width="16px" height="16px"><path fill="#828282" d="M7.999,0.431c-4.285,0-7.76,3.474-7.76,7.761 c0,3.428,2.223,6.337,5.307,7.363c0.388,0.071,0.53-0.168,0.53-0.374c0-0.184-0.007-0.672-0.01-1.32 c-2.159,0.469-2.614-1.04-2.614-1.04c-0.353-0.896-0.862-1.135-0.862-1.135c-0.705-0.481,0.053-0.472,0.053-0.472 c0.779,0.055,1.189,0.8,1.189,0.8c0.692,1.186,1.816,0.843,2.258,0.645c0.071-0.502,0.271-0.843,0.493-1.037 C4.86,11.425,3.049,10.76,3.049,7.786c0-0.847,0.302-1.54,0.799-2.082C3.768,5.507,3.501,4.718,3.924,3.65 c0,0,0.652-0.209,2.134,0.796C6.677,4.273,7.34,4.187,8,4.184c0.659,0.003,1.323,0.089,1.943,0.261 c1.482-1.004,2.132-0.796,2.132-0.796c0.423,1.068,0.157,1.857,0.077,2.054c0.497,0.542,0.798,1.235,0.798,2.082 c0,2.981-1.814,3.637-3.543,3.829c0.279,0.24,0.527,0.713,0.527,1.437c0,1.037-0.01,1.874-0.01,2.129 c0,0.208,0.14,0.449,0.534,0.373c3.081-1.028,5.302-3.935,5.302-7.362C15.76,3.906,12.285,0.431,7.999,0.431z"/></svg>
|
1
|
+
<svg viewBox="0 0 16 16" width="16px" height="16px"><path fill="#828282" d="M7.999,0.431c-4.285,0-7.76,3.474-7.76,7.761 c0,3.428,2.223,6.337,5.307,7.363c0.388,0.071,0.53-0.168,0.53-0.374c0-0.184-0.007-0.672-0.01-1.32 c-2.159,0.469-2.614-1.04-2.614-1.04c-0.353-0.896-0.862-1.135-0.862-1.135c-0.705-0.481,0.053-0.472,0.053-0.472 c0.779,0.055,1.189,0.8,1.189,0.8c0.692,1.186,1.816,0.843,2.258,0.645c0.071-0.502,0.271-0.843,0.493-1.037 C4.86,11.425,3.049,10.76,3.049,7.786c0-0.847,0.302-1.54,0.799-2.082C3.768,5.507,3.501,4.718,3.924,3.65 c0,0,0.652-0.209,2.134,0.796C6.677,4.273,7.34,4.187,8,4.184c0.659,0.003,1.323,0.089,1.943,0.261 c1.482-1.004,2.132-0.796,2.132-0.796c0.423,1.068,0.157,1.857,0.077,2.054c0.497,0.542,0.798,1.235,0.798,2.082 c0,2.981-1.814,3.637-3.543,3.829c0.279,0.24,0.527,0.713,0.527,1.437c0,1.037-0.01,1.874-0.01,2.129 c0,0.208,0.14,0.449,0.534,0.373c3.081-1.028,5.302-3.935,5.302-7.362C15.76,3.906,12.285,0.431,7.999,0.431z"/></svg>
|
data/_includes/icon-twitter.html
CHANGED
@@ -1 +1 @@
|
|
1
|
-
<a href="https://twitter.com/{{ include.username }}"><span class="icon icon--twitter">{% include icon-twitter.svg %}</span><span class="username">{{ include.username }}</span></a>
|
1
|
+
<a href="https://twitter.com/{{ include.username }}"><span class="icon icon--twitter">{% include icon-twitter.svg %}</span><span class="username">{{ include.username }}</span></a>
|
data/_includes/icon-twitter.svg
CHANGED
@@ -1 +1 @@
|
|
1
|
-
<svg viewBox="0 0 16 16" width="16px" height="16px"><path fill="#828282" d="M15.969,3.058c-0.586,0.26-1.217,0.436-1.878,0.515c0.675-0.405,1.194-1.045,1.438-1.809c-0.632,0.375-1.332,0.647-2.076,0.793c-0.596-0.636-1.446-1.033-2.387-1.033c-1.806,0-3.27,1.464-3.27,3.27 c0,0.256,0.029,0.506,0.085,0.745C5.163,5.404,2.753,4.102,1.14,2.124C0.859,2.607,0.698,3.168,0.698,3.767 c0,1.134,0.577,2.135,1.455,2.722C1.616,6.472,1.112,6.325,0.671,6.08c0,0.014,0,0.027,0,0.041c0,1.584,1.127,2.906,2.623,3.206 C3.02,9.402,2.731,9.442,2.433,9.442c-0.211,0-0.416-0.021-0.615-0.059c0.416,1.299,1.624,2.245,3.055,2.271 c-1.119,0.877-2.529,1.4-4.061,1.4c-0.264,0-0.524-0.015-0.78-0.046c1.447,0.928,3.166,1.469,5.013,1.469 c6.015,0,9.304-4.983,9.304-9.304c0-0.142-0.003-0.283-0.009-0.423C14.976,4.29,15.531,3.714,15.969,3.058z"/></svg>
|
1
|
+
<svg viewBox="0 0 16 16" width="16px" height="16px"><path fill="#828282" d="M15.969,3.058c-0.586,0.26-1.217,0.436-1.878,0.515c0.675-0.405,1.194-1.045,1.438-1.809c-0.632,0.375-1.332,0.647-2.076,0.793c-0.596-0.636-1.446-1.033-2.387-1.033c-1.806,0-3.27,1.464-3.27,3.27 c0,0.256,0.029,0.506,0.085,0.745C5.163,5.404,2.753,4.102,1.14,2.124C0.859,2.607,0.698,3.168,0.698,3.767 c0,1.134,0.577,2.135,1.455,2.722C1.616,6.472,1.112,6.325,0.671,6.08c0,0.014,0,0.027,0,0.041c0,1.584,1.127,2.906,2.623,3.206 C3.02,9.402,2.731,9.442,2.433,9.442c-0.211,0-0.416-0.021-0.615-0.059c0.416,1.299,1.624,2.245,3.055,2.271 c-1.119,0.877-2.529,1.4-4.061,1.4c-0.264,0-0.524-0.015-0.78-0.046c1.447,0.928,3.166,1.469,5.013,1.469 c6.015,0,9.304-4.983,9.304-9.304c0-0.142-0.003-0.283-0.009-0.423C14.976,4.29,15.531,3.714,15.969,3.058z"/></svg>
|
@@ -1,66 +1,66 @@
|
|
1
|
-
<p><em>We are accountable for our actions and will act ethically and honestly in all
|
2
|
-
our interactions.</em></p>
|
3
|
-
|
4
|
-
<p>Within the classroom, that means you do your own work! This is especially
|
5
|
-
true when it comes to programming, as it is easy to copy another’s code. Copying
|
6
|
-
code <em>is cheating</em> and lacks integrity. Such violations of cheating
|
7
|
-
or plagiarism will result in zero to a full negative grade on the assignment
|
8
|
-
and reporting to the appropriate university resources. Further
|
9
|
-
infractions will result in an F given in the course.</p>
|
10
|
-
|
11
|
-
<p>CMU provides some nice examples to follow:</p>
|
12
|
-
|
13
|
-
<p>For personal assistance, here are some of the things that are appropriate:</p>
|
14
|
-
<ul>
|
15
|
-
<li>Clarifying ambiguities or vague points in class handouts, textbooks, or lectures</li>
|
16
|
-
<li>Discussing or explaining the general class material</li>
|
17
|
-
<li>Providing assistance with Java, in using the system facilities, or with editing and debugging tools</li>
|
18
|
-
<li>Discussing the code that we give out on the assignment</li>
|
19
|
-
<li>Discussing the assignments to better understand them</li>
|
20
|
-
<li>Getting help from anyone concerning programming issues which are clearly more general than the specific project (e.g., what does a particular error message mean?)</li>
|
21
|
-
<li>Suggesting solution strategies</li>
|
22
|
-
<li>In general, oral collaboration is OK.</li>
|
23
|
-
</ul>
|
24
|
-
|
25
|
-
<p>Here are some things that are inappropriate:</p>
|
26
|
-
|
27
|
-
<ul>
|
28
|
-
<li>Copying files or parts of files (such as source code, written text, or unit tests) from another person or source</li>
|
29
|
-
<li>Copying (or retyping) files or parts of files with minor modifications such as style changes or minor logic modifications</li>
|
30
|
-
<li>Allowing someone else to copy your code or written assignment, either in draft or final form</li>
|
31
|
-
<li>Getting help that you do not fully understand, and from someone whom you do not acknowledge on your solution</li>
|
32
|
-
<li>Writing, using, or submitting a program that attempts to alter or erase grading information or otherwise compromise security</li>
|
33
|
-
<li>Copying someone else’s files containing draft solutions, even if the file permissions are incorrectly set to allow it</li>
|
34
|
-
<li>Lying to course staff</li>
|
35
|
-
<li>Reading the current solution (handed out) if you will be handing in the current assignment late</li>
|
36
|
-
<li>Copying prose or programs directly</li>
|
37
|
-
<li>Giving copies of work to others</li>
|
38
|
-
<li>Coaching others step-by-step</li>
|
39
|
-
</ul>
|
40
|
-
|
41
|
-
<p>If you do any of these, your should also acknowledge it in what you turn in; but expect to have a
|
42
|
-
conversation with an instructor about it and, at least, suffer some penalty
|
43
|
-
in the grade. If we discover you have done this and not acknowledged it,
|
44
|
-
the penalty will be much more severe. In other words, dishonesty is much
|
45
|
-
worse than stupidity.</p>
|
46
|
-
|
47
|
-
<p>Here are some gray areas:</p>
|
48
|
-
|
49
|
-
<ul>
|
50
|
-
<li>Reading someone’s code for clarity or bugs, after you have completed your own</li>
|
51
|
-
<li>Helping with debugging</li>
|
52
|
-
<li>Looking at someone’s prose or program but thinking about them and writing your own</li>
|
53
|
-
<li>Following someone’s advice or instructions without understanding them</li>
|
54
|
-
<li>Many others</li>
|
55
|
-
</ul>
|
56
|
-
|
57
|
-
<p>These, too, should be acknowledged.</p>
|
58
|
-
|
59
|
-
<p>A few resources</p>
|
60
|
-
<ul>
|
61
|
-
<li><a href="https://legacy.scu.edu/ethics/publications/iie/v13n1/challenge.html">Cheating versus Collaboration</a></li>
|
62
|
-
<li><a href="https://www.cs.cmu.edu/~211/policy/cheating.html">CMU Policy</a></li>
|
63
|
-
<li><a href="https://resolutioncenter.colostate.edu/student-conduct-code/">CSU Resolution Center - Conduct Code</a></li>
|
64
|
-
</ul>
|
65
|
-
|
66
|
-
|
1
|
+
<p><em>We are accountable for our actions and will act ethically and honestly in all
|
2
|
+
our interactions.</em></p>
|
3
|
+
|
4
|
+
<p>Within the classroom, that means you do your own work! This is especially
|
5
|
+
true when it comes to programming, as it is easy to copy another’s code. Copying
|
6
|
+
code <em>is cheating</em> and lacks integrity. Such violations of cheating
|
7
|
+
or plagiarism will result in zero to a full negative grade on the assignment
|
8
|
+
and reporting to the appropriate university resources. Further
|
9
|
+
infractions will result in an F given in the course.</p>
|
10
|
+
|
11
|
+
<p>CMU provides some nice examples to follow:</p>
|
12
|
+
|
13
|
+
<p>For personal assistance, here are some of the things that are appropriate:</p>
|
14
|
+
<ul>
|
15
|
+
<li>Clarifying ambiguities or vague points in class handouts, textbooks, or lectures</li>
|
16
|
+
<li>Discussing or explaining the general class material</li>
|
17
|
+
<li>Providing assistance with Java, in using the system facilities, or with editing and debugging tools</li>
|
18
|
+
<li>Discussing the code that we give out on the assignment</li>
|
19
|
+
<li>Discussing the assignments to better understand them</li>
|
20
|
+
<li>Getting help from anyone concerning programming issues which are clearly more general than the specific project (e.g., what does a particular error message mean?)</li>
|
21
|
+
<li>Suggesting solution strategies</li>
|
22
|
+
<li>In general, oral collaboration is OK.</li>
|
23
|
+
</ul>
|
24
|
+
|
25
|
+
<p>Here are some things that are inappropriate:</p>
|
26
|
+
|
27
|
+
<ul>
|
28
|
+
<li>Copying files or parts of files (such as source code, written text, or unit tests) from another person or source</li>
|
29
|
+
<li>Copying (or retyping) files or parts of files with minor modifications such as style changes or minor logic modifications</li>
|
30
|
+
<li>Allowing someone else to copy your code or written assignment, either in draft or final form</li>
|
31
|
+
<li>Getting help that you do not fully understand, and from someone whom you do not acknowledge on your solution</li>
|
32
|
+
<li>Writing, using, or submitting a program that attempts to alter or erase grading information or otherwise compromise security</li>
|
33
|
+
<li>Copying someone else’s files containing draft solutions, even if the file permissions are incorrectly set to allow it</li>
|
34
|
+
<li>Lying to course staff</li>
|
35
|
+
<li>Reading the current solution (handed out) if you will be handing in the current assignment late</li>
|
36
|
+
<li>Copying prose or programs directly</li>
|
37
|
+
<li>Giving copies of work to others</li>
|
38
|
+
<li>Coaching others step-by-step</li>
|
39
|
+
</ul>
|
40
|
+
|
41
|
+
<p>If you do any of these, your should also acknowledge it in what you turn in; but expect to have a
|
42
|
+
conversation with an instructor about it and, at least, suffer some penalty
|
43
|
+
in the grade. If we discover you have done this and not acknowledged it,
|
44
|
+
the penalty will be much more severe. In other words, dishonesty is much
|
45
|
+
worse than stupidity.</p>
|
46
|
+
|
47
|
+
<p>Here are some gray areas:</p>
|
48
|
+
|
49
|
+
<ul>
|
50
|
+
<li>Reading someone’s code for clarity or bugs, after you have completed your own</li>
|
51
|
+
<li>Helping with debugging</li>
|
52
|
+
<li>Looking at someone’s prose or program but thinking about them and writing your own</li>
|
53
|
+
<li>Following someone’s advice or instructions without understanding them</li>
|
54
|
+
<li>Many others</li>
|
55
|
+
</ul>
|
56
|
+
|
57
|
+
<p>These, too, should be acknowledged.</p>
|
58
|
+
|
59
|
+
<p>A few resources</p>
|
60
|
+
<ul>
|
61
|
+
<li><a href="https://legacy.scu.edu/ethics/publications/iie/v13n1/challenge.html">Cheating versus Collaboration</a></li>
|
62
|
+
<li><a href="https://www.cs.cmu.edu/~211/policy/cheating.html">CMU Policy</a></li>
|
63
|
+
<li><a href="https://resolutioncenter.colostate.edu/student-conduct-code/">CSU Resolution Center - Conduct Code</a></li>
|
64
|
+
</ul>
|
65
|
+
|
66
|
+
|
@@ -1,7 +1,7 @@
|
|
1
|
-
<p>Please do not share material from this course in online, print, or other media. Course material is
|
2
|
-
the property of the instructor who developed the course. Materials authored by third parties and
|
3
|
-
used in the course are also subject to copyright protections. Posting course materials on external
|
4
|
-
sites (commercial or not) violates both copyright law and the CSU Student Conduct Code.
|
5
|
-
Students who share course content without the instructor’s express permission, including with
|
6
|
-
online sites that post materials to sell to other students, could face appropriate disciplinary or
|
1
|
+
<p>Please do not share material from this course in online, print, or other media. Course material is
|
2
|
+
the property of the instructor who developed the course. Materials authored by third parties and
|
3
|
+
used in the course are also subject to copyright protections. Posting course materials on external
|
4
|
+
sites (commercial or not) violates both copyright law and the CSU Student Conduct Code.
|
5
|
+
Students who share course content without the instructor’s express permission, including with
|
6
|
+
online sites that post materials to sell to other students, could face appropriate disciplinary or
|
7
7
|
legal action.</p>
|
@@ -1,5 +1,5 @@
|
|
1
|
-
<p>Any CSU student who faces challenges or hardships due to their legal status in the United States
|
2
|
-
and believes that it may impact their academic performance in this course is encouraged to visit
|
3
|
-
<a href="https://undocumented.colostate.edu/">Student Support Services for Undocumented, DACA & ASSET</a>
|
4
|
-
for resources and support. Additionally, only if you feel comfortable, please
|
1
|
+
<p>Any CSU student who faces challenges or hardships due to their legal status in the United States
|
2
|
+
and believes that it may impact their academic performance in this course is encouraged to visit
|
3
|
+
<a href="https://undocumented.colostate.edu/">Student Support Services for Undocumented, DACA & ASSET</a>
|
4
|
+
for resources and support. Additionally, only if you feel comfortable, please
|
5
5
|
notify your professor so they may pass along any additional resources they may possess.</p>
|
@@ -1,3 +1,3 @@
|
|
1
|
-
<p>The <a href="https://diversity.colostate.edu/mission-vision-and-goals/">Mission, Vision, and Focus</a>
|
2
|
-
webpage of the Vice President for Diversity includes a
|
1
|
+
<p>The <a href="https://diversity.colostate.edu/mission-vision-and-goals/">Mission, Vision, and Focus</a>
|
2
|
+
webpage of the Vice President for Diversity includes a
|
3
3
|
comprehensive statement of CSU’s commitment to diversity and inclusion.</p>
|
@@ -1,12 +1,12 @@
|
|
1
|
-
<p>This course will adhere to the CSU <a href="https://catalog.colostate.edu/general-catalog/policies/students-responsibilities/#academic-integrity">Academic Integrity/Misconduct</a>
|
2
|
-
policy as found in the General Catalog and the <a href="https://catalog.colostate.edu/general-catalog/academic-standards/academic-policies/">Student Conduct Code</a>.</p>
|
3
|
-
|
4
|
-
<p>Academic integrity lies at the core of our common goal: to create an intellectually honest and
|
5
|
-
rigorous community. Because academic integrity, and the personal and social integrity of which
|
6
|
-
academic integrity is an integral part, is so central to our mission as students, teachers, scholars,
|
7
|
-
and citizens, I will ask that you affirm the
|
8
|
-
<a href="https://tilt.colostate.edu/Integrity/Pledge">CSU Honor Pledge</a>
|
9
|
-
as part of completing your work in this course.</p>
|
10
|
-
|
11
|
-
<p>Further information about Academic Integrity is available at CSU’s
|
1
|
+
<p>This course will adhere to the CSU <a href="https://catalog.colostate.edu/general-catalog/policies/students-responsibilities/#academic-integrity">Academic Integrity/Misconduct</a>
|
2
|
+
policy as found in the General Catalog and the <a href="https://catalog.colostate.edu/general-catalog/academic-standards/academic-policies/">Student Conduct Code</a>.</p>
|
3
|
+
|
4
|
+
<p>Academic integrity lies at the core of our common goal: to create an intellectually honest and
|
5
|
+
rigorous community. Because academic integrity, and the personal and social integrity of which
|
6
|
+
academic integrity is an integral part, is so central to our mission as students, teachers, scholars,
|
7
|
+
and citizens, I will ask that you affirm the
|
8
|
+
<a href="https://tilt.colostate.edu/Integrity/Pledge">CSU Honor Pledge</a>
|
9
|
+
as part of completing your work in this course.</p>
|
10
|
+
|
11
|
+
<p>Further information about Academic Integrity is available at CSU’s
|
12
12
|
<a href="https://tilt.colostate.edu/TipsAndGuides/Tip/18">Academic Integrity - Student Resources</a>.</p>
|
@@ -1,3 +1,3 @@
|
|
1
|
-
<p>Please review the core <a href="https://tilt.colostate.edu/TipsAndGuides/Tip/128">rules of netiquette</a>
|
2
|
-
for some guidelines and expectations on how to
|
1
|
+
<p>Please review the core <a href="https://tilt.colostate.edu/TipsAndGuides/Tip/128">rules of netiquette</a>
|
2
|
+
for some guidelines and expectations on how to
|
3
3
|
behave in an online learning environment, such as canvas.</p>
|