Skip to content

Instantly share code, notes, and snippets.

@allindow

allindow/tommasina_dtr.markdown

Last active June 16, 2016 06:12
Show Gist options
  • Save allindow/25eb4bd1f54f5e6fab7d6e1e270618fb to your computer and use it in GitHub Desktop.
Save allindow/25eb4bd1f54f5e6fab7d6e1e270618fb to your computer and use it in GitHub Desktop.
Download ZIP
Raw
tommasina_dtr.markdown

These are notes from Tommasina and my DTR meeting before we began Headcount.

  • Learning goals for the project: T wants to sticking with TDD, even when we don't know what we're looking for, A too; A's goal getting comfortable with parsing through CSV

  • Collaboration styles: divide and conquering, one person do merge and pull requests,

  • Communication preferences: Angela is comfortable with anything, slack, last projects used screenhero, talked on the phone

  • Work style: T likes to work slowly and methodically, have to understand. Angela is about efficiency, doesn't have a lot of time to not be efficient, thinks about it when doing other things

  • Last project: worked well: worked efficiently with Y, they weren't at Turing as much as others, but still got work done. split up when a concept that neither one knew what was going on, which helped (but not necessary for that project), what went poorly: time sucks with a concept that we weren't taught about and took a long time to figure out, tried to figure out why headers weren't working, frustrating to spend so much time on one problem -For best work: needs clarity about what's going on, when we're working, what we're working on

  • Scheduling restraints- T wants to be in bed by 10, A can't stay every late every day, but could stay up to 6 every day except Thursday, could screenhero around 7:30 and could be available most of the night

  • read through all files, CSV files, sketch an idea out of how classes are working, to feel like I understand the spec

  • Schedule: tomorrow plan on staying until 6 and then Wednesday, we have to see, Thursday screenhero 7:30, Saturday the rest of the day could work, Sunday could do screenhero in late afternoon,

  • What holds you back from feedback? A can give feedback no problem, T nervous about holding us up,

  • What are your strengths? A good at implementing ideas, can figure out a way to do it, good googler, T motivated

  • What could use improvement? T wants to be more confident at coding, keeping our current goal in mind, A to encourage her to say it aloud; for A, she wants to remember to keep things to a single responsibility, to help, T could use triple checker attitude to remind us to refactor into multiple methods

  • We'll try using trello to manage our responsibilities

@hakamibrahim
Copy link

Hey can I ask you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment