Our_BattleShip_DTR.md

Pairing Project Best Practices:

What are each of our learning goals for this project? What drives us in this project?

Maria: I would like to gain a better understanding of methods and when to call methods on certain classes. In addition, I would like to get more comfortable with writing code using little reference.
Alex: I would like to improve the syntax of my methods, get a better understanding of the workflow for a paired project and develop the soft skills to work efficiently with a partner.
Common Goals: Push our understanding of the concepts (structures, git workflow, etc.) further.

What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?

We’d like to try a ping-pong type of collaboration (for example, one of us will write out a test while the other one codes the method) and work more independently once we both feel comfortable with it.

How do you communicate best? How do you appreciate receiving communication from others?

Maria: I appreciate direct feedback verbally, preferably video or in person. Also, would like to know what expectations are not being met. I am between introverted and extroverted but fall a bit more on extraversion because I am energized as opposed to drained when around other people.
Alex: I need regular exchanges in person, through Slack or Facetime and to receive constructive feedback on my work and clear indications when I did not meet expectations or when what I did or said hurt my partner’s feelings (straightforward communication). I have trouble understanding things on the spot and sometimes need time to think through other people’s code. I’m more on the introvert side of the spectrum.

How would you describe your work style?

Maria: I like to collaborate with others but also need time to think through problems on my own.
Alex: I like to work on my own with time to think and to dive into concepts.

What are each of our strengths? How can our strengths complement each other?

Maria: empathetic towards others and a team player
Alex: staying focused for a long time, studying, explaining concepts I understand
As a team: find different and possibly better ways to approach a problem by sharing ideas

What’s gone well or poorly in your previous projects?

Things that have gone well:
Maria: finishing projects and making sure others get ideas across
Alex : meeting deadlines
Things that have gone poorly:
Maria: unevenly distributed work
Alex: unproductive communication style, lack of empathy

How will we set direction and make decisions as a team?

• Set clear expectations that we can both agree on for sub-iterations of the projects.
• Prepare solutions on our own before we meet, and discuss the pros and cons of each solution.
• Agree to disagree sometimes and listen to each other’s ideas.

How will we overcome obstacles?

• Go for a walk and think about what is blocking us.
• Communicate clearly about how we feel and what bothers us.
• Frame the problems in a non-violent/non aggressive way (separating fact from emotion).
• Have a retro every other day to talk about what’s going well in our communication and what’s not.

What do you need (resources, environment, communication) to do your best work?

Maria: For resources, I look to Google, class material as well as my classmates/mentor. Also, I prefer a more quiet, less trafficked environment in order to focus better away from distractions. I like to work on my own but also have time to work with others to get a different perspective and/or gain a better understanding of material. If I feel stuck after having worked for a long stretch of time, I tend to take a break for an hour or come back to the material wish a fresh set of eyes the next day.
Alex: Quiet space at Turing (pairing stations or phone booth) and out of Turing (quiet cafe/home). I prefer to work for long stretches of time with breaks.

What scheduling restraints do you have? What are your scheduling preferences?

Maria: I prefer to not be working between 10 pm and 5 am.
Alex: I work every day from 7.45 am to 9 pm, and I try not to work on Sunday.

What is your style for giving feedback? Does anything ever hold you back from giving feedback?

Maria: I try to be direct and constructive as possible when giving feedback. Sometimes, I refrain from giving feedback if I think it might hurt the other person’s feelings.
Alex: I like to give feedback verbally but giving negative feedback can be hard.

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?

Maria:
strengths: Github flow, understanding code
areas of improvement: gain a better understanding on how to write methods that call on an object from a different class
Alex:
strengths: understanding of classes, methods, and scope, thinking logically about a problem
areas of improvement: syntax, limit test cases for testing, merge conflicts on github

How can our team help support you in improving these skills?

Maria: spend a little more time in class to discuss certain topics like we did last Thursday
Alex: material on best coding ruby practices and tips on how to write shorter methods

What tools do you want to use to manage the project?

Trello, Slack/Zoom, this DTR, Github.

How do you want the group to solve problems when members run into issues with features of the project?

Use our individual resources before discussing our problems together (unless individual resources are not available).

How do you know if a project is successful? How can we achieve that as a group?

We’ll know the project was successful if both of us understand every part of the project and if we can describe technically what the code does. Also, we’ll have succeeded if the two of us meet the goals we’ve set for ourselves at the beginning of this DTR.

How will we recognize each other's successes and celebrate them?

We’d like to pay attention to each other’s individual goals and celebrate steps towards meeting these goals with high fives, thumbs up, etc.

Any additional questions that you would like to add:

n/a