Skip to content

Latest commit

 

History

History
48 lines (39 loc) · 2.7 KB

dtr.md

File metadata and controls

48 lines (39 loc) · 2.7 KB
Raw

Defining The Relationship

Expectations?

  • Kris: On a good trajectory, would like to clearly define his strengths, would like to work more with the cart, would like to feel more uncomfortable when tackling a task.
  • Zack: Would like to be the project manager(needs more experience with leadership), keep sharpening general skills.
  • Chris: Would like to fully understand new layers that will be added to the project.
  • Karina: I would like to test JavaScript. Time management.

Availability?

  • Kris: Mornings, would like to be home by 9.
  • Zack: No responsibilities outside of Turing, available always, prefers not the mornings, probably going to leave by wrap up on a couple of days.
  • Chris: No conflicts with home, would like to be home by 9, usually runs in the morning but also willing to work really early. Leaving on Thursday-Sunday for sister's wedding, happy to work remotely.
  • Karina: Do not prefer mornings, Wednesday might be conflict, would like to be home by 9.

Communication?

  • Kris: Slack is good way to reach him, clear commit messages, enjoys waffle.
  • Zach: Slack is great way to contact him.
  • Chris: Slack is great.
  • Karina: Slack is good, feel free to mention any things I could work on.

Strengths?

  • Kris: Comfortable testing, comfortable with authentication and authorization.
  • Zack: Good at catching syntax errors, testing is fun, has sendgrid.
  • Chris: Feels adequate at everything learned in mod 2.
  • Karina: TDD, pairing is nice, front-end, Oauth.

Work on?

  • Kris: JavaScript, pushing logic down the stack.
  • Zack: Styling, JavaScript, pushing logic down the stack.
  • Chris: Waffle, more commenting on pull requests, team work-flow.
  • Karina: Time Management, consistent on clean code.

Features?

  • Kris: Twitter Oauth, maybe more.
  • Zack: Tweet from site.
  • Chris: Twitter.
  • Karina: Mapping, vertical farms.

Git Workflow?

Development branch, master is EXCLUSIVELY used for production ready things. Small pull requests into branch. Local dev branch per person. Really good commit messages. Reviewing code before merging and commenting, don't merge your own pull request. Slack when you've made a pull request. Double check that all tests are passing before you open a pull request. Write it in your pull request that all tests are passing. (or needs code review because they are not.). Keep commits and branches small.

Personal work/communication style?

  • Kris: enjoys pairing, open to suggestions.
  • Zach: enjoys working together in same space, call him out on things.
  • Chris: enjoys active feedback when driving, prefers pairs of two. Needs a break every two hours or so.
  • Karina: Tomatoes, walks are nice, water is nice.