If you fully understand how our methodology works, what to expect about the projects you deliver, and why they are so important, you'll be more motivated to do the work and take advantage of it.
We want you to deliver a couple of projects every week. Building projects is all that matters in this course because: Your employer will pay you to create projects.
Note: Exercises, quizzes, and lessons only exist because you need them to learn how to build projects.
Since projects are the most critical part of the course, we have created several ways to give you feedback; here are a few:
It's not always possible, and it's tough to implement, but we make a significant effort to create unit tests for every project; this means that you can run a command in the terminal (or press a button) to get instant feedback about your code.
Note: Automatic grading is a double-edged sword because the grading feedback in the command line is hard to read. It's essential to learn how to read these tests.
Each assignment you deliver will be manually reviewed by a mentor. The mentor will scan your code and give you feedback via GitHub or as a message inside 4Geeks.com.
This feedback will focus mainly on the coding guidelines; you can read them here, but here is a brief summary of the criteria:
Every now and then, we dedicate parts of the live classes to review previous code in several formats. Group review: during class, you will be put into teams with one mentor to review project solutions from you or your classmates.
There are many ways to get unstuck:
The more active you are during the course, the more you will take advantage of it: