Skip to content

Instantly share code, notes, and snippets.

@dietza
Last active October 22, 2020 22:29
Show Gist options
  • Save dietza/da8968b2082bdbaa1d8a47e8f51314b1 to your computer and use it in GitHub Desktop.
Save dietza/da8968b2082bdbaa1d8a47e8f51314b1 to your computer and use it in GitHub Desktop.
Refactor Tractor [FitLit] - DTR

Define The Relationship

Group Members: Allison Dietz, Bryce Jarrett, Cooper Terrones

What are each of our learning goals for this project? What drives us in this project? Understanding SASS, WebPack and the Fetch API and how to best integrate these new technologies. Wanting to learn new technologies and take a further step in our developing education.

What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?

Divide and conquer can work as long as the standards are clearly defined and working roles are agreed upon. Norms / best practices and conventions.

Appreciate pair-programming, and have experienced unsuccessful divide-and-conquer strategies.

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

Honest and straight-forward feedback - we are all here to become the best developers we can be, and help each other get there.

‘unsolicited feedback’ is hereby solicited.’

How would you describe your work style?

Emphasize consistent communication & workflow practices so that we all stay on the same page with progress of the project.

Balance between efficient progress and fully understanding why we are doing something or pursuing a certain approach.

What are each of our strengths? How can our strengths complement each other?

Coop: chill, flexible glue

Bryce: Specialist, Self-Confident, Lover of Wisdom & Knowledge, Objective/Analytical

Allison: Intuitive-Conceptual, Loyalist, Calm/Cool/&Collected, Lover of Moderation

What’s gone well or poorly in your previous projects?

Make sure to pause and refactor along the way - clean up at the ends of sessions to avoid unnecessary obstacles.

How will we set direction and make decisions as a team?

Discussion, lay out personal ideas and come to consensus on how to move forward among differing ideas.

How will we overcome obstacles?

Maintain respectful team dynamics and remember to utilize the resources available to us. Put in the time, but also take breaks as necessary.

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

Agreed upon larger blocks of time for working together as a team. Self-research to come together with further understanding of WebPack, Sass, etc

What scheduling restraints do you have? What are your scheduling preferences?

Bryce is one hour ahead (TX, central timezone) Cooper works 12-5pm Sundays

What is your style for giving feedback? Does anything ever hold you back from giving feedback?

Direct and considerate.

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?

Bryce: strengths in logic, quick processing and JavaScript

Cooper: UI, responsive design and CSS, branches

Allison: comfortable in organizing and formatting code for consistency, refactoring for clarity over reducing lines. Working on building confidence in communicating ideas.

What tools do you want to use to manage the project? Tupl, zoom, google, slack, github,screen share, reviewers/ mentors

Tuple, zoom calls, GH project board, PR template and thorough reviews (use rocks, mentors, etc)

How do you want the group to solve problems when members run into issues with features of the project?

Be communicative and transparent if running into git/workflow conflicts so that we’re all aware of the issues and able to resolve them as cleanly as possible.

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

Fulfilling functional expectations, Adherence to DRY /SRP principles, Each member fully understanding the code present, Smooth workflows, achieving a high mark on professionalism & testing

How will we recognize each other's successes and celebrate them?

Focus on big issues, ‘don’t sweat the small shit’ Don’t get too stressed/stuck - embrace the eustress

Recognize each other’s growth in areas of intended focus & learning

What does remote focus look like for you?

Minimize distractions as much as possible, ask someone to mute if necessary

Pomodoro breaks are especially important for remote work and doubly so for quarantine. What should our Pom cadence look like?

Allow a POM after big wins / breakthroughs, Also as a chance to step away if feeling stuck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment