Issue(s) that show plans/progress to team objectives
Iteration Review (the rest I was absent for), however, I created a GitHub project to track what we were doing throughout our project
Highlights of key commit(s) in Issues, summarizes code contributions
Shown below. I was the pseudo-backend/devops, and I did the frontend-backend connection, as well as the bogosort and insertion sort algorithms. I also set up the system by which we would have inheritance for our sorting methods
Review GitHub analytics for key commits each week during the project, shows consistent participation for 3 weeks
Screen Shots Below
Commit Graphs
Backend
Frontend
Key commit and code evidence
Creating the Inheritance Framework:
Insertion Sort Code
Bogo Sort Code (I really wanted to try it so I did it, we planned for it to be implemented but it never was
API Controller
Key project takeaways, and improvements for actual project
Throughout this project, I learned how to improve my collaboration skills with other team members, as well as work on some parts of Java I wasn't technically proficient in. Throughout last trimester, our project, while ambitious, had been muddled by miscommunication, supply chain issues, and more, which led to a project that was under what we wanted to complete. Thus, this trimester, I vowed to try and complete the project we set out to. For the first week however, this wasn't true. I was slacking off and not really using my weekends to my fullest. But midway through I changed that. I started setting more consistent schedules for myself (which I used to hate) and adhered to them. I made time for coding, even asking my father for advice on how he plans coding with breaks. Through this, I became much more efficient in my coding, and I even looked into sounds that could help my study, like brown noise. This project has helped me greatly in improving my time management and communication skills.
This project also helped me understand Spring. Many of the people I had worked with before often used tools like ChatGPT or the internet to understand how Spring worked. While that was fine for the time being, I knew that if I was going to be coding Spring, I had to do it myself (I really like coding by hand as opposed to ChatGPT). So I spent time dissecting each part, each decorator, each method, to see what they did, and eventually I was able to grasp how the sorting methods were used. Through this I also gained an appreciation for the framework surrounding spring, including the POM files, which are truly amazing at reducing installation times, and the JWT security and CORS. I definitely appreciated being able to set what origin our Spring application could accept.
Nevertheless, I still used ChatGPT to an extent in my project, as I have for other internships, and I found that it has been extremely useful. Throughout this project, while I seldom asked ChatGPT for code, I still used it heavily as a debugging tool, similarly to many of my peers. I found that it's not just great for giving answer, it also is great because it points out areas that you may not have seen, and you can use your human intuition to gather what may be the issues there. I used ChatGPT to bounce off ideas, and see what I could do to solve an issue.
Throughout this project, I've learned many things, including the value of many tools we use, to many soft skills that I'm sure to take into our passion projects. But while still I have improved, it is imperative that I take these skills into the passion project with full force, and I don't let them go, lest I have to deal with the consequences and time loss of having to deal with them.
Individuals Video, Issue(s), Commits(s):
Commit Graphs
Backend
Frontend
Key commit and code evidence
Creating the Inheritance Framework:
Insertion Sort Code
Bogo Sort Code (I really wanted to try it so I did it, we planned for it to be implemented but it never was
API Controller
Key project takeaways, and improvements for actual project
Throughout this project, I learned how to improve my collaboration skills with other team members, as well as work on some parts of Java I wasn't technically proficient in. Throughout last trimester, our project, while ambitious, had been muddled by miscommunication, supply chain issues, and more, which led to a project that was under what we wanted to complete. Thus, this trimester, I vowed to try and complete the project we set out to. For the first week however, this wasn't true. I was slacking off and not really using my weekends to my fullest. But midway through I changed that. I started setting more consistent schedules for myself (which I used to hate) and adhered to them. I made time for coding, even asking my father for advice on how he plans coding with breaks. Through this, I became much more efficient in my coding, and I even looked into sounds that could help my study, like brown noise. This project has helped me greatly in improving my time management and communication skills.
This project also helped me understand Spring. Many of the people I had worked with before often used tools like ChatGPT or the internet to understand how Spring worked. While that was fine for the time being, I knew that if I was going to be coding Spring, I had to do it myself (I really like coding by hand as opposed to ChatGPT). So I spent time dissecting each part, each decorator, each method, to see what they did, and eventually I was able to grasp how the sorting methods were used. Through this I also gained an appreciation for the framework surrounding spring, including the POM files, which are truly amazing at reducing installation times, and the JWT security and CORS. I definitely appreciated being able to set what origin our Spring application could accept.
Nevertheless, I still used ChatGPT to an extent in my project, as I have for other internships, and I found that it has been extremely useful. Throughout this project, while I seldom asked ChatGPT for code, I still used it heavily as a debugging tool, similarly to many of my peers. I found that it's not just great for giving answer, it also is great because it points out areas that you may not have seen, and you can use your human intuition to gather what may be the issues there. I used ChatGPT to bounce off ideas, and see what I could do to solve an issue.
Throughout this project, I've learned many things, including the value of many tools we use, to many soft skills that I'm sure to take into our passion projects. But while still I have improved, it is imperative that I take these skills into the passion project with full force, and I don't let them go, lest I have to deal with the consequences and time loss of having to deal with them.