Name: Adam Bowers
Partner: Kyle Schulz
Project Reflection
-
What is one thing that went unusually well during this project? The willingness to try each coding idea that was presented. I believed that allowed us to explore all avenues for solving the problem. Everyone was often available and made changes in his schedules to accommodate other members. He had a positive attitude and were open to all approaches to solving a problem. Each person took the time to answer questions about the code and how it interacted with other classes.
-
In hindsight, is there anything you would have done differently? It would have been helpful to review and discuss each iteration of the project prior to starting to code it. I feel we ran into issues on structuring classes and duplicating code that may have been avoided if we had fully understood the scope of the project. There were also issues related to not running prior tests after completing a new method. While this did not always create problems during the coding process, it did at the end because certain methods in earlier written classes were modified which caused previously written tests to fail.
-
Given these reflection questions, what specific, actionable steps will you take moving into your upcoming group project to continue your growth with working in technical teams? I will try to push my team to read the entire spec before coding any lines so that we can try to understand how the classes and modules should be structured to avoid issues with code architecture and to prevent duplicative code. Additionally, I will make running all prior tests after creating a new method a focus, so that any broken tests can be resolved shortly after new methods have been created.
-
If you were working with this partner again, what is something that you would want to focus on improving as a team? I would want to focus on the entire spec of the project prior to starting to code. I think we could derive a good blueprint for the general structure of the classes and modules.
Feedback for your partner
-
What strengths did your partner bring to the project? He understood the process of obtaining information about other classes that were not coupled directly with each other. He was able to take broad ideas an implement them into code. For example, we would brainstorm an idea of how to get classes with separate repositories to speak to each other. Additionally, he always took the time to explain how the code in previously written methods functioned. Even when we were in a time crunch, he was always calm and collected. Overall, it was clear that Kyle wanted to do a through job when coding.
-
What is something they could do better? I think it would be helpful to spend more time planning the overall design of the code.