Skip to content

Instantly share code, notes, and snippets.

@bbp5280
Last active July 30, 2017 21:10
Show Gist options
  • Save bbp5280/e193b5bcb9aeee248b3460cf293ad72e to your computer and use it in GitHub Desktop.
Save bbp5280/e193b5bcb9aeee248b3460cf293ad72e to your computer and use it in GitHub Desktop.

Project: Idea Box

Group Member Names: Ben Porter and Francy Lang

Project Expectations: What does each group member hope to get out of this project?

  • Use time productively, work on creating baby functions one at a time. Do the best that we can and each be able to articulate our way through the final code.

Goals and expectations:

  • To be more patient with ourselves and focus on what we have done and less about what we haven't or what we could have done better.

Team strengths:

  • Francy: Organization, planning.
  • Ben: flexible, adaptive.

How to overcome obstacles:

  • Scheduled pairings: Monday 4:10 with Margo, Tuesday 4:10 with Nick, Wednesday 12:00 with Christie
  • Take breaks when things are getting bleak.

Schedule Expectations (When are we available to work together and individually?):

  • Weekend: Saturday 11:00AM , mornings- 8am check-ins and planning for the afternoon, evenings next week.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):

  • Communicate through slack regularly and/or as needed.

Abilities Expectations (Technical strengths and areas for desired improvement):

  • Francy Strengths: HTML and CSS
  • Francy Improvement: jQuery and more complex JS functions. Responsive Design- without flexbox.
  • Ben Strengths: HTML and CSS and JS functions
  • Ben Improvement: jQuery

Workload Expectations (What features do we each want to work on?): CSS, responsiveness delete button, and prepend- complete together

  • Francy: edit card and update in local storage and on DOM, search/filter cards.
  • Ben: localStorage (storing and retrieving), upvote, downvote, final CSS edits.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):

  • Work on commiting more in GitHub...complete one thing and then commit.

Expectations for giving and receiving feedback:

  • Be open about needing breaks and commmunicate intentionally and in a respectful tone. Ask clarifiying questions before criticizing the code.

Agenda to discuss project launch:

  • Individually sketch-out the layout with percentages and tags.
  • Focus on the UI and get the comp in place first.
  • Identify the functionality we can do.
  • Keep track of questions that we can just ask during a pairing.

Ideas:

  • Start by implementing what we know from linked list project.

Tools:

  • Use human capital as a resource, ask questions frequently...don't struggle in silence.

Additional Notes:

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