revision

Author: oliiso

Diff for: _docs/developer/google_summer_of_code/2024_Sophia_Oliinik.md

@@ -4,18 +4,17 @@ category: Developer > Google Summer of Code 2024
 ---
 
 ## Overview of project:
-My summer GSoC 2024 project was Enhancing User Interface for Viewing Grades. While originally, this was intended to focus on the Rainbow Grades presentation, I also wanted to implement and update more visual representation for statistics about homework. It was decided for me to pivot a little more in the direction of gradeable specific statistics page, and bringing more updates to that. Because of this, I was able to add some updated user interface design to Rainbow Grades and the Statistics page for gradeables. 
+My summer GSoC 2024 project title is Enhancing User Interface for Viewing Grades. While originally, this was intended to focus on the Rainbow Grades presentation, I also wanted to implement and update more visual representation for statistics about homework. It was decided that I should pivot a little more in the direction of gradeable specific statistics page, and bringing more updates to that. Because of this, I was able to add some updated user interface design to Rainbow Grades and the Statistics page for gradeables over the course of this summer. 
 
 
 
 ## Outside of programming
-Submitty implemented a great system for continuous integration and check-ins for the summer contributors. This was successful through the daily "Stand up" meetings that we had. This brought a great opportunity for showing your work, getting second opionions, asking questions, keeping things accountable, and seeing where other contributors were at with their work. Another element of our meetings included demonstrating our work, and recieving feedback from the team. I was able to do so with a few of my projects, and it was a great way to learn what worked and what changes were needed to add, along with my presentation skills I communicated with my mentor, Jaeseok Kang, through video calls and messaging, where we discussed barriers I came across, and status updates. These were very helpful to me in my process of working on Submitty through the summer, and I was able to learn a lot as a programmer through this. Along with these, my initial weeks were spent with time taken to understand the extensive code base that Submitty has, along with the structure of the system.
+My initial weeks were spent understanding the code base that Submitty has, along with the structure of the system. Submitty implemented a great system for continuous integration and check-ins for the summer contributors. This was successful through the daily meetings that we had. This brought a great opportunity for showing your work, getting second opionions, asking questions, keeping things accountable, and seeing where other contributors were at with their work. Another element of our meetings included demonstrating our work, and recieving feedback from the team. I was able to do so with a few of my projects. It was a great way to learn both what worked, and what changes were needed. Along with this, I also got feedback from my mentor through the summer. Through video calls and messaging, we discussed barriers I came across, and status updates. These were very helpful to me in my process of working on Submitty through the summer, and I was able to learn a lot.
 
 
 
 ## Pull Request work:
-### PR's
-Below are the pull requests that I worked on and were merged this summer. The main area of issues that I worked on included Rainbow Grades UI and instructor grading data statistics. These links include documentation PR's, a PR to the Submitty repo, and PRs to the RaibowGrades repo. 
+Below are the pull requests that I worked on this summer. The main area of issues included Rainbow Grades UI and instructor grading data presentation. These links include documentation PR's, a PR to the Submitty repo, and PRs to the RaibowGrades repo. 
 
 - [#77](https://github.com/Submitty/RainbowGrades/pull/77) [Feature:RainbowGrades] Adding hover text to rainbow grades bad status cells
     * This was one of the first additions I brought to Submitty. It added a feature to the rainbow grades gradebook page that implemented a hover text box for students that had a "bad status" on a homework. This brings more attention that the student can look into why they have a bad status on the assignment, and it brings convenience for instructors in their larger gradebooks to see who has a bad status and on what assignment with just hovering their mouse over the cell. 
@@ -54,8 +53,9 @@ Having this review processes this summer really taught me a lot as a new contrib
 - [#10840](https://github.com/Submitty/Submitty/pull/10840) add term and course
 - [#56](https://github.com/Submitty/RainbowGrades/pull/56) display rainbowgrades version
 - [#10763](https://github.com/Submitty/Submitty/pull/10763) add gradeable percents to GUI
+- [#10859](https://github.com/Submitty/Submitty/pull/10859) add performance warnings to display
 
 
 
 ## Acknowledgments:
-I am very greatful for this summer opportunity to work on Submitty. Through these weeks, I was able to grow a lot as a programmer, team member, and mentee. The daily meetings were an immense help in learning how to communicate where you are at with your work, and a great place to learn to ask for help. Through these meetings I was able to grow a lot as a professional. Working on the code base itself was also a large part of how I grew this summer. I was able to take time to understand previous code that was written, and consider how to bring the changes needed in a consistent way. Halfway through the summer, I had a pivot in the focus of my project, it helped teach me to be adaptable and to learn new parts of Submitty that I was not previously accustomed to. Going through the review process of getting a pull request approved was a good process to learn what areas were working, and what areas I can improve my code. Along with this, being able to review other contributors PR's was a great reference to be able to learn how others were improving the system, and the process they went through to bring their implementations. I want to thank Barb Cutler, Jaeseok Kang, Cameron Peterson, and Preston Carman for their mentorship through my summer with Submitty. 
+I am very greatful for this summer opportunity to work with Submitty. Through these weeks, I was able to grow a lot as a programmer, team member, and mentee. The daily meetings were an immense help in learning how to communicate where you are at with your work, and a great place to learn to ask for help. Through these meetings I was able to grow a lot as a professional. Working on the code base itself was also a large part of how I grew this summer. I was able to take time to understand previous code that was written, and consider how to bring the changes needed in a consistent way. Halfway through the summer, I had a pivot in the focus of my project, it helped teach me to be adaptable and to learn new parts of Submitty that I was not previously accustomed to. Going through the review process of getting a pull request approved was also a great process to learn what areas are working, and what areas I can improve my code. Along with this, being able to review other contributors PR's was a great reference to be able to learn how others were improving the system, and the process they went through to bring their implementations. I want to thank Barb Cutler, Jaeseok Kang, Cameron Peterson, and Preston Carman for their mentorship through my summer with Submitty.