Pair Project Reflection

## Abstract
- The project assignment revolved around a website that created motivational posters. These posters could be randomly generated from a provided set of arrays including photos, titles, and quotes. We were also tasked with creating an input field in which the user would be able to create their own custom poster. A save functionality was also required to allow the user to store saved posters and delete any that were not wanted.

## Overall
- My approach to working on a team was wanting to provide constant support for my project partner and completing the project together in a collaborative setting. We would take turns coding and committing, and ensured every decision made was agreed upon by both team mates. We chose to set aside time from our days to both be present and ready to work. Anna and I both like to disconnect from classes with a gym session right afterwards, which worked out perfectly for us. 

## Technical
- A resource we used when reaching a technical challenge was other classmates in different breakout rooms. When Anna and I reached a part that we both could not solve, we would reach out to our classmates for advice on how to solve an issue. For example, for the last function needed to add a way to delete the element that the user clicked on. A classmate advised us to try the "event.target.value" method. After research, we realized this would work for our inteded purposes and incorporated it into our code.

## Reflection
-One personal takeaway I had on this project is the importance of realizing when I needed to reach out for help. Turing has a unique way of presenting us with a problem and not always providing the answers / methods to solve it until a few days later. I realized that it is imperative to know when to reach out for help and not take too long struggling on the same problem. 

-One technical takeway from this project I have is the importance of clear communication while using Git. Being in tune with your teammates is very important when pulling / pushing changes so you can avoid having merge conflicts. 

-For the next project I want to focus on using my time wisely and not getting hung up on a problem. I also want to be able to clearly communicate when I have reached fatigue because near the end of Saturday I was so tired that it was hard to keep up with my partner. 

===================================================================================================

Group Project:

## Overall
- My approach to this project was to initially work on the project together until we got to a point where each team member could split up and work on a section. This worked well because we ended up switching to each other's branch and got to all get practice in JS, CSS, and HTML.

## Technical
- A resourse I used when stuck was cohort mates. We would post in the question in Slack and individually break off into other breakout rooms to discuss the problems and find the answers. We would then come back and explain what we learned to the other 2 teammates. 

## Reflection
-One personal takeaway I had on this project is to be cogniscent of self-care. We would be hardstuck on an issue for far too long and not remember to walk away. For future projects I will set an actual timer and commit to walking away once time ran out.

-One technical takeaway I have from this project is regarding asking for help. There were times where we got help from another group but it was not enough to get us to a solution and we would be stuck for another hour. I think knowing when to ask for the answer and an explanation instead of a hint would be more productive
and a better usage of our time.