jplip
commented
8 months ago Individual Review "Justin Liporada" grading "Torin Wolff"
- [✓] Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.
- contributes to the group and writes issues that he has. he is across the class so I don't see him or hear him but when talking to him, he was nice, kind, and easy to understand. 0.9/1
Individuals Video, Issue(s), Commits(s)
- [✓] Video in CPT caption style , includes Web demo of key contribution to project, 1 minute: the video takes a very calm and slow take and the cursor moves where it has to be and the captions are out of the way but in a slow enough fashion to read and calmly understand his video 0.9/1
- [✓] Issue(s) that show plans/progress to team objectives: wrote multiple issues but they were team related tickets it looks like and the one that he wrote that was his own problem and was able to fix it with no other issues 0.85/1
- [✓] Highlights of key commit(s) in Issues, summarizes code contributions: We talked about this personally and was able to talk about all problems and tell me instantly on what I was asking about 0.9/1
- [✓] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks: he participates all over the weeks and looks like multiple commits in a few of the days. 0.9/1
Per check. 0.55 not attempted/no check 0.7 attempted, incomplete, but some runtime 0.8 mastery and runtime 0.9 above and beyond.
Freeform comment. Provide positivies and growth summary. Justify or comment on final score. Be sure to provide extra details on anything below 0.7 average or above 0.8.
(0.9+0.9+0.85+0.9+0.9)/5=0.89
Justin's comments.
They talked about their issues and went through them.
I asked them questions about their work and answered immediately.
Showed me their key commits.
Worked throughout the weeks multiple times.
Nice to talk to as we were grading each other.
Alright, imagine your picture is made up of tiny dots called pixels. Each of these pixels can be a mix of colors—like red, green, and blue. We use numbers to describe how much of each color there is in a pixel. These numbers go from 0 to 255, where 0 means none of that color, and 255 means a lot.
Now, when we talk about sorting by color, we're talking about putting these pixels in order based on how much red, green, and blue they have. For example, if we have two pixels, one that's mostly red (let's say 255 red and 0 green/blue) and another that's all blue (0 red and 0 green, but 255 blue), we'd sort them by their red values.
The binary part comes in because computers really like 1s and 0s. So, when we write down these color numbers, we often use 8 bits of 1s and 0s for each color. It's like a secret code where each bit represents a power of 2, and adding them up gives you the color number. But, when we're sorting, we're mostly looking at the regular numbers (not the 1s and 0s) to decide which pixels come first in the order. It's like sorting your colored crayons by looking at the labels with the color names instead of the weird barcode numbers on the crayon wrappers.
If you're curious about how these colors turn into 1s and 0s, check out Binary colors for a sneak peek into the magical world of binary color codes!