Skip to content

Instantly share code, notes, and snippets.

@kayyali18
Last active July 31, 2018 04:09
Show Gist options
  • Save kayyali18/1bc35cae7250495c0458c61772befeb8 to your computer and use it in GitHub Desktop.
Save kayyali18/1bc35cae7250495c0458c61772befeb8 to your computer and use it in GitHub Desktop.

#DTR Memo for 2Do-Box Pivot - Kevin Simpson and Ahmad Kayyali Guiding Questions to Define The Relationship:
What are your learning goals for this project? What drives us in this project?
Kevin - My goal is to meet the specs for the project through the second phase.
Ahmad - To complete all phases
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Kevin - My style for collaboration is generally a divide-and-conquer style, but working with Ahmad, who has quite a bit more experience with JS than I do, I would prefer a paired approach so that I can learn from him.
Ahmad - All styles work for me, as long as I get to code
How do you communicate best? How do you appreciate receiving communication from others?
Kevin - Slack generally works best for me.
Ahmad - Slack
How would you describe your work style?
Kevin - I'm pretty relentless. I can go for long periods without a break unless I'm becoming overly-frustrated.
Ahmad - Dividing big problems into manageable daily tasks
What are your strengths? How can our strengths complement each other?
Kevin - I feel that I'm generally pretty good at keeping a strategic view of the task, which makes me better-suited to navigating.
Ahmad - Minimising and refactoring code to be as concise as possible
What’s gone well or poorly in your previous projects?
Kevin - In my previous projects, my partners struggled a bit with the JavaScript portions of our tasks, which meant that I fel that I had to come up with the majority of the solutions. My last partner, despite his struggles, was great at keeping us on task and getting us set up with pairing.
Ahmad - Nothing really
How will we set direction and make decisions as a team?
Kevin - I believe it's important to be honest and forthright with problems, and that generally the most expedient solution will often be best rather than get sucked down a rabbit hole.
Ahmad - We'll work out the best strategy for achieving our goals over the week
How will we overcome obstacles?
Kevin - I try to approach obstacles by tracing them backwards step-by-step until I can find the cause. If things get out-of-hand or frustrating, take a break, move onto an task and come back to it later, or asking for help from Mod 2.
Ahmad - My viewing them as challenges
What do you need (resources, environment, communication) to do your best work?
Kevin - As long as I have a clear idea of when/where we're meeting and the enough time to complete the task, I'm happy.
Ahmad - Laptop and water
What scheduling restraints do you have? What are your scheduling preferences?
Kevin - I can make most schedules work provided I have enough time to arrange it with my family.
Ahmad - Anytime 24/7
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
Kevin - I'm generally pretty honest, but am also generous with praise when deserved.
Ahmad - I hate giving feedback because I don't like telling people what they should be or do
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?
Kevin - I feel like my JavaScript is in decent shape coming out of Ideabox. While I may not have my partner's experience, I am coming at it from a new persepective, which might help us to find solutions that might not occur to him.
Ahmad - Javascript and CSS
What tools do you want to use to manage the project?
Kevin - Pairing with upper-Mod folks if necessary.
Ahmad - Stack overflow
How do you want the group to solve problems when members run into issues with features of the project?
Kevin - Methodically. Use console.logs. Follow problems backward and fix them regardless of how much time it takes.
Ahmad - Kevin has that on point
How do you know if a project is successful? How can we achieve that as a group?
Kevin - I feel that this project will be successful if I walk away with a better understanding of JavaScript than I had before we started.
How will we recognize each other's successes and celebrate them?
Kevin - High-fives.
Ahmad - It's a success to me if I feel that I gave it my best effort
Any additional questions that you would like to add:
Template for DTR Memo Project: 2DoBox
Group Member Names: Kevin Simpson and Ahmad Kayyali
Project Expectations: What does each group member hope to get out of this project? To walk away with a better understanding of JavaScript and DOM manipulation.
Goals and expectations: Our goal is to meet the expectations for phase three and to do work on the project together as much as possible.
Team strengths: Strong foundation in JavaScript.
How to overcome obstacles: Patiently and honestly.
Schedule Expectations (When are we available to work together and individually?): After class and on the weekends when available. Not more than a few hours on Saturday/Sunday.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): We will use Slack and talk in/after class.
Abilities Expectations (Technical strengths and areas for desired improvement): That we have the know-how to take on the JavaScript requirements without much need for help from upper-Mod folks.
Workload Expectations (What features do we each want to work on?): We want to complete Phase 3 of the project at the very least.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): We will use normal Git workflow and standard Driver/Navigator pairing.
Expectations for giving and receiving feedback: To be honest, kind, and specific

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