CSP Final, N@tM Retrospective | Isabel Marilla Individual Review | Period 2

[iKAN2025]

My written review consists of my

• [x] blog of CPT project, plans and completion of work here
• [x] design, an article that contains the preparation of key features before coding
• [x] correlation to CPT, an article that shows how your feature maps to College Board requirements
• [x] pull request(s), an issue containing a link to your pull requests from fork or branch to the main
• [x] code commits, the comments & deltas in GitHub that prove your work
• [x] one-minute video, prepared in CPT style to highlight your feature with the project https://www.veed.io/view/86f3e6a6-82b5-4f4b-9bd6-0bb3c6fe4778?panel=share

[jm1021]

Your blog and all pieces on journey are looking very nice. Try to fix these things quick.

Problems:

1. CPT requirements could be bullets with response to stand out better. Not nested in paragraph. Perhaps state or show CPT requirements clearly in blog so I know you are working from CB materials.
2. Video is private, I can't get to it.

[iKAN2025]

Thank you for looking at my blog! :) I fixed all the changes. Let me know if it works!!!!!

[7mwang]

Glows:

• Gives short summary of project as introduction
• Provides links to previous issues to show workflow and planning
• CPT requirements gone over concisely in table
• Commits aren’t just a big list, but gives key commits for specificity
• Page shows clear organization in project
• Video requirements also were discussed on blog page
• Video also goes over everything nicely, and covers feature of website Grows:
• Video could have used a bit more editing, perhaps zooming or highlighting

Overall, I think you did wonderfully with this blog and video. It’s super organized and has enough information to provide evidence of fulfilling the CPT requirements, but doesn’t overwhelm the reader, as it is very easy to understand. Your video also goes over your feature at a nice pace. All requirements were completed, plus having really good organization. 1.1/1

[jm1021]

Glows:

• Gives short summary of project as introduction
• Provides links to previous issues to show workflow and planning
• CPT requirements gone over concisely in table
• Commits aren’t just a big list, but gives key commits for specificity
• Page shows clear organization in project
• Video requirements also were discussed on blog page
• Video also goes over everything nicely, and covers feature of website Grows:
• Video could have used a bit more editing, perhaps zooming or highlighting

Overall, I think you did wonderfully with this blog and video. It’s super organized and has enough information to provide evidence of fulfilling the CPT requirements, but doesn’t overwhelm the reader, as it is very easy to understand. Your video also goes over your feature at a nice pace. All requirements were completed, plus having really good organization. 1.1/1

Mathew does a nice job of highlighting some likes. This shows that he is very vested in his grading and is picking out gems that he likes, or that need improvement. I watched this video as well and though it has many great qualities there is something about things like "zooming", "highlighting" that need improvement. Isabel does a great transition to backend home page and showing JSON/Collection in action; I think this is part of the running system and shows power of work leading into writeup about Collection. Mathew calls out some elegant things "commits aren't a big list", "vide requirements are on the blog". These call outs are not only glows, but perhaps things Mathew could incorporate or learn form.

[Lin-cT]

Glows (Blog):

• The blog is concise and organized
• Shows teamwork and cooperation through the writing, as many features were worked on with others
• Links to the brainstorming and checkpoint blogs, demonstrating thought out planning and good documentation of project
• Fleshed out explanation of the purpose of the project and functionality
• CPT Requirements is organized in a table with each requirement clearly listed and a concise explanation of how their code satisfies requirements
• Describes aspects of the video, helping viewer to better understand what information the video encompases
• References a few key commits

Grows (Blog):

• Bullet pointed information would have made information easier to process and much more concise
• More pictures of code demonstrating the requirements could help provide concrete proof of met requirements in project
• Link to video in blog would have been nice

Glows (Video):

• Captions are easy to see and read
• Demonstrates and explains the code nicely
• I like the console and backend code demonstrations
• No mouse wiggling

Grows (Video):

• Zooming in on the features would help it stand out and would be easier for the viewer to understand what is going on

I think you did wonderfully overall. There is plenty of information within your blog post that demonstrates a well fleshed out project. Multiple links to documentation show well thought out planning of the project before execution. The blog is easy to understand and the information is easy to process. The requirements are described in decent detail, although some pictures of the code would be nice to have. Overall, I think this is a great blog.

1.1/1