Site Deployed on Netlify here
Author: Alexander Beers, Anotoine Charette, Ryan Emmans Version: 2.0.3
Books are life-changing. They have the power to enlighten, educate, entertain, heal, and help us grow. This app is used to track what books have impacted the user, and what's recommended to read next.
Node.js
08-30-2021 2:45pm - Application now has a fully-functional express server, with a GET route for the book resource.
08-31-2021 2:00pm - Created POST route for /books which allows books to be added to the database.
08-31-2021 4:30pm - Created DELETE route for /books which allows books to be deleted from the database.
09-01-2021 8:00pm - Created PUT route for /books which allows the user to update book details.
09-02-2021 7:00pm - Adds book images. Adds Auth0.
Name of feature: Storage - Allow books that a user enters to persist
- Estimate of time needed to complete: 1hr
- Start time: 1:30
- Finish time: 2:45
- Actual time needed to complete: 1hr 15m
Name of feature: Storage - Add a new book to shelf, to keep book lists up to date
- Estimate of time needed to complete: 1hr
- Start time: 1:15
- Finish time: 2:00
- Actual time needed to complete: 45min
Name of feature: Storage - Delete book from shelf, to keep book lists up to date
- Estimate of time needed to complete: 1hr
- Start time: 3:00pm
- Finish time: 4:30pm
- Actual time needed to complete: 1hr 30m
Name of feature: Storage - Add PUT /books to allow client to update DB with book updates
- Estimate of time needed to complete: 1hr
- Start time: 3:00pm, 5:00pm
- Finish time: 4:00pm 5:30pm
- Actual time needed to complete: 1hr 30m
Name of feature: Auth0
- Estimate of time needed to complete: 4hrs
- Start time: 3:00pm, 2:00pm
- Finish time: 4:00pm 7:00pm
- Actual time needed to complete: 5hrs
-
What hours will you be available to communicate?
During the day up until 12:00am PST
-
What platform will you use to communicate (ie. Slack, phone …)?
Slack, phone, and Remo
-
How often will you take breaks?
Breaks will be taken as needed as determined by the group.
-
What is your plan if you start to fall behind?
Prioritize features and precede as needed
-
Make a list of each parson’s strengths. Antoine: Logical thinking Ryan: 'Visual guy', frontend design Alex: Problem solving, backend design
-
How can you best utilize these strengths in the development of your application?
Each person can take the lead in tasks that involve the strengths listed above
-
In what areas do you each want to develop greater strength? Antoine: Frontend design, styling (UI, layout, etc) Ryan: backend-development Alex: Frontend design, styling (UI, layout, etc)
-
Knowing that every person in your team needs to understand the code, how do you plan to approach the day-to-day development?
Meetings will be held at the beginning of each coding session to discuss that sessions tasks and priorities. Code reviews and educational disccusions will also be held.
-
What will your team do if one person is pulling all the weight while the other person is not contributing?
3 strike rule before further action is taken
-
What will your team do if one person is taking over the project and not letting the other member contribute?
Ensure every voice is heard and immediately communicate to said person to let them know they are taking over
-
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?
Engage in jolly cooperation and explain the code from each contribution that every member has made