Skip to content

Instantly share code, notes, and snippets.

@sertmer

sertmer/pallet-picker-dtr.md

Last active February 4, 2020 00:10
Show Gist options
  • Save sertmer/b6e15124405a793eef5b5265d6690eb8 to your computer and use it in GitHub Desktop.
Save sertmer/b6e15124405a793eef5b5265d6690eb8 to your computer and use it in GitHub Desktop.
Download ZIP
James Miller and Scott Ertmer DTR
Raw
pallet-picker-dtr.md

Group Member Names:

  • James Miller and Scott Ertmer

Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?)

  • Scott: Progress over past abilities
  • James: I would like to better solidify my knowledge of the backend side of things, while also maintaining/improving my skills in TDD, Git Workflow, refactoring, etc. I think we will know that we were successful if we feel we did that the best of our abilities and feel good about meeting all the requirements of the project. If possible we may want to try and incorporate cool graphical libraries like Three JS and D5 (?).

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

  • Scott: Direct and quick to discuss pros and cons.
  • James: My strengths are in being able to be a chameleon of sorts, I work well according to the strength and style of my partner(s). Essentially, I am flexible, and if need be can work through tough problems. Also communicates often! I think we are two people who are very intent on becoming better at their craft. I am excited to work with Scott as he is an artist, and I think he will have some great insights into what would be most useful for a “Persona” who is using our software. We are a couple of bad ass motherfuckers

How we can use our strengths to overcome obstacles:

  • Scott: discuss things as they come up, work when it's work time, rest when it's not.
  • James: We will be able to overcome obstacles by relying on our abilities to look at a problem and consider how to implement it. If we get stuck we can lean on each other, throwing ideas back and forth, to try and figure out a solution. We also both can be dedicated to solving a problem, no matter how much time we have spent on it, but are self-aware of this tendency and so will remind each other that it is time to take a break or work on a different problem.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

  • Scott: stand up before class (8:30) if that works for James. Usually turning off my computer around 9PM
  • James: I am available whenever, wherever, and can do whatever is easiest / best for my partner. Weekdays/Weekends, I have no other commitments

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

  • Scott: Slack at any time, but don't expect response after 9.
  • James: I think it is a good idea that we communicate daily, to check in on the progress we are making, celebrate our wins, and just enjoy the process of developing software. Tend to feel that overcommunication is better than under communication. So if we knock out a User Story, or open a PR, just let the other know, and then communicate what bit of functionality/feature we plan to take on next.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

  • Scott: Getting more comfortable with connecting front and back end.
  • James: Would be cool to really try and implement the lesson from today on crafting very detailed and thorough User Stories, and have each User story correspond to a branch / PR. Think if we spend a lot of time crafting those we could get a feel for how we can predict the various milestones we will hit over Day 2, Day 3, Day 4 etc. Personally would love the chance to get my hands dirty with some Three.js / D5(?) and I know Scott is too, so that would be an awesome growth expectation. But that should be the reward we give ourselves after we have met all the requirements of the project and done so to a level of proficiency.

Workload Expectations (How are we going to make sure we contribute equally?):

  • Scott: Keeping an eye on contributions (lines added / commits)

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

  • Scott: GH projects, verbose PR's, not merging your own pull req's, and daily linting. Atomic commits. Cleaning out logs and pseudo before opening a PR.
  • James: Definitely want to use the PR template that we have been using, and feel like we should do our best to do a code review and leave comments where applicable. May be another good opportunity to becoming more familiar with Git Rebase as that may be a necessary/beneficial skill to have for the Cross-Poll projects

Expectations for giving and receiving feedback:

  • Scott: Be direct, kind and timely. Nothing more useless than feedback after the fact!
  • James: Actionable, Honest, Kind. Be positive and constructive, and if there are disagreements, do our best to craft a message from a position of understanding and kindness.

Project management tools we will use (GitHub Projects and Trello are popular tools):

  • GH projects.

Other Notes:

  • Scott's migraines - will do everything I can to prevent them, and will communicate as soon as I know. Might miss a day or two, but not super likely.
  • James: Day 1 Agenda: Setup Repo, Go over Project Spec, start up Project Board and crafting user stories, and if we are feeling extra feisty maybe start trying to implement some?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment