TL;DR:
Main point is that, for the most part, students who fall behind can eventually run out of time by the end of their contract. Then they either have to work something out with CodersCampus to pay for extended support, or else finish on their own without support (something we have never seen before).
We are still iterating on early warning systems to help you fix the problem as early as possible, for your own benefit.
Disclaimer:
This is a topic which has many more nuances, some legal and financial, than can be properly addressed in a brief support document. As a result, this document will only address a few issues, and of those, only from the perspective of an instructor. This is not a legal document, and does not affect your contract with CodersCampus, a lending institution, or any other point of view.
Note:
This document may not always reflect the latest iteration of our processes implemented on your behalf.
We have seen our best students fall behind and still have great outcomes, including a new coding career. But these are the rare exceptions.
Here is a partial list of the cascade of consequences for falling behind, from first to last event:
Since each of the above events can cause you lots of heart-burn and frustration, each of the above events is more carefully explained, below.
If you are only one or two assignments behind, the hard truth is you will probably have to spend more time grinding on your code to get caught up.
The reason this can be a big deal is because, if you remain behind, it heightens the chances of you not graduating within your contract time. If you have questions on your specific contract please reach out to Irish Morales on slack.
The best discipline is ALWAYS internal. A professional, guided by thier own high expectations of self, are 10x better equipped than any tool that collects data.
But if you are behind, and the internal professional motivation isn’t doing the trick, you’re going to have to show us you are working on the courework in order to remain active. You will officially be in Time Watch status. The way you show us your progress and committment is with the Work Log below.
Click this link for the Work Log
If you fall behind in the bootcamp, you may be marked as inactive. Here’s what that means and how you can regain your active status.
To regain your active status, you need to submit Work Logs to show progress. This log should include:
Regularly submitting your Work Log will demonstrate your commitment and help you transition back to active status.
If you are on the verge of becoming inactive, you will be in Time Watch status. You can take steps to remain active:
Staying active ensures you remain connected with your peers and instructors, receive timely support, and make the most of your bootcamp journey.
Along with just putting more time into your code, attending meetings/check-ins (for which we track attendance), will help you not only get caught up, but will give you glimpses at assignments you will have to do in the future, and see where people get hung up in those assignment, which will help you avoid those hangups.
If you use all of your resources (the coursework, YouTube, Stack overflow, google, Chat GPT, Gemini & Claude), as well as come to the check-in meetings, your chances of getting caught up are far greater.
If you are concerned that you will fall behind due to a life event, or simply not moving at as fast a pace as you thought you might, please reach out to Pete Carapetyan, Irish Morales, or myself (Miriam Law) via slack.
THERE IS ZERO JUDGMENT IF YOU FALL BEHIND! We just want to rally behind you to do what we can to get you caught up, graduated, and employed.