Use this template 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 are each of our learning goals for this project? What drives us in this project?
-
Greyson's goals
- formating better code
- JS - Html pairing
- understanding collaborative git workflow
-
Orlando's
- Solid understanding of fuctions, loops, arrays, methods
- cosole.log everything and understand it
- collaborative git workflow
- Gain confidence about my own work and capabilities
- I want to practice rubber ducking and pseudo coding
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- Greyson's style
- I prefer divide and conquer and want to get better at paired programming.
- trying to get better at giving hint (driving-navigator)
- Shared learning
- Orlando's style
- divide and conquer
- I need ot know what is my end goal(clear)
- flexible
- knowing my own need and other people's needs
- How do you communicate best? How do you appreciate receiving communication from others?
- Greyson's communictation styles
- Direct verbal communicator / slack calls
- Scheduling in writting - planning ahead
- When not on video/ slack is the best way of communication.
- Not supper emotive communicator
- Orlando's styles
- calls better way of communications
- address issues ASAP
- coding problems: Slack/ Tuple
- How would you describe your work style?
- Greyson's work styles
- Hunker down- tunnel vission: needs to improve on taking poms.
- Detailed oriented
- Orlando's work styles
- Detailed oriented
- Get-it done type of guy: trying to change and better understand
- What are each of our strengths? How can our strengths complement each other?
- Greyson's strengths
- Team member
- Supportive attitude
- Detailed orientation
- stress managment
- Orlando's strengths
- Detailed oriented
- Good listener
- Supportive
- What’s gone well or poorly in your previous projects?
- Greyson
- Open to ideas and other interpretation of my own ideas
- Not being aware of my team's emotional state
- Maintaning a level head in stressful situation
- Orlando
- Lack of communication
- Not stating my needs and wants.
- Not listening
- celebrate small accomplishments
- Sharing the spotlight with teammates
- How will we set direction and make decisions as a team?
- Greyson
- using psuedocode to map out the project
- when we diagree about decisions, we use research to decide which option to go with
- Orlando
- I'd like ot be clear about our goals and intentions for the project. My goal is to understand my pieces of code and best coding practices.
- using strategies that we both understand and can if needed teach the other.
- How will we overcome obstacles?
- Greyson
- Using the console to explore individual lines of code.
- Personally, I need to be quicker to use reference materials like MDM.
- Orlando
- By creating a work strategy that I can use to hold myself accountable and deliver my work with out compromising my learning process. I want to being able to understand what I am doing before moving forward.
- By practicing my learning methods.
- Talk about the problem before trying to solve it. "rubber ducking"
- What do you need (resources, environment, communication) to do your best work?
- Greyson
- Environment is HUGELY important to me (luckily I'm at home)
- Orlando
- Communication
- Time away from the computer, POMs
- Flexibility with schedules, communication when schedules need to adjust, being accountable and making up for time missed
- What scheduling restraints do you have? What are your scheduling preferences?
- Greyson
- Preference: an hour break after class, and then get into it, try to finish by 7 or 8
- Orlando
- No restraints, try to finish by 9
- Available 5-9
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- Greyson
- I try to avoid world like "I like that," or "I don't like that."
- When giving and recieving feedback I think it's really important to communicate impressions of the work to the author, and that these impressions can be hugely informative about what's being communicated in the work.
- Orlando
- I am not a direct person and giving feedback is not an easy process
- I value feedback and how it promotes a working environment and allows forward movement
- 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?
-
Greyson
- I've got a pretty good grasp on arrays and I think I'm getting good at point specific data where ever it's nested and mutating it
- my formatting needs work, and I need to edit and refactor more
-
Orlando
- Good understanding of data types and how array and string methods work
- Getting good at using the console log
- could use improvement on for loops and how to use the Return statement in combination with for loops.
- What tools do you want to use to manage the project?
- Greyson
- I want more familiarity with Atom.
- I need to get familiar rep.l, but I don't want to >.<
- Orlando
- Tuple / Slack
- Run.js
- How do you want the group to solve problems when members run into issues with features of the project?
- Greyson
- I also want to break it into smaller pieces
- Drawing diagrams helps a lot
- Orlando
- I like to break it into smaller pieces
- Console log everything
- Write on code on paper for a different perspective
- How do you know if a project is successful? How can we achieve that as a group?
- Greyson
- Understanding code and developing strategies for working on code collabratively
- Orlando
- It'll be successful if I learn the git workflow and if I understand what the code is doing
- How will we recognize each other's successes and celebrate them?
- Greyson
- I'm a big fan of high-fives, but I think celebration will be pretty verbal via zoom.
- I'll be the first guy to shout hooray, and it's not insincere, take me seriously, you rock.
- Orlando
- Let's have a beer.
- G: "I'm into beer too."
- Set aside 10 minutes to look back at what we've accomplished and talk about it regularly (with flexibility, and as a learning strategy)
Any additional questions that you would like to add:
- Is there anything we can do to support each other's growth?
- Greyson
- Nudging me to be mindful and empathetic in code.
- Orlando
- Patience, a feeling of support
- What does remote focus look like for you? (headphones, distractions minimized (tv, family stuff, etc), video on)
- Greyson
- I'll put on headphones when I need them, sometimes I'll be interupted by a dog, but mostly I'm in a distraction free space! Lucky me
- Orlando
- Phone, notifications, videos on the internet can be very distracting.
- When working from the same place where you live, life can get in the way. What are some potential life things that could interfere with your ability to focus, and what plan can we come up with to approach those issues? (Examples: my kids, my dog, my partner, etc.)
- Greyson & Orlando Making time for our partners is important. We want to try to stay ahead of work and be done with our sessions earlier in the evenings.
- If we encounter issues such as power outages, Zoom difficulties, or bad wifi, what backup plans can we have in place? (This could have answers like asking a neighbor to borrow wifi, using cellphone hotspot for internet, switching to slack or skype.
- We've traded numbers. Greyson has a hotspot that he can use. We'll text to communicate if all fails.
- Pomodoro breaks are especially important for remote work and doubly so for quarantine. What should our Pom cadence look like? How will hold ourselves accountable?
- We're going to download the app that Scott recommended and make use of it in our sessions.
- Quarantine is tough, so it’s important to make note of our mental/emotional state when working with others. How can we make space to check in on each other’s well being, in addition to the work that needs to be done?
- Start meetings with personal check-ins and small talk
Project: RomCom
Group Member Names: Greyson and Orlando
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
- We both want to increase our understanding of the code and work on technical growth skills recommended to us by the instructors after the last project. We've agreed that having check-ins at the end of the session to briefly point at what we've accomplished during that day alone will go a long way in helping us measure our success.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- We both always want to help the team. We want to collaborate in ways that are helpful and create the sense that we are accomplishing something. We've discussed the discomfort of giving feedback, but have also both expressed areas where we'd like to grow and identified aspects of the ways we communicate so that we can better give eachother feedback and help eachother learn the content.
How we can use our strengths to overcome obstacles:
- We're both detail orientated and are going into the project with an expectation of being thorough and coding for understanding first. We've agreed to communicate when we need solo time to practice and study before bringing new ideas back to the group.
Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
- We've communicated that we'll be online between the hours of 5-8 and available for group or solo work depending on what's needed.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):
- We'd like to be casual but focused and time efficient in our communications. We'd like to try to at least touch base daily. We both have slack on our phones and have decided it'll be our primary point of reaching out, and we'll use Tuple. Decisions are going to be based on what we both understand and can execute.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- Greyson wants to improve on refactoring and formatting, as well empathetic code. Orlando hopes to get better at arrays, functions, methods, and objects, and rubberducking and pseudocoding. We both would like to work on collabrative git workflow.
Workload Expectations (What features do we each want to work on?):
- We're both really excited about using JS in tandem with HTML.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Being intentional with splitting the driver/navigator rolls and sharing problem-solving techniques.
Pomodoro Break Schedule:
25-5-25-5-25-15
Expectations for giving and receiving feedback:
- We're going to be understand of discomfort and try to use it as an oppurtunity to give each hints and lead eachother to conclusions. Feedback isn't a tool to put anybody or their ideas down, but rather a mode of communication which allows us to understand how our work is being percieved by other people.
Additional Remote Considerations:
- We've got to respect the things outside of eachother's control, but we've also got to take responsibility and communicate with each other about what's happening in our lives. We'd like to encourage each other to practice self-care.
Project management tools we will use (GitHub projects or Trello are popular tools):
- GitHub, Slack, Tuple, Atom, Run.js
Day 1 Agenda:
- Take some thorough time with the ReadMe. Make some day-by-day goals. Work through some Psuedocode.
Additional Notes: