leighlars/gist:d64f32a60448999d263e3d16af8b7e8d

## gistfile1.txt
Project: What's Cookin'? Pair Project Mod 2

Group Member Names: Horacio Borrego, Leigh Larson

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?):
Demonstrate comprehension and understanding of JS-- data manipulation and iterating over data. We are excited to build a program that is close to what we could design in the professional world. We will know we're successful if it works.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):
 Leigh is a maverick, pragmatic, approachable, flexible. Horacio is flexible, easy-going, and experienced in projects like this.

How we can use our strengths to overcome obstacles:
Be mindful of tone, but clear in message. Upfront, tactfully. Recognize it's about the team. Humility.

Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
Be off the computer by 8pm unless otherwise necessary. Monday mtg 5-6.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):
We'll communicate via chat on Slack, but screen share / call via Zoom. Clear in our PRs (use template) and can easily understand issues via Github.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Horacio - Solid on HTML and CSS, wants to improve on class interactions.
Leigh- Solid on refactor, JS, CSS, prototypes. I'm looking forward to using more data manipulation.

Workload Expectations (What features do we each want to work on?):
Lots of work together. Driver/navigator except minor details.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Frequent small commits, PR/code review template, walking through it together. Before commits, we do style / debugging review. Before final submission, we get an outsider's review on aesthetics.

Pomodoro Break Schedule: 30 min on / 7 min off. Whoever is not driving can keep track of time. Break for lunch and meet at 1.

Expectations for giving and receiving feedback:
On the spot. Open-minded, available. It's not personal. Assume positive intent first. Tactful. Frequent.

Additional Remote Considerations:
Solid internet connection.

Project management tools we will use (GitHub projects or Trello are popular tools):
Github projects.

Day 1 Agenda:
Set-up. Read through spec, rubric, and README. Project board, plan: class structure, wireframe HTML, CSS using either screenshot mark up tool, or drawing it out ourselves.

Additional Notes: excited to crush it!!!!!!
	Project: What's Cookin'? Pair Project Mod 2

	Group Member Names: Horacio Borrego, Leigh Larson

	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?):
	Demonstrate comprehension and understanding of JS-- data manipulation and iterating over data. We are excited to build a program that is close to what we could design in the professional world. We will know we're successful if it works.

	Team strengths & collaboration styles (consider discussing your Pairin qualities here):
	Leigh is a maverick, pragmatic, approachable, flexible. Horacio is flexible, easy-going, and experienced in projects like this.

	How we can use our strengths to overcome obstacles:
	Be mindful of tone, but clear in message. Upfront, tactfully. Recognize it's about the team. Humility.

	Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
	Be off the computer by 8pm unless otherwise necessary. Monday mtg 5-6.

	Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):
	We'll communicate via chat on Slack, but screen share / call via Zoom. Clear in our PRs (use template) and can easily understand issues via Github.

	Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
	Horacio - Solid on HTML and CSS, wants to improve on class interactions.
	Leigh- Solid on refactor, JS, CSS, prototypes. I'm looking forward to using more data manipulation.

	Workload Expectations (What features do we each want to work on?):
	Lots of work together. Driver/navigator except minor details.

	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
	Frequent small commits, PR/code review template, walking through it together. Before commits, we do style / debugging review. Before final submission, we get an outsider's review on aesthetics.

	Pomodoro Break Schedule: 30 min on / 7 min off. Whoever is not driving can keep track of time. Break for lunch and meet at 1.

	Expectations for giving and receiving feedback:
	On the spot. Open-minded, available. It's not personal. Assume positive intent first. Tactful. Frequent.

	Additional Remote Considerations:
	Solid internet connection.

	Project management tools we will use (GitHub projects or Trello are popular tools):
	Github projects.

	Day 1 Agenda:
	Set-up. Read through spec, rubric, and README. Project board, plan: class structure, wireframe HTML, CSS using either screenshot mark up tool, or drawing it out ourselves.

	Additional Notes: excited to crush it!!!!!!