rheamimicarillo / can-of-books-frontend

Project Name

Author: Amy Pierce, Rhea Carillo, Jordan Yamada Version: 1.0.0 (increment the patch/fix version number if you make more commits past your first submission)

Overview

This is the frontend for the Can of Books project we are doing for class 301.

Getting Started

Clone the starter template from

Architecture

HTML, CSS, Javascript, React.js, Axios

Change Log

08/29/22 5:45PM Application is a fully functioning frontend connected to a server and is rendering a webpage with the expected data.

Estimates

Lab11

Name of feature: Set up

Estimate of time needed to complete: 3 hours

Start time: 2pm

Finish time: 5:45 pm

Actual time needed to complete: 5 hours

Lab12

Name of feature: Set up

Estimate of time needed to complete: 5 hours

Start time: 2:00 pm

Finish time:

Actual time needed to complete:

Credit and Collaborations

Thanks to Sheyna Watkins, [other people or resources that helped]

What hours will you be available to communicate?

All team members will be available from 9am-6pm and additional hours as negotiated.

What platform will you use to communicate (ie. Slack, phone …)?

Slack and in person.

How often will you take breaks?

We are going to try to employ a 50-10 pomodoro strategy.

What is your plan if you start to fall behind?

Fail. (Jordan disagrees so we are negotiating this point.)

Cooperative

Make a list of each parson’s strengths.

Rhea is good at debugging, analyzing, and commenting. Jordan is good at debugging, analyzing and creative problem solving. Amy is good at time management, breaking and fixing code and wearing purple.

How can you best utilize these strengths in the development of your application?

Seriouslyly we agree that we're all tired of these questions.

In what areas do you each want to develop greater strength?

Amy wants to get better at writing dry code and using built in functions, Jordan wants to get better at intial project implementation, Rhea wants to get better at assertiveness.

Knowing that every person in your team needs to understand the code, how do you plan to approach the day-to-day development?

Very carefully. We will pair program, discuss any code a member doesn't understand, and check in on each other's progress as needed.

Conflict Resolution

What will your team do if one person is pulling all the weight while the other person is not contributing?

Muay Thai.

What will your team do if one person is taking over the project and not letting the other member contribute?

Muy Thai.

How will you approach each other and the challenge of building an application knowing that it is impossible for two people to be at the exact same place in understanding and skill level?

Everyone has strengths and weaknesses. We will be respectful of each other's learning processes. And...

Muy Thai.