Starting this project alongside my teammate who we both were in a separate team before it disbanded and we were placed into this team, I didn't have a lot of confidence in joining a new team while they’re halfway through their development. I wasn’t confident that I would be able to find an easy way to ease into the programming side of the project, being exposed to someone’s code who hadn’t prepared for another programmer seemed frightening to me. But despite my worries things worked out really smoothly.

I spoke with the programmer on items they are working on that I could handle so they can focus on bigger picture stuff while I get an understanding of the already in place code so when I handle new systems and bigger responsibilities I don’t accidentally mess up some of the code. This worked perfectly as we ran into a very serious couple of bugs a few hours before our playtest. 

This error for our map caused many issues for the systems we had in place, movement was not functional at all, with only the afternoon to fix it me and the original programmer sat together and went through different sections of the code while testing separate theories to cut on the time needed to debug. And since I took the time before to get an understanding of the code, it was very easy to test anything related to the movement, which I would not have been able to do last week, which inevitably saved the playtest build as I was able to figure out what had happened a few hours after we discovered it. Along with this I was able to get many debug features in for our developers for the playtest build, things that will make the workflow of our testers much easier while adding some small quality of life additions for our playtesters so there isn’t any misunderstanding while they play.