Project: Mod 4 Paired
Group Member Names: Nathan Thomas, Fenton Taylor
-
What are each of our learning goals for this project? What drives us in this project?
N: Have a better understanding of javascript syntax
F: Get up to speed on testing frameworks in JS -
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
N+F: Both. There is a time and place for both. -
How do you communicate best? How do you appreciate receiving communication from others?
N+F: Frequently, in person and in Slack. Always know what each other are doing. Let each other know when we are stuck and going to miss deadlines. -
How would you describe your work style?
N: Get it done. Work diligently and persistently. Work late only if its productive.
F: Very persistent. I like to make it work, and refactor up front when it makes sense. -
What are each of our strengths? How can our strengths complement each other?
N: Communication. Good at asking questions. Researching implementation or previously unknown tech.
F: Communication. Design decision-making. -
What’s gone well or poorly in your previous projects?
N+F: Communication (both ways). Keeping track of projects on project boards. Actual collaboration on PR reviews. -
How will we set direction and make decisions as a team?
N+F: As a team. Both offer ideas, ask questions, and compromise. Don't make any big changes or decisions without consulting with partner first. -
How will we overcome obstacles?
N+F: Collaborate. Try solo first. Ask partner. Ask classmates. Then ask instructors. -
What do you need (resources, environment, communication) to do your best work?
N: Be well-rested.
F: I do my best work on my own when I am well-rested. I like to collaborate on design decisions first, though. -
What scheduling restraints do you have? What are your scheduling preferences?
N: Friday evenings.
F: I like to leave before 5 and work from home.
Workload Expectations (What features do we each want to work on?):
If one person seems to be getting more done than the other, we should pair more to balance the workload.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Use GitHub Projects
- Review and comment on PRs and approve before merging
- Set up branch protections
- Make requested changes on PRs before merging
Expectations for giving and receiving feedback:
Come from a caring place. Be open.
Day 1 Agenda:
- Set up repo
- Set up project board
Additional Notes: