Rocket provides multiple levels of difficulty to accommodate different learning speeds and prior experience. Students can complete Bootcamp without attempting Comfortable, but students that complete Comfortable may have a firmer grasp of concepts. Rocket recommends completing Base for all of each day's post-class and pre-class exercises before attempting Comfortable.
Bare minimum. All students must complete Base to understand concepts.
Reinforce with further exercises around same concepts. For students that wish to deepen understanding of current concepts before moving onto new ones.
Deepest exercises that Rocket offers for each concept. For students that wish to push the limits of their understanding of the current concepts.
Professional tech teams typically run using Agile Scrum Methodology. Rocket simulates this during Bootcamp project weeks. Each course day students will share the following with their section to keep each other on track.
What did you do between the previous course day and today?
What do you plan to do between today and the next course day?
Do you have any blockers?
Students present projects in class on the last day of each module. Presentations should cover the following.
App development strategy
Biggest challenges faced
What you might do differently next time
After each project your section leader will review your code with you 1-1. Please prepare answers to below questions before meeting. Consider recording notes; past students have found post-mortem notes helpful for resumes and portfolios.
Consider questions from both a technical and process perspective.
What went well? Please share a link to the specific code.
What were the biggest challenges you faced? Please share a link to the specific code.
What would you do differently next time?
Record a video after each project to showcase your hard work for your portfolio and employers.
Demo your app in a 1-2 minute video (brevity is best!)
Explain who your app is for, what their problem is and how they would solve their problem with your app
Use language that non-technical recruiters would understand
Record locally with Zoom with your face in the upper-right corner. Upload to YouTube and embed a video link in your project README.
These batches did not have a time limit; please keep yours under 2 minutes if possible.
You can then view their code under the File Changes tab in the PR to view all the changes they have made.
To run and build their project locally, you can click on their forked repo in the PR and git clone it down as usual to run the project.
Once cloned, you can follow the README to setup and run the app!
Peer Code Review
Occasionally we will review each others' code to learn from each other. Start by reviewing your partner's code individually, before discussing the review in pairs.
Part 1: Individual
Clone partner's code
Read partner's code
How does it work?
How is it different from my implementation?
What can I learn from this?
Run partner's code
If you're not sure how certain code might behave, run it. Feel free to edit the code to verify your understanding.
Complete code review on partner's GitHub pull request to help them improve
Part 2: In Pairs
Review learnings from individual code reviews
Pair program on 1 person's code to get a working version. The person with the weaker understanding of the current concepts should be the driver.
Using Google as a Resource
Students will need to use Google as a resource to solve problems not explained in Rocket's curriculum. Rocket will do our best to document the most common mistakes, but it would be impossible to document all. Professional SWEs spend most time finding answers on Google, and googling effectively may be your most important takeaway from Bootcamp.
With experience you will know when you are on the right track. Often it takes multiple permutations of Google search keywords to find the answer we are looking for. The goal when reading documentation, Stack Overflow or forum answers is to find relevant information as quickly as possible without reading more than necessary.