Trimester 2 Final Review

Trimester 2 Retrospective.

My Feature: Queue Status before trimester began:

• Feature was not deployed
• All control, including teacher were on one page
• Disorganized system of storing queues
• Backend did not store anything other than queue

5-Point Summary

1. Made queue usable on a deployed site
   
   • Any controls used by teacher were moved to a page on spring. Frontend features were limited to add and remove from queue.
   • Queue is stored as table, uses converter to convert to JSON
   • Queue automatically updates, no need to refresh
   • Created a modal to connect to assignment

Key Commits:
Queue Refresh - Image 3
Queue Converter
Separation into Backend and Frontend HTML page - Image 1
Assignment Modal - Image 2

Previous Image Next Image

Planning Issue

1. Implemented feedback and learnings from first usage.
   Queue was first used during a checkpoint in January. I learned several things, as I will always know how to use my feature, but other people might not and did not, resulting in several bugs.
   • Buttons can only be clicked once, and check that user is in appropriate list, avoiding null errors.
   • Timer count down is displayed in page title so user can view time while presenting.

Key Commits:
Feedback: Updating Names - All Images
Timer update: no null spam, timer in title - Image 5
Check if user is in correct queue - Image 4, 6

Previous Image Next Image

Planning Issue

1. Integration and Expansion of feature.
   On the first review, we had to go up individually, even though feature groups would have been more efficient.
   • Allowed teacher to choose group set of people to enter queue, allowing feature teams to be tracked in queue and present. Any user in queue could move team over.
   • Stored presentation length on backend, allowing teacher to set a dynamic presentation length.
   • Integration with table management to view gitHub profile based on click from backend

Key Commits:
Frontend support for Groups
Presentation Length: What can be done quickly, with practice
Previous Image Next Image

Planning Issue

1. Team Teach.
   Presented team teach on classes.
   • After first team teach, needed a way to keep other students attention, many people stopped paying attention. Introduced new FRQ format where people had to work together to answer an FRQ.
   • Introduced intentional mistakes to keep people’s eyes open and ensure that they stay attentive. Format improved attention and was used in following team teaches.

Key Commits:
Practice FRQ walkthrough
Classes tips
Team Teach

1. New convert_notebooks.py to automatically display mermaid images.
   
   • Modified convert_notebooks.py to convert any mermaid cells into an image, then display the image in the converted md file
   • Helped others set up mermaid and customize to their blog structure

Key Commits:
Mermaid convert_notebooks.py Previous Image Next Image

Process and Ideation Blog

Reflection and the Future

Next Steps:

• Group creator feature in conjunction
• Auto update name changes of users
• Is and Has relationships in mermaid

Growths

• Finished a working feature that was deployed and usable in class
• Took feedback based upon usage, realized the difficulty in making it usable for others, not just yourself who created it, and made it usable

Weaknesses

• Sometimes, need to take a step back and delegate work, letting others do and learn
• Need to have better monitoring system and review system/communication for pull requests. PRs containing things such as localhost links destroyed website more times than preferred. Improved over trimester, need to continue to improve
  • This was improved with recommended measures before N@tM, and successful demonstrations of features were held.
  • Also split up features into individual branches, ensuring that nobody messes with other files

Feature Details

The end goal with this is to allow future classes to continue to build upon the work we did. Part of this is documentation, and hence I decided to keep my combined mermaid diagram with the Calendar feature and hope that others continue to add on.
Feature Write Up: LINK
Diagram Summary: In Conjunction with Calendar

MCQ

Score 34/39. Score was OK but more silly mistakes were made than I would’ve liked. MCQ Corrections: LINK
Biggest Mistake: Not reading carefully. Need to read after how many times loop passes, double check selected correct answer, etc.

Night at the Museum

N@tM was a successful presentation. Me and Jon presented our projects to teachers, parents and students, and received feedback. Some of this feedback was minor fixes such as a centering issue that I didn’t notice, but the biggest piece was that there should be a button if you would like to end your presentation early. This was reflected by several parents and several teachers (i.e. Mr. Askegreen).

Other Projects

I walked around to other projects and provided some feedback on their feedback forms. One project that stood out was a national park review and travel tool. This project stood for me because of an interest in National Parks. Gave some recommendations, such as storing national park data on backend in addition to comment and review data.

A Side Project w/ A Fun Story

Story told during presentation.