Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- DTR: JT & PB Mentorship
- Use this template to when conducting DTR with your project partners. It's recommended that you copy/paste this template into your own gist each time you conduct a DTR to take notes on the conversation.
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- J: 3,000 ft view and zero in.
- P: Conceptual. Vague initially. Rather ask questions.
- How do you communicate best? How do you appreciate receiving communication from others?
- J: Specific, actionable and kind
- P: Specific. Opportunities to improve, detailed oriented. Slack/in person. Brutally honest.
- How would you describe your work style?
- J:
- P:
- What are your strengths? How can our strengths complement each other?
- J: Testing
- H: Rails, DB Schema and design - rebase - git issues
- T: React Native
- What’s gone well or poorly in your previous projects?
- How will we set direction and make decisions as a team?
- How will we overcome obstacles?
- What do you need (resources, environment, communication) to do your best work?
- What scheduling restraints do you have? What are your scheduling preferences?
- J: Evenings, after 6 pm or Saturdays
- P: Evenings.
- Tuesdays @ 6 pm. At Turing. d
- Any additional questions that you would like to add:
- Goals and expectations:
- P: AI, machine learning
- Python
- Machine Learning Posse
- Team strengths:
- How to overcome obstacles:
- P: Can internalize or may need to need to go to specifics or take a break.
- J: Ask about where he's at?
- Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
- J: Slack available: 8 am - 6 pm. Within 2 hours, with expectstion.
- Expectations for giving and receiving feedback:
- Call out when you are done with test or code and are waiting to do something.
- PR comments
- Slack call out
- Additional Notes:
- dMeeting once a week, sat as extra day when needed. Screen share when needed. Always ask questions.
Add Comment
Please, Sign In to add comment