DTR_hang_in_there.md

Project: Hang in There

• Group Member Names:

  Tim Keresey and Orlando Murcio

• Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?): Tim

  • Learning to actually implement code concepts into a real product.
  • Establish a good group project workflow.
  • Write good DRY code
  • Get better idea of my strengths Orlando
  • have a beter understanding of DOM manipulation
  • create a clear timeline fo deliverables and ask for help when needed
  • ask for code review from a Mentor
  • write DRY code
  • make use of the driver-navigator style

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

  Tim

  • Good at organizing tasks in a team setting.
  • Good articulation of concepts.
  • Not a very big ego. Orlando
  • strong communication skills
  • I like to be clear when dividing and conquer is requires but I prefer a driver-navigator style.
  • shared knowledge

• How we can use our strengths to overcome obstacles:

  • Stay honest about levels of understanding as we go along.
  • make use of all ways of communication to talk about the project but also talk about better ways to support each other.
  • Planning is really important because it gives me sctructure and I know what are the things that need more attention.
  • have 5 min at the end of the session to talk about our current project's status and overall goals

• Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):

  • 2 hours every evening, Wed. to Fri., 5-7; Sat. and Sun. 8-12; Mon. TBD

• Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):

  • slack 9am - 8pm. Tuple for work time. Exchange phone numbers for just in case situatuions.

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

  Tim

  • DOM manipulation & event listeners
  • time managment and efficiency
  • writting pseudocode

  Orlando

  • DOM manipulation & event listeners
  • DRY javaScript
  • getting betterat taking pom and breaks
  • time managment
  • practice better cnaming convention
  • rubber duccking

• Workload Expectations (What features do we each want to work on?): Tim

  • be consistent with the workload
  • even split of workload between the memebers of the team Orlando
  • one iteration a day
  • usinng a list-making application for work managment like Notion
  • for the two of us to work on a project together

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

  • atomic commits are important
  • even work distribution with pull request
  • Git and GitHub fluency
  • Code review by a mentor

• Pomodoro Break Schedule:

  • every 35 minutes for a POM

• Expectations for giving and receiving feedback:

  • honest at giving feedback
  • remain open to new ideas and ways of writing code

• Additional Remote Considerations:

  • dog barking from time to time

• Project management tools we will use (GitHub projects or Trello are popular tools):

  • notion, GitHub projects

• Day 1 Agenda:

  • Review readme file for iteration 1

• Additional Notes: