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?):
- We hope to collectively acheive a thorough understanding of every line of code written, and feel this will be a strong marker of the project's success.
- We look forward to gauging our growth together over the course of the project as a representation of the power in a growth mindset.
- We would like to acheive as much completion of the highest iterations we can, conscious of prioritzing the quality of our code and collaboration through each iteration along the way.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Our respective thinking styles of 'Intuitive-Conceptual' and 'Imaginative-Inspirational' lead us to expect we'll come together easily around a high-level understanding of the concepts, and anticipate applying a more intentional focus to the details of syntax and construction of our code.
- We've each reflected and agreed upon the benefits of meeting together in person to work through challenges on the first project, and anticipate that doing so again will prove valuable for this and future projects as well - specifically for the opportunity to collaborate more immediately and directly.
How we can use our strengths to overcome obstacles:
- Ben's enthusiasm and adaptability are great connective characteristics to level our collective mindset when encountering challenges, and may be focused through Allison's tendency to strategize, synthesize and associate cause & effect.
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):
- We've discussed our schedules and agreed that we'll be generally open and flexible, both prioritizing our learning here and the consideration of our respective partners - commitments/ any conflicts at this stage generally being around other scheduled Turing classes or meetings. Allison has a standing meeting with her mentor on Monday afternoons and Ben with his on Fridays, so we have discussed the possibility of collaborating around these times specifically for the code reviews and persistent questions.
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?):
- Daily communication will be key, and likely increase as we get further into the project. We've exchanged numbers, which will likely be the easiest form of communication when we are not at our computers. We've used Tuple to collaborate on this DTR, and would like to work together in person as we are able.
- We've connected over a shared appreciation for building a considerate and deeper relationship - really getting to know each other and already appreciating each other's strengths and contributions. Ben is especially attentive to checking in, and we have found an early comfort in openness with each other which should serve us well in communicating throughout the project.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- We've recognized feeling like we are in a similar place after our experiences in (and chances to talk through) the first solo project. While neither of us come from a previous technical background, we share a drive to grow together and push each other in our progress to fully understand the concepts as we learn and apply them.
Workload Expectations (What features do we each want to work on?):
- Starting from a similar place and each wanting to gain a well-rounded understanding, we've considered that we may work more closely in collaboration than employing much of a 'divide-and-conquer' approach - we may adjust this as we get deeper into the project, but would like to start with enough alignment to ensure we both feel like we are solidly on the same page.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- We'd both like to practice and become more comforatable/confident in the collaborative git-to-GitHub workflow, so working through the actual code more synergistically and being able to discuss even this remote push-pull process more directly as we execute it may be particularly helpful for our team to most fully accomplish our learning goals. We want to support each other in becoming the best developers possible, and will emphasize the professional benchmarks of refined code, atomic commits, and intentionality in our code reviews and commits.
Pomodoro Break Schedule:
- Having both found value in practicing with a pomodoro timer for self-regulation, we've agreed on a base of about 35min for working time before each pause to reset - granting flexibility as necessary ("rigid state of flexibility").
Expectations for giving and receiving feedback:
- We've set the norm for our communication to be considerate and well-informed by each other's intentions and thought processes going into the work, before proceeding to discuss alternatives or critical edits. Respect and mutual gratitude will be our guides!
Additional Remote Considerations:
- While we are remote, we've practiced with various options including zoom, slack calls and now Tuple - and are comfortable sharing our screens, and videos to work remotely as humans. We may both be granted access to the Turing basement, and if so may collaborate there, or in either of our respective home outdoor spaces. With each other's phone numbers and openness to frequent communication, we won't need to rely soley on a wi-fi connection to communicate if we do need to arrange alternate locations.
Project management tools we will use (GitHub projects or Trello are popular tools):
- Allison's note-taking style and inclination to break down steps in planning will help focus our approach to managing this project and staying organized as a team. We will use GitHub most extensively and may employ other tools as recommended &/or needed.
Day 1 Agenda:
- We want to come back with a fresher set of eyes to go over the code in all of the provided files (index.html, styles.css, data.js, Cover.js, main.js), making sure that we have a really solid foundational understanding from which to build our approach and begin our technical work.
- With this greater understanding of the project ahead of us, we will have a more robust dscussion of our intended timelines, and how best to implement them toward a balance of project completion and quality.
- We want to check in with a repeator, mentor or instructor to be sure that the inital GitHub Pages deployment was successful, so as not to have started from a small mistake we'll suffer later.
- Dig into 'Iteration 0', start pseudocoding and researching the less familiar concepts we can anticipate needing to use.
Additional Notes:
- We're excited to learn together, collaborate and uplift each other through the course of this project!