Template for DTR Memo
Group Member Names:
- Vee Andrade
- Scott Ertmer
- Ben Firth
What feedback did you get on FitLit today? What was your biggest takeaway?
- Vee Andrade: params and more dynamic functions, taking initiative to try to fill your gaps.
- Scott Ertmer: Refactoring functions using params to make them more dynamic, Choosing what not to show to the user
- Ben Firth : inheritance, destructuring
Goals and Expectations for the Project
- Whole group: don't be afraid to mess up - especially if we focus on atomic commits and branches. Take the initiive to fill your own gaps. LEVEL UP!!!
- get comfortable jumping into codebase we didn't create.
- performing code reviews.
- spies, maybe!
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Scott: Be direct and kind in my communication, ux, ui.
- Ben: Easy Goin' Ben, not high stressed. Jack of all trades/well rounded.
- Vee: Once your foundation is built, it is very strong. Considerate of all teammate's feelings.
How we can use our strengths to overcome obstacles:
- quick, kind communication is key to good planning and execution as well as repairing breakpoints.
- We are all approaching this a chance to try to fill our gaps, and we can rely on each other's support to do so.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- All pretty free, thursday nights a night off. weekends: One full(8 hours) one half day of work. Only come to turing one day of the weekend.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- Group dm on slack. Post on slack whenever you have an open PR. Team priority to get to those quickly. Don't expect a merge after 9pm. Group decisions:
Workload Expectations (How are we going to make sure we contribute equally?):
- Have your put in the time, reaching the 10-11 hour days working. If we focus on the code reviews, and can really speak to each other's code and take responsibilty for understanding it, we will have done our jobs.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Independent, use your resources. Trello. Code review to ask questions.
- use template for PR's Expectations for giving and receiving feedback:
- Honest, and Kind and Timely.