Author: Alan Chelko, Stephen Clemmer Version: 1.0.0 (increment the patch/fix version number if you make more commits past your first submission)
Books are life-changing. They have the power to enlighten, educate, entertain, heal, and help us grow. Throughout this module, we are creating a small app to track what books have impacted you, and what’s recommended to read next.
Web applications essentially all work by managing data related to “resources”. The resources that an app cares about can be just about anything: a product for sale, an uploaded photo, a review, a bit of weather data… whatever it is that gets stored in a database. When the app provides the interface to create, read, update, and delete a resource, we refer to that as a CRUD app. Over the next few labs, you will build an app that has books as a resource.
Primarily, the project entailed working through CRUD / REST / Mongoose / Axios / Express:
* CRUD: Create / REST: POST / Mongoose: Model.create() / Axios: axios.post() / Express: app.post()
* CRUD: Read / REST: GET / Mongoose: Model.find() / Axios: axios.get() / Express: app.get()
* CRUD: Update / REST: PUT / Mongoose: Model.findByIdAndUpdate() / Axios: axios.put() / Express: app.put()
* CRUD: Delete / REST: DELETE / Mongoos: Model.findByIdAndDelete() / Axios: axios.delete() / Express: app.delete()
Backend: Express Server, Node.js and Mongoose/MondgoDB cloud deployment Frontend: primarily React
Author: Alan Chelko & Stephen Clemmer Version: 1.0.0 (increment the patch/fix version number if you make more commits past your first submission)
* Stephen Clemmer, Partner
* Special thanks to Audrey and Ben
Alan Chelko & Stephen Clemmer Team Agreement
For any potential conflicts, we plan to work things out on a consensual basis, but assuming a real conflict arises, we would plan to go through a pros and cons scrum session and weigh it from there. We'll still strive to reach consensus.
Alan: some JS experience from earlier this year Stephen: Feels more comfortable on the backend than the front end currently. Project management.
Generally, we'll tap the strengths of each member, but we do not want to silo anybody by any particular skill or lack of skill. We have decided to have Stephen drive on the backend and Alan drive on the front end
Knowing that every person in your team needs to understand all aspects of the project, how do you plan to approach the day-to-day work?
We will pair program for this project. Stephen driving on the backend, Alan driving on the front end. We will pause as needed to clarify the code.
Target same hours as normal CF class hours: 9:00 - 17:00 PST.
Slack, Remo, gmail.
As needed
We will ACP at every functional component
Alan will merge front end PRs. Stephen will merge backend PRs.
Name of feature: Lab 11 #1 Repository Setup Estimate of time needed to complete: 1 hour Start time: 1:00 p.m. Finish time: 2:00 p.m. Actual time needed to complete: 1hour
==================================================================== Name of feature: Lab 11 #3 Book Component Estimate of time needed to complete: 4 hours Start time: 3:30 p.m. Finish time: 9:00 p.m. Actual time needed to complete: 5.5 hours
==================================================================== Name of feature: Lab 12 #1 Create
Estimate of time needed to complete: 2 hours Start time: 2:00 p.m. Finish time: 3:30 p.m. Actual time needed to complete: 1.5 hours
==================================================================== Name of feature: Lab 12 #2 Delete
Estimate of time needed to complete: 2 hours Start time: 4:30 p.m. Finish time: 6:00 p.m. Actual time needed to complete: 1.5 hours
==================================================================== Name of feature: Lab 13 #1 Update Estimate of time needed to complete: 4 hours Start time: 2:30 p.m. Finish time: 5:30 p.m. Actual time needed to complete: 3 hours
====================================================================
2:27 AM | Today
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent