Reflections - Githubissues

What went well

Effective communication helps streamline experience. Being very clear on what each person is thinking and that the other person understands what is being communicated
Managing frustration! It would have been very easy to get off track when we weren't able to achieve what we wanted, but we were able to take a breath, take a break, and then evaluate optimal next steps

It might sound funny given what we said previously, but planning! We took a whole day to plan things out, which gave us a solid foundation of how we wanted to construct our app moving forward. What we didn't account for was unexpected problems and delays that come up - we learned that we should probably expect those sorts of things to happen in any project.
Our division of labor from synch-to-synch. We tried to be very clear on who was working on what file, what names for variables are, and where our code should connect with the other person's

Scoping! We vastly overestimated the achievable scope of our project. While this was frustrating, it was also a great learning experience on how to manage time schedules and the iteration process. As we gathered the data necessary to build all the various pages of our app, we started to better understand how we could have built towards a smaller feature set, and then expanded it, while still meeting the requirements of the project.
Choose a better API to construct a project around - we were warned that the API was hard to work with, but we felt we could do it because we had seen other apps that used it. We should have taken more time to evaluate where our skill level was at with the time period we were given

I encountered a 'programmer adage' last week that stuck with me: 'When evaluating the time it takes for a project, double that estimation, then double it again.' While the adage might go overboard, the core principle is sound - your app is always going to take longer than you think. Scope accordingly.