What are each of our learning goals for this project? What drives us in this project?
- Our goal is to learn and understand as much as possible about Promises and get better at testing.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- At the beginning we will work together more and towards the end start dividing and conquering alone.
- Leave the dungeon.
How do you communicate best? How do you appreciate receiving communication from others?
- By slack and/ or in person
Project: Swapi-Trivia Group Member Names: Eric Meldrum & Consuelo Sierra Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
- Our goal is to learn and understand as much as possible about Promises and get better at testing.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- At the beginning we will work together more and towards the end start dividing and conquering alone.
- Leave the dungeon.
- Eric’s strengths: flexibility; makes a lot of progress once we have some momentum (getting started is challenging)
- Consuelo’s strengths: Flexible as well, pretty good at communication, when I know what I’m doing, I’m good at progress.
How we can use our strengths to overcome obstacles:
- Get help early to get a strong start (from Spam, et. al.)
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- Try to be out of here by 6:00 every day; no real scheduling constraints other than Eric’s kinda-long commute
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- constant!
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- Eric would like to get more practice with React so it comes more like second-nature, and to create a really good UI.
- Consuelo wants to get better at testing.
Workload Expectations (What features do we each want to work on?):
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Lots of small commits with detailed commit messages
- Every time one person pushes code, immediately notify the other person and create a PR. Leave detailed feedback on the PR before merging.
Expectations for giving and receiving feedback:
- Be honest. If one person doesn’t understand something, or know what to do, or doesn’t like the way something is, they need to say something.
Project management tools we will use (GitHub projects or Trello are popular tools):
- GitHub Projects & Issues