-
What role do you typically play on a team?
I've been in leadership and managerial roles in earlier life playing sports, and in work environments. I take a big picture approach to things, and thus often have a certain level of understanding of all rolls in a group and how to organize them. In this project I took the liberty of setting organization standards by creating a gh projects page to organize our workflow. In situations like this project where I don't feel I have a good enough grasp on aspects of whatwe need to do, I am always happy to defer to those who do and focus on listening and understanding.
-
What resources or strategies did you use when you were presented with a technical challenge?
We had several instances of bugs appearing that we could not solve by reviewing the code, and deferred to using the debugging tools in the browser dev tools. This was, I believe, a first time for all of us really utilizing those tools in a real time problem problem solving situation and it was very satisfying to uncover the mystery of the bug through those means.
-
What is one personal/professional takeaway from this project?
The process of github workflow with PRs, commenting on them, and merging is difficult to focus on when you're trying to focus on all the other aspects of a project, but it is important to practice those things.
-
What is one technical takeaway from this project?
The debugging tools in the dev tools are my friend and very effective. Keep using those whenever possible.
-
Based on these takeaways, what is something you want to focus on for the next project?
Focus on organization. Github workflow and psuedocoding are very important. I want ensure I have a very solid thought out idea of how I'm going to approach a segment of the project, ensure I am 100% solid on it, and have a clear vision forward from that point.