badges only

brownsarahm · brownsarahm · commit 1064ce7f6032 · 2023-11-28T16:34:52.000-05:00
diff --git a/_practice/2023-11-28.md b/_practice/2023-11-28.md
@@ -0,0 +1,10 @@
+1. Pick a component that is in the more detailed von Neumann (other than the ALU) and contribute an explanation of what it is to your group repo. Coordinate with your team so that each contribution is a different component by creating an issue stating what you will work on before contributing. Link to your PR in the group repo in your badge PR. All contributions should include a description of the component- what it does and how it is built- and it's predecessors.  All must include sources as markdown links. 
+2. review a classmate's PR providing feedback and either approving or requesting changes
+3. Work with your group mates to ensure both your PR and the one you reviewed get approved and merged. 
+1. Read about [systems abstractions](https://cacm.acm.org/opinion/articles/259395-systems-abstractions/fulltext) in CACM and answer reflection questions below in {index}`systemsabstractions.md` based on the systems abstraction reading:
+```
+1. What are your overall thoughts on this article?  (include how much is neew vs familar, easy vs hard to understand, etc)
+2. How has you undertanding of these changed during this course.
+3. Do you think you understand this article more now than you would have at the beginning of the semester
+4. Write 3 questions and their answers that could be a quiz to see if someone understood or had misconceptions about the abstractions in this article.
+```
diff --git a/_prepare/2023-11-30.md b/_prepare/2023-11-30.md
@@ -0,0 +1 @@
+Spend a few minutes thinking about what you know about memory and reading and writing files in programming. Make some notes about it (that you do not need to submit).  (you'll discuss this with classmates at the start of class)
diff --git a/_review/2023-11-28.md b/_review/2023-11-28.md
@@ -0,0 +1,3 @@
+1. Pick a component that is in the more detailed von Neumann (other than the ALU) and contribute an explanation of what it is to your group repo. Coordinate with your team so that each contribution is a different component by creating an issue stating what you will work on before contributing. Link to your PR in the group repo in your badge PR. All contributions should include a description of the component- what it does and how it is built- and it's predecessors.  All must include sources as markdown links. 
+2. review a classmate's PR providing feedback and either approving or requesting changes
+3. Work with your group mates to ensure both your PR and the one you reviewed get approved and merged. 

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+Spend a few minutes thinking about what you know about memory and reading and writing files in programming. Make some notes about it (that you do not need to submit). (you'll discuss this with classmates at the start of class)`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	+1. Pick a component that is in the more detailed von Neumann (other than the ALU) and contribute an explanation of what it is to your group repo. Coordinate with your team so that each contribution is a different component by creating an issue stating what you will work on before contributing. Link to your PR in the group repo in your badge PR. All contributions should include a description of the component- what it does and how it is built- and it's predecessors. All must include sources as markdown links.
	`2`	`+2. review a classmate's PR providing feedback and either approving or requesting changes`
	`3`	`+3. Work with your group mates to ensure both your PR and the one you reviewed get approved and merged.`