Skip to content

Instantly share code, notes, and snippets.

@QuinnrElder
Last active June 8, 2022 21:40
Show Gist options
  • Save QuinnrElder/ef57e3b6c1590af7cdfe214a372ef7a0 to your computer and use it in GitHub Desktop.
Save QuinnrElder/ef57e3b6c1590af7cdfe214a372ef7a0 to your computer and use it in GitHub Desktop.
DTR ~ Define The Relationship

DTR: Guiding Questions to Define The Relationship:

What is your collaboration style?

Quinn:

  • I love to try and figure things out on my own. At the same time I love to pair on new things that others are also interested in learning.

What are my strengths? How can my strengths complement the team?

Quinn:

  • Motivated ~ I am always willing to put in the work.
  • Communication ~ I have a tendency to over communicate and ask lots of questions.
  • I believe that if we take care of the small things the big things tend to work themselves out.

What are my weaknesses?

Quinn:

  • Spelling
  • I can get sucked into the weeds and over think things easily.
  • Have a hard time remembering to timebox things in the moment.
  • I can be a scatter brain at times if I dont stay organized.

What do you need (resources, environment, communication) to do your best work?

Quinn:

  • Strong communication with teammates.
  • The more detail in tickets the better!
  • I like to have an enviorment where it is safe to fail.
  • I like when I feel like I can reach out to teamates to pair around a problem.
  • I also may ask the same question more than once lol

How do you like to recieve feedback?

Quinn:

  • I tend to like to recive things in a blunt and head first approach. If someone was to try and beat around the bush when attempting to give feedback to spare feelings, I can get lost in what is actually trying to be conveyed. Blunt and honest is how I learn from feedback.

Where do you want to improve your technical skills?

Quinn:

  • GraphQL / SQL
  • Cypress testing
  • Contentful ~ this is the first project I have used a tool like this so as much insite and hands on would be great.
  • StoryBook ~ this is the first project I have used a tool like this so as much insite and hands on would be great.
  • CSS / SCSS / BEM / ITCSS ~ if applicable in this project

How do you know if a project is successful? How can we achieve that as a group?

Quinn:

  • I would consider a "success" in this project if we are first able to make the client happy! It should be our goal to stay inline with the timeline of the project. If each team member was able to learn/practice technical skills. I would also consider us growing together as Sparkboxer's a major win! The more that we can work together the easier future goals and projects will be.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment