Guest User

Untitled

a guest
Nov 17th, 2018
118
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.92 KB | None | 0 0
  1. DTR: JT & PB Mentorship
  2.  
  3. 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.
  4.  
  5. What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
  6. J: 3,000 ft view and zero in.
  7. P: Conceptual. Vague initially. Rather ask questions.
  8.  
  9. How do you communicate best? How do you appreciate receiving communication from others?
  10. J: Specific, actionable and kind
  11. P: Specific. Opportunities to improve, detailed oriented. Slack/in person. Brutally honest.
  12.  
  13.  
  14. How would you describe your work style?
  15. J:
  16. P:
  17.  
  18. What are your strengths? How can our strengths complement each other?
  19. J: Testing
  20. H: Rails, DB Schema and design - rebase - git issues
  21. T: React Native
  22.  
  23. What’s gone well or poorly in your previous projects?
  24. How will we set direction and make decisions as a team?
  25. How will we overcome obstacles?
  26.  
  27. What do you need (resources, environment, communication) to do your best work?
  28.  
  29.  
  30. What scheduling restraints do you have? What are your scheduling preferences?
  31. J: Evenings, after 6 pm or Saturdays
  32. P: Evenings.
  33. Tuesdays @ 6 pm. At Turing. d
  34.  
  35. Any additional questions that you would like to add:
  36.  
  37. Goals and expectations:
  38. P: AI, machine learning
  39. Python
  40. Machine Learning Posse
  41.  
  42. Team strengths:
  43.  
  44. How to overcome obstacles:
  45. P: Can internalize or may need to need to go to specifics or take a break.
  46. J: Ask about where he's at?
  47.  
  48.  
  49. Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
  50. J: Slack available: 8 am - 6 pm. Within 2 hours, with expectstion.
  51.  
  52. Expectations for giving and receiving feedback:
  53. Call out when you are done with test or code and are waiting to do something.
  54. PR comments
  55. Slack call out
  56.  
  57. Additional Notes:
  58. 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