React Solo Project Expectations

Next week, you get a full week to write a compelling front-end application to go into your portfolio.

Expectations

The following is the list of expectations that must be met for a project to be considered complete.

1. Project will be picked from the list of projects from the previous reading or come up with your own idea.
2. You should have the following documentation either in the Wiki of your GitHub repo or in a documentation folder in your root directory:
   • Schema
   • Feature Document outlining MVP features as well as additional features (user stories and acceptance criteria strongly encouraged)
3. A README with instructions on how to launch the application
4. Your app must have user authentication
   • Sign Up
   • Login / Logout
   • Demo User Login
5. Must have at least one major CRUD feature in addition to user authentication
6. Front-end:
   • React
   • Redux
   • Hooks are optional (but encouraged)
7. Backend:
   • Express
   • Sequelize

Student Responsibilities

1. By EOD today, create your project repo, upload your feature list to your repo and send your project advisor your list of features for sign-off
2. Join your new “circle” slack which you will be invited to by the end of day. Your circle consists of all the students that have the same project advisor as you. You will be having stand up and end of day chats with this circle.
3. Every day you will attend stand up with your advisor and the other students in your circle – be prepared to discuss what you worked on the day before and have a plan for what you want to accomplish that day.
4. Complete all nightly reports as per usual and use these reports to reflect on your progress. We rely on these reports to check in on your progress so please, as always, take them seriously. Some examples:
   • “I expected to finish the back- and frontend for logging in, but still need to debug my onSubmit.”
   • “At the beginning of the day, I was very confused about the Redux cycle, but going through debugger waterfalls while testing my action creators on the window really helped.”
   • “Today I really struggled with destructuring my state. I think the next time I do a project like this, I will structure my frontend state to use more slices and less nesting.”

Question Asking

During this project, you will get practice expressing yourself when running into trouble without just saying “it doesn’t work”. In a professional environment, knowing when to ask for help and not spending too much time on any one problem is critical, but making the most out of the time with your manager or Senior Engineers is also vital.

Questions should be asked in Slack to your entire circle. Before asking a question, please have the following available:

• What you are working on
• A description of the problem
• What the error message says on the server/frontend console (if there is one)
• A relevant code snippet
• The debugging process you’ve done so far (MANDATORY)

This process allows your fellow students to also help you out – further, it will allow us to know if multiple students are having similar issues and if so we can have a group session to clarify if necessary.