Skip to content

Instantly share code, notes, and snippets.

@AkiraBrand
Last active July 6, 2018 18:34
Show Gist options
  • Select an option

  • Save AkiraBrand/7debc9b53fe7ad27472e03ffe27f9233 to your computer and use it in GitHub Desktop.

Select an option

Save AkiraBrand/7debc9b53fe7ad27472e03ffe27f9233 to your computer and use it in GitHub Desktop.
Night Writer DTR w/ Abdullah
Guiding Questions to Define The Relationship:
What are your
learning goals for this project? What drives us in this project?
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Abdulla: Pair at beginning to define the project/responsabilites/etc and then work independent with frequent check ins
Ruth: Similar, but read alone at beginning, pair a bit to make some things, and then continue with above process.
How do you communicate best? How do you appreciate receiving communication from others?
Abdulla: Visually, in person ideally, ok with slack
Ruth: Visually, in person ideally, 1-on 1, ok with slack
How would you describe your work style?
Abdulla: Stay ahead! Aim higher than expectation, meeting is ok as long as intention is to consistently move past just bare minimum
Ruth: Front-loading to alleviate last-minute pressure
What are your strengths? How can our strengths complement each other?
Abdulla: Responsability-hold self accountable to do what say they are going to do, restorative - fixing problems, relator - building
deeper connection with someone, adaptability - great with changing things on the fly
Ruth: ideas, strategist, accumulating knowledge/things, deliberate
deliberate and adaptable will compliments
strategist and restorative will compliment - i make strategy abudlla is good at fixing issues as arising
What’s gone well or poorly in your previous projects?
Abdulla: poorly => figuring something out on his own, well => able to keep up with deadlines
Ruth: poorly => clearly phrasing the questions i'm trying to ask well => got that shit DONE, and learned a TON
How will we set direction and make decisions as a team?
Identify the scope of project, break it down into smaller and smaller things, prioritize, execute. REPEAT
Making changes to code ok, explain to each other at check in for bigger changes in direction communicate first
How will we overcome obstacles?
individual research -> each other -> peers -> mentor -> talk to teacher (loop back at each iteration to each other)
What do you need (resources, environment, communication) to do your best work?
Abdulla: communication to the max, delegation, not overlapping on thing we are working on unintentionally
Ruth: a little bit of hand holding then delegte
What scheduling restraints do you have? What are your scheduling preferences?
Abdulla: work hard until 7 pm then done. Bday party this saturday afternoon-evening. Prefer to not code after 8 pm.
Ruth: spiked energy working style. pair till 7. Prefer to take day by day, this saturday at noon has appointment.
(meet up 9 am saturday, sunday afternoon)
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
Abdulla: Suportive, almost never critical. no.
Ruth: To the point. lack of knowledge.
What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills?
Abdulla: Git, refactoring (can help Ruth with that) cleaning up code, GETTING from a to b (can help Ruth)
Ruth: Getting the hang of Git, housekeeping at same time as writing, understanding destination (b) and starting point(a) (can help Abdulla)
What tools do you want to use to manage the project?
Abdulla: lets use existing tools
Ruth: lets use existing tools
POMS. YES.
How do you want the group to solve problems when members run into issues with features of the project?
Go over spec sheet with everyone in Mod -> Communicate with each other -> Throw code into slack
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?
Learning something new and applying it!
Any additional questions that you would like to add:
no
Template for DTR Memo
Project:
Group Member Names: Ruth and Abdulla
Project Expectations: What does each group member hope to get out of this project?
Learning something new and applying it
Goals and expectations:
Tests run, Did what we needed to do with some semblance of efficiency, adhere to workflow, get to know people better and feel more comfortable
working with them
Team strengths: Complementing skills i.e. Strategic/Restorative.
How to overcome obstacles:
individual research -> each other -> peers -> mentor -> talk to teacher (loop back at each iteration to each other)
Schedule Expectations (When are we available to work together and individually?):
Abdulla: work hard until 7 pm then done. Bday party this saturday afternoon-evening. Prefer to not code after 8 pm.
Ruth: spiked energy working style. pair till 7. Prefer to take day by day, this saturday at noon has appointment.
(meet up 9 am saturday, sunday afternoon)
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
Abdulla: Visually, in person ideally, ok with slack
Ruth: Visually, in person ideally, 1-on 1, ok with slack
Abilities Expectations (Technical strengths and areas for desired improvement):
Abdulla: Git, refactoring (can help Ruth with that) cleaning up code, GETTING from a to b (can help Ruth)
areas of improvement: Problem solving, understanding and memorizing the template of classes and tests.
Ruth: Getting the hang of Git, housekeeping at same time as writing, understanding destination (b) and starting point(a) (can help Abdulla)
areas of improvement: Practice working with and accessing data-types.
Workload Expectations (What features do we each want to work on?):
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):
Expectations for giving and receiving feedback:
Abdulla: Suportive, almost never critical. no.
Ruth: To the point. lack of knowledge.
Agenda to discuss project launch:
Ideas:
Tools:
Additional Notes:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment