Anusha Khobare - Individual Review Ticket

[Flying-Book]

Name	Team+Indi+Teacher	Issues	Key Commit(s)	Analytics
Anusha Khobare		Team Review Ticket	SASS buttons, Binary Source, Binary Shift Interaction Added, Binary Converter + Infographic, Binary Games	See GitHub Profile

---

Link to website: https://jplip.github.io/frontTri2/Binary%20Representation/

Project Retrospective: Binary Calculator Development

What Went Well:

• Feature Development: Successfully implemented the Binary Calculator and Binary Games Functionality.
• Collaboration: Demonstrated strong teamwork among the team, individual, and teacher contributions through joint team infographic.
• Problem-Solving: Resolved Imaging Issues in Infographic, and Binary Games broken functionality

What Could Be Improved:

• Imaging: Infographic uses links because image preview was not showing for ASCII Tables
• Documentation: Enhance documentation (Read Me + Comments)
• Issues: More sub-issues when problems occur + task lists within github

Key Achievements:

• Incorporation of SASS buttons and Binary Source, enhancing the project's visual and functional aspects.

• Addition of significant features:

  • Binary Shift Interaction Added
  • Binary Converter + Infographic

  • Binary Games

    Link to Video https://clipchamp.com/watch/cS7JRP5YDm7

    Individual Review "My name" grading "Their name"

• [ ] 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.

Individuals Video, Issue(s), Commits(s)

• [ ] Video in CPT caption style , includes Web demo of key contribution to project, 1 minute
• [ ] Issue(s) that show plans/progress to team objectives
• [ ] Highlights of key commit(s) in Issues, summarizes code contributions

• [ ] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

  Per check.
  0.55 not attempted/no check 0.7 attempted, incoomplete, 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.

[Flying-Book]

Team Review Ticket: https://github.com/jplip/frontTri2/issues/4

[ArnavNadar]

Individual Review Arnav grading Anusha

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. Individuals Video, Issue(s), Commits(s)

Video in CPT caption style , includes Web demo of key contribution to project, 1 minute Issue(s) that show plans/progress to team objectives Highlights of key commit(s) in Issues, summarizes code contributions Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

Key contributor Score: 1 Good work division Contributed a lot to their project. Talked about team collaboration Great attitude during presentation Showed idea making process Talked about future additions

Video in CPT caption style Score: 0.86 Video went over everything but could have been more specific.

Issues Score: 0.9 They have their own personal review ticket issue.

Key Commits: 1 Commits are there when I was checking Team Review. There when checking contrbution history. Next time they could maybe corporate it within the exit ticket.

Git Hub Analytics Score: 0.87 Good amount of commits and each commit has value.