progress

[varunm532]

• For the logic gate part, we have incorporated an interactive truth table for all of the logic gates.
• Then we are planning to add a randomly generated quiz about logic gates which would randomly decide the inputs and outputs. Then the user would have to match it with the corresponding logic gate(s). Logic from the previous part (interactive truth table) will be used to check if the answer is correct.
• Then we would like to add an overall theme which would look good for the UI.
• Added new quiz

  Finish new quiz based off recommendations

• Make add picture inside button and code it so that the border is highlighted with clicked
• Code logic for quiz
• Code function to check user input

  Progress

• Made button border highlighted when clicked
• Completed majority of logic code
• Coded function to check user input
• Fixed bugs with logic
• Integrated old quiz to page and fixed conflicting variable bugs

  Future additions ideas

• Make second quiz user friendly
• Condense code

link to project: https://tdwolff.github.io/NAVTFrontend/basics/logicgates

• Major commits:
  • Logic for 1st quiz
  • 1st quiz logic bug fixes
  • New quiz

-link to video: https://youtu.be/t56tQb8sSa0

[vibha-yganji]

Individual Review "Vibha" grading "Varun"

• [x] 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)

Varun's Video, Issue(s), Commits(s)

• [x] (0.9) Video in CPT caption style, includes Web demo of key contribution to project: Varun's video showed key commits and appropriately explained the project to me. Captions were also easy to follow along with.
• [x] (0.9) Issue(s) that show plans/progress to team objectives attempted, incomplete, but some runtime: issues containing team progress along the duration of the project were made + showed helpful suggestions for the future.
• [x] (0.8) Highlights of key commit(s) in Issues, summarizes code contributions mastery and runtime: key commits were high in number and were important to the project. When he explained the project to me, it was clear what he had done that and how his contributions were important to the project.
• [x] (0.9) Review GitHub analytics for key commits in each weeks during the project: commits were very high and well-spaced out across the duration of the project, he went above and beyond in contributing to the project.

Overall: 0.9

Very high-level number of commits that were regularly done + extensive knowledge of the project. The video was very detailed and clearly showed his contributions to the project. When explaining his project, he clearly gave me a walkthrough and sure I understood what he had contributed. However, he should create issues throughout the course of the project to keep track of overall team progress.