CPT Final Individual | CompSci Blogs

Write-Up Strength(s) Generally, I feel that your write-up is brief, which I see as a good thing. Descriptions of individual segments/fragments of overall project/feature code seem to both cover what is needed to map to/fulfill CPT program requirements and simultaneously not drag out unnecessarily. I can learn from this and apply to future write-ups for myself; in my Mapping, I felt I made code explanations that, although thorough, may have included excessive description.

Note: this is for both your Write-Up and Video--clarifying feature vocabulary such as "elixir cost" or including some additional context could help clarify for any actual CPT graders, just in case.

Comments for Code Code appears somewhat simple, but that may not be a bad thing...

A major strength I see is use of cumulative code learned throughout CSP course so far through lessons like Team Teaches, previous coding activities, or even Live Reviews. Because a lot of the code is part of the curriculum, this could be a nice advantage in the eyes of CPT graders. Usage of coding methods like sorting through lists or quiz questions and answers exemplify this.

This is just an assumption on my part, but possibly distinguishing various fragments of code referenced in Write-Up between Backend and Frontend could be necessary/helpful for future true CPT grading.

Possibly clarify if/how data from generating deck(s) through quiz + editing through swapping cards is stored. Local storage? Database?

CPT Video Notes Immediately I notice strength in how video is formatted and edited. For the most part, captions are simple and quick yet still readable and still provide sufficient context/explanation. I can learn from this, as this might contrast to my personal CPT Video, which included too much text in captions, which didn't pair well with my Video pacing. Visuals such as arrows pointing to various specific assets of feature are also well done.

Your deck-editing page (result following Quiz) may lack some context/instructions. Here are some suggestions:

Possibly displaying elixir value for individual cards could add more meaning to average elixir cost value and add more complexity to overall feature.
More instructions could be nice. Possibly more specific hints telling users what card swapping does/what the meaning of it is could be helpful. Note: why swap only two specific cards each time? Are there only two cards that could be swapped out since they are categorized as spells/defense/offense or something? Card swaps are defined as "viable", but maybe some additional context could go a long way.

Score: 4.7/5

Project seems to meet requirements and include various aspects that could be seen as advantages in CPT grading, but might lack finalization.

LincolnC2008 / student3

CPT Final Individual | CompSci Blogs #6

CPT Final Individual | CompSci Blogs