Open Emaad-Mir opened 7 months ago
Had every requirement, nice demos and explanations too! Good calling back to previous mistakes too.
NOTE: This didn't dock your score but I would try moving a little slower when presenting. Not a huge thing but it would help the quality of your presentations.
Emaad Mir's Individual Review Ticket
Frontend contributions:![image](https://github.com/TEE-CSA/TEE-Frontend/assets/86995831/18a7d5b8-5e7b-4ef7-a794-be3c54a8c63c)
Key Commits:
Backend contributions:![image](https://github.com/TEE-CSA/TEE-Frontend/assets/86995831/2a685869-85cd-4ab7-9fba-5c1f0fb79088)
Key Commits:
Reflection
One significant (individual) improvement that I made was fixing the inconsistent functionality of the betting system for both the Fibonacci and the sorting races. At the time of our crossover review, we still had a few issues in getting the betting implementation to work for arrays of all sizes. What we have for our project now is definitely a large improvement from what we had a few days ago, as now users can play the racing game, place bets, and see the pop up message at the end informing them if they won or lost along with a fun fact about the sorting algorithm that won. One thing that I learned from doing this project was knowing the order of the different sorting algorithms from fastest to slowest. This was a very important part of our project, as we needed to ensure that the time it took for each sorting algorithm to travel across the whole track accurately reflected its efficiency compared to the other algorithms. For example, the sorting algorithms from fastest to slowest is usually merge sort, insertion sort, selection sort, and bubble sort. Therefore, we had to construct the race so that as efficiency increases, the time to cross the finish line decreases. As with any project for this class or any team-related activity, I learned about the absolute necessity of communication. My group members (Tay Kim and Ethan Tran) and I made a group chat for our scrum team, and us communicating ensured that we wouldn’t be running into issues such as merge conflicts. We would always inform each other if we were going to make any changes to certain files or commit some code. If something suddenly stopped working, one of us would always inform the group chat so that everyone was aware. Overall, I fully understand the significance of talking to your group mates/teammates, whether it is in this class or in situations beyond this class.