Skip to content

Instantly share code, notes, and snippets.

@mdflynn
Last active July 21, 2020 20:35
Show Gist options
  • Save mdflynn/29acaf9920bb08183e39bb8a8892e06c to your computer and use it in GitHub Desktop.
Save mdflynn/29acaf9920bb08183e39bb8a8892e06c to your computer and use it in GitHub Desktop.
DTR for Ideabox
What are each of our learning goals for this project? What drives us in this project?
  • A clear understanding between the data model and the DOM.
  • Create a website from scratch, a large project tying everything that we've learned so far.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
  • We all think that a paired programming approach would fit our group best. We want to be on the same call working towards that day's objective.

  • How do you communicate best? How do you appreciate receiving communication from others?

We like to do Slack and all available media (i.e. Zoom, Tuple)
  • Making sure there is enough advanced notice ahead of any scheduled events that might be missed or running late.
How would you describe your work style?
  • Collaborative, diligent, and structured. Including all POMs!
What are each of our strengths? How can our strengths complement each other?
  • Estelle - Having some prior exposure, helping lead us towards our goal. As well as Git Workflow!

  • Dennis - Willing to ask questions to any sources to find a solution.

  • Mike - Good at being positive for the team. Open availability.

Our strengths will compliment each other because we have experience, and will stay positive and reach out if we hit roadblocks.

What’s gone well or poorly in your previous projects?
  • In the past projects, there were not enough commits. Truly understanding what each line of code is doing and why it's there. We'll each individual test the site to ensure no new bugs.
How will we set direction and make decisions as a team?
  • We will have a tribunal to ensure we're all on the same page with the decisions made. We will make sure to communicate all of our ideas and decide as a team.
How will we overcome obstacles?
  • By researching concepts and asking questions to our support networks. Taking a POM to see if we can clear our minds and look at the problem from a fresh angle.
What do you need (resources, environment, communication) to do your best work?
  • Good communication and a positive environment. Breaks for self-care; dinner, drinks, and bathroom breaks.
What scheduling restraints do you have? What are your scheduling preferences?
  • Mike - None. Anytime before 9pm.

  • Estelle - Time for morning walks. Stop time 9pm

  • Dennis - Kiddos, Friday 5-8, Sunday 3-5 unavailable.

What is your style for giving feedback? Does anything ever hold you back from giving feedback?
  • Critical feedback is difficult, not wanting to disrupt group harmony. Kind and constructive feedback. Wanting to grow as a team.
What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills?
  • Mike - Getting good at JS and enjoy Flexbox. Get stronger CSS and HTML.

  • Estelle - Getting better at JS and really concise code. As well as HTML structure. Wanting to get stronger with JS, CSS, and HTML and project management.

  • Dennis - Comfortable with a bit of HTML and CSS. Can improve use of terms of art and understanding how to speak the code. And git workflow.

  • Getting a lot of practice and ensuring everyone knows why we're using that code. And to make sure we can say it in the proper way.

What tools do you want to use to manage the project?
  • GitHub, Zoom, Tuple. GitHub project board.
How do you want the group to solve problems when members run into issues with features of the project?
  • Collaboratively.
How do you know if a project is successful? How can we achieve that as a group?
  • If we all feel proud of our work. That we can speak to every line of our code. Taking ownership of our code.
How will we recognize each other's successes and celebrate them?
  • Using words of affirmation. Lifting each other up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment