Skip to content

Instantly share code, notes, and snippets.

@JF-Lalonde
Last active June 5, 2017 14:58
Show Gist options
  • Save JF-Lalonde/5d03febbee6954c67e39801c1a43a369 to your computer and use it in GitHub Desktop.
Save JF-Lalonde/5d03febbee6954c67e39801c1a43a369 to your computer and use it in GitHub Desktop.
Black Thursday DTR

Guiding Questions to Define The Relationship:

What are your learning goals for this project?

  • To learn more than we did at the beginning. Learn how to handle CSV files, and to become better at paired projects.

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

  • Pair programming is the way to go, at least to start off.
  • Driver/navigator until/if we feel comfortable enough to break off into a divide/conquer approach.

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

  • Talking one-on-one, slack is good to communicate outside of that. Be frank and direct with each other, treat each other with respect.

How would you describe your work style?

  • "Get it done", better working with others, but can work by yourself if needed. Getting to vocalize thoughts can be a big help. Try to stick to a schedule.

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

  • Spending the time together to get the work done. Bringing different strenghts to the project and being open to the other person's ideas.

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

  • Being at Turing or just meeting up somewhere that isn't home to get away from distractions. Reaching out to Mod 3 students if we feel we've hit a wall.
  • Maitaining good communication is crucial.

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

  • Randy: Sometimes 6pm, Randy will check today (Tues 5/30) and get back to JF about a schedule. JF: Timebox to 9pm at the latest on weekdays.
  • Working on weekends: we could both come in around 9am and leave around 6pm, but we're both flexible. JF's house is open if we want to let the dogs play while we work.

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

  • Being direct without coming off as confrontational. Just being honest with each other and listening without hangups.

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?

  • Randy: Testing is a weakness. Strength -- try to rely on what we know and build from it. Classes and methods, and instance variables.
  • JF: Testing is a weakness too, hard to do TDD. Whiteboarding is a strenght, planning before coding.
  • We both want to place a strong effort on implementing TDD.

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

  • Program like god. Try to adopt a top-down methodology.

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

  • Present the problem as soon as it occurs. Talk through ideas for solutions to each other, then classmates, then mentors.

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

  • If we both walk away with a sense of accomplishment. Focus on learning rather than just getting it completed.
  • Feel like we asked for help when we needed it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment