cloney_island_dtr.md

Group: Nick Erhardt, Nick Gheorghita, Jesse Shipley, Brett Rivers, Mike Schutte

Guiding Questions to Define The Relationship:

• What are your learning goals for this project?

Jesse: external API's and TDD (robust) Nick G: building services (POROs) Brett: DRY DRY DRY (will be challenging due to scope of project) Nick E: pair programming with each person to learn nuances, action-cable in rails 5 (non-refresh render) Mike: Reps on OAuth, CRUD API. OO best practices.

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

Jesse: Decidedly neutral, with living situation, prefers remote. Paired division. Nick G: Neutral to both. Brett: Past experience has been 100% divide and conquer, communicate on Slack and Git. Nick E: Pair in the beginning to establish style/convention and to troubleshoot. Mike: Neutral, prefer pair in the beginning.

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

Jesse: Straightforward and direct. Nick G: ditto Brett: ditto Nick E: ditto, working on not making assumptions Mike S: ditto

• How would you describe your work style?

Jesse: Do work. Likes having a steady queue of things to do. Nick G: Prefers to front-load. Brett: Nothing different. Nick E: Nothing different. For difficult stuff, need isolation. Mike S: Same.

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

Jesse: being up front about struggles. Nick G: all good Brett: 25 minute rule Nick E: Small check-ins throughout the project. For both progress and relationship development. Mike S: Communication (detailed)

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

Jesse: communication Nick G: same Brett: same Nick E: Go for most personal form of comm first. Less misinterpretation. Mike S: same.

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

Jesse: Can get here around 8am, sometimes need to leave at 4:30. Nick G: Trying to do mornings. Turing takes priority. Brett: Latest is 6:00pm, here at 6:30am except Friday, prefers 4:30 bus. Works 5:30am-9pm Nick E: 8am arrival (pending weather), prefer to leave around 5:30 and pickup work after 7pm. Mike S: 5-7am sprint. Flexible schedule.

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

Jesse: Same as Mike Nick G: If worth saying will be said. Brett: pretty much says stuff. Nick E: Pros and cons conversation Mike S: Direct, humorous, sarcastic.

• 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?

Jesse: Strength(learn quickly (could be new tech point person)) Delta(tangential with new concepts (Mike should monitor)) Nick G: Strength(Handy with styling) Delta(weaknesses determined on the go, feeling iffy on services, testing) Brett: Strength(likes db stuff) Delta(styling) Nick E: Strength(strong TDD) Delta(overly robust testing sometimes), needs reminder about experimentation scope Mike S: Strength(css manipulation, refactoring, testing) Delta(apicurious)

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

  • Waffle
  • Slack
  • Github
  • Screenhero
  • Pomodoro system

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

  • 25 minute rule

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

Jesse: learn something new and cool Nick G: good to go Brett: no worries, get better at larger projects Nick E: touching something new (technology, approach). Portfolio piece. Mike S: Everyone can explain the code, strong OOP, portfolio ready.

Any additional questions that you would like to add:

• waffle-number-initials-describe-feature
• Closes #waffle-number in PR comment
• Tag team members in PR, members can commit individually instead of as a group all the time
• Mention open PRs in Slack channel
• Delete accepted and merged PRs
• Have set number of team views/comments on PRs before merging. (2+ members review)
• Travis CI / auto push master to Heroku on all tests passing
• SimpleCov
• CodeClimate
• Double quotes
• Test

describe Model do
  describe '.class_method' do
    it 'returns the thing' do
    end
  end
  describe '#instance_method' do
    it 'returns the thing' do
    end
  end
end

---

re-DTR

Nick E: Would like to see more planned out cards so people can grab them independently.