Skip to content

Commit 5f7cc16

Browse files
committed
notes
1 parent 5799744 commit 5f7cc16

File tree

7 files changed

+145
-0
lines changed

7 files changed

+145
-0
lines changed

_practice/2022-12-05.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
```{index}
2+
```

_prepare/2022-12-05.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
2+
1. Make a table that compares and contrasts the unix file system to git *as* a file system on at least 5 aspects (eg header + 5 rows) in `filesystem.md`. Based on this, write a definition of a file system generally and how knowing that these are both file systems helps reinforce concepts and improve understanding.
3+
1. In `whypointers.md` write a blog-post style argument for why understanding pointers as a concept is important for a computer science student even if they will not work directly in a language that uses pointers. Consider your audience to be a student who is in CSC212 and struggling. Use two examples from this class where we relied on the concept of pointers to explain how something worked.
4+
1. Reflect on how thise course impacts programming/debugging skills in `skillup.md`. You can write this as how you think your own skill has improved **or** as if you are convincing another student to take this class. Touch on at least three topics.

_review/2022-12-05.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
1. Review the questions from class today and in {index}`review.md` for any questions that you got wrong, write a solution and explanation for your confusion. If you missed class, write a solution guide for all of the questions in today's notes.
2+
1. Update your KWL chart by adding 2-3 rows about topics you learned about that are not listed.
3+
1. Add a new, up to date overview of how you think about computing overall to your KWL repo. Mark the one you made at the beginning as {index}`overview-post.md` and this one as {index}`overview-post` either with heading or the file name

activities/practice.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -210,3 +210,11 @@ Activities:
210210
Activities:
211211
```{include} ../_practice/2022-11-30.md
212212
```
213+
214+
## 2022-12-05
215+
216+
[related notes](../notes/2022-12-05)
217+
218+
Activities:
219+
```{include} ../_practice/2022-12-05.md
220+
```

activities/prepare.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -241,3 +241,11 @@ Activities:
241241
Activities:
242242
```{include} ../_prepare/2022-11-30.md
243243
```
244+
245+
## 2022-12-05
246+
247+
[related notes](../notes/2022-12-05)
248+
249+
Activities:
250+
```{include} ../_prepare/2022-12-05.md
251+
```

activities/review.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -236,3 +236,11 @@ Activities:
236236
Activities:
237237
```{include} ../_review/2022-11-30.md
238238
```
239+
240+
## 2022-12-05
241+
242+
[related notes](../notes/2022-12-05)
243+
244+
Activities:
245+
```{include} ../_review/2022-12-05.md
246+
```

notes/2022-12-05.md

Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
# How does all of this work together?
2+
3+
4+
## Contract Checkin
5+
6+
7+
8+
Create an issue on your grading contract using the following as a template, use the title, "Contract Checkin"
9+
10+
Edit so that it applies to you, including deleting any sections that do not apply to you.
11+
```
12+
I am (not) on track to complete my contract as agreed.
13+
14+
15+
I plan to (catch up/ revise my contract / take an incomplete).
16+
17+
To revise my contract I will:
18+
<!-- consultation is optional -->
19+
- [ ] attend office hours to discuss options
20+
- [ ] submit the revised contract as PR by the contract revision deadline of December 12.
21+
22+
23+
To catch up, I will:
24+
- [ ] request a review from @brownsarahm and @m-bowen in all of my open PRs by 7pm today
25+
- [ ] attend office hour on (dates)
26+
- [ ] complete (items) by 12/6 at 3pm
27+
- [ ] complete (items) by 12/8 at 5pm
28+
- [ ] complete (items) by 12/13 at 3pm
29+
- [ ] complete (items) by 12/15 at 3pm
30+
- [ ] complete (items) by 12/19 EOD
31+
32+
To complete work after accepting an Incomplete grade I will:
33+
- [ ] complete all activities in my contract by (date)
34+
35+
I have the following questions about my grade/grading in this course:
36+
37+
- [ ] q1
38+
- [ ] q2
39+
```
40+
41+
Assign @brownsarahm on the issue so that I can get to it easily.
42+
43+
Please *also* copy & paste your questions here on Prismia so that I can answer common, general ones in class. I will answer personal ones on the issue
44+
45+
## IDEA
46+
47+
If we hit a 75% response rate, then you will all get up to three "gifts" where instead of revising, I will give you an answer you need to acknowledge.
48+
49+
50+
## Review Questions
51+
52+
53+
Why do we need to lock writing to a global variable when threading a program?
54+
55+
- [ ] otherwise all threads will overwrite incorrectly and only the slowest one will be saved
56+
- [ ] otherwise their start/finish order can impact the calculation
57+
- [ ] it is the only way for a variable to be shared across threads
58+
59+
60+
Why do we use version control?
61+
62+
- [ ] to have a cloud backup of code
63+
- [ ] it's a legacy tool for undoing changes before IDEs could do it
64+
- [ ] to be able to separate different versions of code
65+
66+
67+
68+
69+
Why floating point instead of fixed point for fractions ?
70+
71+
- [ ] floating point allows for faster calculations
72+
- [ ] floating point allows more precise representation
73+
- [ ] floating point allows for representation of a broader range of values
74+
75+
76+
77+
78+
Label and put in order the following steps:
79+
80+
```
81+
82+
x. **step** binaries for compiled libraries is combined with the compiled program code
83+
x. **step** code is translated from assembly to machine code
84+
x. **step** code from includes is copied into the file
85+
x. **step** code is translated from a high level language to assembly
86+
```
87+
88+
89+
## Review today's class
90+
91+
```{include} ../_review/2022-12-05.md
92+
```
93+
94+
95+
96+
## Prepare for Next Class
97+
98+
```{include} ../_prepare/2022-12-05.md
99+
```
100+
101+
102+
103+
## More Practice
104+
105+
```{important}
106+
- If you're on track, you can skip the remaining ones
107+
- if you are not on track: **the remaining three will count for two each, but will be more complex**
108+
109+
```
110+
111+
```{include} ../_practice/2022-12-05.md
112+
```

0 commit comments

Comments
 (0)