Being on a team and remembering to communicate and check my Teams can be challenging. Sometimes I forget that I have to check if any of my team members messaged me. I was able to get all of my work done easily and quickly but had to wait to test my code until another team member finished their stuff. I really enjoyed my task for this project since I am getting pretty good at writing test codes for a class.

A problem that seems to keep happening is people not responding and also what times people get their work done. Since it is a group of people mixed with undergrads and grad students we all lead very different lives and therefore have very different schedules. While some of us work during the day others work at night. I also, depending on the day, try to focus solely on one class on certain days and therefore totally forget about checking Teams for this class sometimes. I am getting better at checking it though.

Time for project three!

I haven’t been on a team since I quit basketball my senior year of high school after 12 years of playing it year-round. I missed being on a team and having people with my back, but I didn’t miss having teammates who didn’t want to be on a team and only looked out for themselves. I worked with my teammates great, well at least the ones that actually responded in the teams chat, and I was able to get all my work done. I also had a great teammate that jumped on a call with me multiple times to help me figure out my problem with gradle. I now know to use intellij going forward with the projects involving gradle since my visual studio code was not happy with gradle.

In conclusion, I enjoyed this project thanks to a few awesome teammates. I hope the next project goes just as well and hopefully a little smoother.

Never again.

I learned a lot from this assignment. I learned that it sucks to start a project, that I had 2 weeks to get done, the night before it was due. It was painful. I pulled a 12-hour coding marathon in one day. The reason I had to start late was because I didn’t figure out my software issue that was not allowing me to start it because I missed office hours the week before since I was at a women in tech convention and then my professor sacrificed his time Wednesday night to meet with my after his class that ended at 10pm. It was a draining process but it also taught me a very good lesson. I will act immediately if I am having trouble in the class rather than trying to figure it out by myself with no help and waiting last minute to ask my professor to help me.

The code itself was also difficult but I know I did a good job and I’m proud of myself. I am also happy that now I have code that I have written well that I can reference if I ever get stuck since I needed a refresher in Java. Overall, it was a very memorable assignment.