crate mod 4

# DTR: Define the Relationship

One teammate should copy and paste the *raw* markdown into a gist of your own.

### Guiding Questions to Define The Relationship:

* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
* How do you communicate best? How do you appreciate receiving communication from others?
* How would you describe your work style?
* What are each of our strengths? How can our strengths complement each other?
* What’s gone well or poorly in your previous projects?
* How will we set direction and make decisions as a team?
* What do you need (resources, environment, communication) to do your best work?
* What scheduling restraints do you have? What are your scheduling preferences?
* What is your style for giving feedback? Does anything ever hold you back from giving feedback?
* What do you identify as being your biggest strength(s) technically? Where do you feel you could use improvement in your technical skills? How can our team help support you in improving these skills?
* How do you want the group to solve problems when members run into issues with features of the project?
* How do you know if a project is successful? How can we achieve that as a group?
* How will we recognize each other's successes and celebrate them?

Any additional questions that you would like to add:


### Template for DTR Memo

Project: 2001 Mod 4 Cross Poll

Group Member Names: Olivia Webster, Megan Huggins, Ryan Camp, Margo Flewelling, Travis B

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? YES, you can still fully answer this question without knowing exactly what you're going to build.):
Megan: More seamless understanding of working with backend and get a better sense of what a real structure of what the work flow actually is.
Get more comfortable with git rebase
Travis: More well versed in technologies he's not familiar with. learn more JS, react hooks.
Ryan: Do a good job. Learn as much as he can. Learn more react and redux and hooks.
Margo: Feel comfortable coding in a new language 
Olivia: Get to know hooks more, get a really good understanding of the code base


Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Megan: good at testing. Flexible. Can code together or separately. Will follow through on separate work. 
Travis: Doesn't get frustrated with stuck points. can help us get out of rabbit holes. Also flexible. Up for coding together or working on his own. Not big groups, but pairing is good. 
Ryan: Good at reading docs, the ability to sit with something for a long time. Patient. Generally Helpful. Flexible colab style. Big groups,
pairing, or independent all fine.
Margo: Loves working with APIs. Likes to work independently first especially with a new language. Once has a solid footing
feels more comfortable pairing. 
Olivia: Communicative, feel pretty comfy with react. Flexible collab style. Prefer pairing or groups of 3. 

How we can use our strengths to overcome obstacles:
Use our strengths from our respective programs to help each other overcome obstacles. If someone is floundering we work
together to reel them back in. 
Being overly communicative with each other is super important. 
We're gonna crush it. 

What do you need to look out for, in terms of strengths/working styles coming into conflict?

Megan: not letting herself get bogged down if she runs into something she doesn't understand. Focusing on leaning on the team and
not being afraid of asking questions. 
Being intentional about divying up work and making sure no one gets left behind. 

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
Megan: likes lunches to herself, and sundays. But if need be can work on sundays. Always on slack. 
Travis: flexible. Tries to cut things off by 8pm but if it's the home stretch can be flexible on cut off.
Friday nights finish a bit early. Break after 4. 
Ryan: Pretty open. Would like to be off by 9pm mnt time at the latest. 
Margo: likes to take lunch, likes to take a little break after school. 9pm mnt time would be a good cut off. Sometimes
likes a half day on the weekends. 
Olivia: Flexible, would also like to be done by 9pm. 


What is the one hour/day that each teammate has on their calendar for personal study/practice time?
morning before class.
None of us want to get too bogged down in the project so that we can do networking. 
1 hour before class, one hour after lunch. 
Looser response time after school hours, maybe.

Growth Expectations (areas for desired improvement):
Megan: Want to delve deeper into actual creating with redux, hooks, work flow. 
Travis: Would like to get better at look at where someone is going with a piece of functionality already written and then build
on that without feeling like you're messing up original code.
Ryan: Effectively anayze and implement new code. utilizing what is already there and be able to build on it. 
Margo: Feeling more comfortable with express and node 
Olivia: Feeling more comfortable diving into existing code and implementing new features. Either learn redux or learn hooks.

Expectations for giving and receiving feedback:

Megan: don't be a jerk. Understanding that we're all learning different things and help each other without being frustrated.
Travis: Specific, actionable and kind. Nothing vague. Something substantial.
Ryan: if he's coming across as too direct or abrasive just let him know and he will adjust his behavior.
Margo: struggles giving constructive feedback. Wants to work on expressing feelings before it boils over. 
Olivia: direct and kind and specific.