##DTR Memo ##Project: Night Writer ##Group Member Names: Jasmin Hudacsek, Susi Irwin
###Project Expectations: What does each group member hope to get out of this project? Goals and expectations:
- Jasmin - I’d like to establish a good paired workflow since I’ve never worked on a project like this with another person. Go teamwork! Susi - I hope to better understand enumerables and Arrays with this project. I am excited and a bit nervous for a Paired project as I have never done anything like this before using GitHub. As Jasmin says, Go teamwork!
###Schedule Expectations: When are we available to work together and individually?
- Susi has a child so mornings are better, but she has worked it out with her husband to be able to stay late a few times a week if needed. I can stay after Tuesday and Wednesday this week and will work in the mornings individually. I get back on Slack around 8pm and can work until about 10pm.
- Would be able to work together some lunches and some evenings after class. Available anytime in the evening, but plan on linking back up around 8pm.
###Communication Expectations: How and often will we communicate? How do we keep lines of communication open?
- Slack is awesome and probably first line of non-face-to-face communication. If a schedule change needs to happen, Slack should be the method of communicating that change.
###Abilities Expectations: Technical strengths and areas for desired improvement:
- Jasmin wants to get better at understanding instance variables really work and get better with hashes.
- Susi wants to focus on working with and really understands arrays and hashes.
- Both: collections in general.
###Workload Expectations: What features do we each want to work on?
- At first, we want to work together to kick off the first few steps of the project. This will allow us to get our feet wet together and understand the direction we need to take. We both are interested in mapping so we may split the workload on this one to be sure that we both get the experience.
###Workflow Expectations: Git workflow/Tools/Code Review/Reviewing Pull Requests:
- Will use Slack to let each other know about pull request and code reviews.
- Committing should be often as to not lose any work or versions. Any individual work should be completed on branches and submitted with Pull Requests.
- We need to be careful and clear on exactly what we are working on. “Hey I am working on section [insert here]. This can be done in person and on Slack if needed.
###Expectations for giving and receiving feedback:
- Open and Honest
- Upfront
- In person
- Over coffee - stepping away from the physical area
###Agenda to discuss project launch:
- Monday lunch - going to have project kickoff and create setup for project. Won’t leave school on Monday until we have at least something written down in Atom. i.e. Actual code, pseudocode, etc.
###Ideas:
- Might be using a Hash for the key/value of ABC/Braile
- Could also be a system of Arrays and enumerators
- Figure out how to numbers 1-9 match with the first letters a-i and see if we can condense that * so we aren’t writing redundant code
###Tools:
- Atom, Github, Terminal, notebooks, whiteboard, google, slack, screenhero, Google Docs
###Additional Notes: Initial feelings into this project
- Jasmin - Feeling a little nervous about my own technical skills, but I feel Susi is a great partner who’s empathetic to similar feelings and that we’ll bang out this project together!
- Susi - Pretty nervous about my technical knowledge and being able to apply what I know and what I understand to the project. Jasmin and I seem to be in the same boat on everything we discussed with similar mindsets about partner work and communication.
- Solidify due date and time for project on Monday July 11,2016