An open API service indexing awesome lists of open source software.

https://github.com/thomas-basham/digital-bookshelf-backend


https://github.com/thomas-basham/digital-bookshelf-backend

Last synced: 4 months ago
JSON representation

Awesome Lists containing this project

README

        

# Project Name

**Authors**: Cole Gibbs, Thomas Basham
**Version**: 1.0.0

## Overview

Books are life-changing. They have the power to enlighten, educate, entertain, heal, and help us grow. Build out this code base to create an web app to track what books have impacted you, and what's recommended to read next.

## Getting Started

clone repos to both machines and deploy on cloud
Download express, dotenv, cors, mongoose
Add gitignore's
add .env's

## Architecture

Express, dotenv, cors, mongoose, nodemon, mongodb, javascript,

## Change Log

## Estimates

Name of feature:**Set up Repos**

Estimate of time needed to complete: **2hrs**

Start time: **2:00**

Finish time: **2:30**

Actual time needed to complete: **30mins**

Name of feature:**Storage**

Estimate of time needed to complete: **2hrs**

Start time: **2:30**

Finish time: **4:00**

Actual time needed to complete: **1.5hrs**

---------------------------------------------------

Name of feature:**Create/ Add new book**

Estimate of time needed to complete: **2hrs**

Start time: **2:00**

Finish time: **4:00**

Actual time needed to complete: **2hrs**

Name of feature:**Delete/ Remove a book**

Estimate of time needed to complete: **2hrs**

Start time: **4:00**

Finish time: **:00**

Actual time needed to complete: **hrs**

## Credit and Collaborations

### Logicstical

#### What hours will you be available to communicate?

We will communicate an work between 1 and 6 pm. We will meet at night if we are behind.

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

We will use Slack to communicate.

#### How often will you take breaks?

We will take breaks every hour to hour and a half.

#### What is your plan if you start to fall behind?

We will define our priorities and focus on those tasks. We will meet at night if needed.

### Cooperative

#### Make a list of each parson’s strengths

Thomas: organized, timely, and open minded
Cole: prioritizing, orginization, and communication

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

We can use these strengths by defining what needs to get done and when in the most efficent way.

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

Thomas: Functional Programming
Cole: Pair Programming

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

We will pair program so we will be able to ensure that we both understand what is being coded.

### Conflict Resolution

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

If one person is pulling to much weight, the one doing more will ask for more support and the one not contributing will ask for more responsiblity.

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

The person who is contribuing less will tell the other team member that they are unhappy with the amount of work they are doing and would like to have an even split on tasks.

#### 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?

We will be pair programming so hopefully the holes in one partners knowledge will be filled by the others and vica verca.

## Resources
[https://prismatic-gaufre-72d962.netlify.app/]
[https://github.com/bashamtg/can-of-books-backend/]
[https://github.com/colegibbs/can-of-books-frontend]
[https://trello.com/b/NqrdXmp5]
[https://can-of-books-backend-cole-tom.herokuapp.com/]