As a reminder: REMINDER: Although we recommend working together with your peers, students are assessed individually. The deliverables you submit for assessment must be original and unique. Click here for more information about Project Deliverables and Group Work.
Contrary to popular belief, working as a developer involves significant collaboration. Being a developer within an organization (be it a company, association, etc.) means that you will have a role that requires your individual expertise and skill set. Being a developer; however, also means working with other developers.
Because working with others is such a critical soft skill, OpenClassrooms encourages collaboration among students completing developer paths (i.e. Web Developer, JavaScript Application Developer - React, iOS, Android etc.). Although group work is encouraged, all of the work you submit for assessment must be your own. Any form of code plagiarism will result in the invalidation of deliverables during an assessment, and ultimately the jury’s refusal.
How can I collaborate with other learners?
There are several ways you can collaborate with other learners during your OpenClassrooms training. You can:
- organize study sessions via videoconference
- recommend and share resources
- demonstrate your approach to completing projects
- share tips on how to progress quickly
You may find even more ways to work together with your peers, but be sure that you understand the differences between collaboration and plagiarism.
|
Examples of Collaboration ✅ |
Examples of Cheating❌ |
|
Sharing your screen with other learners to discuss your code and explain how you arrived at a solution. |
Sending your code to another learner, suggesting that they copy your work without explaining it. |
|
Share your repository with another learner, pointing out specific areas where you need help. |
Sharing your code publicly on a Workplace or Discord group to ask for help. |
|
Collaborating with learners who are working on the same project as you. |
Asking for ready-made solutions from learners who have already completed the project you’re working on. |
|
Explaining a concept that a learner is struggling to understand. |
Giving a working code to a learner without trying to help them understand it. |
|
Consulting someone else's code, making sure you fully understand it before using it yourself. |
Copying/Pasting a code without understanding it (and without being able to explain it to your mentor or during your defense). |
|
Consider feedback from other learners; even if a code is working, there are always multiple right answers. |
Sharing your code as the only possible solution that everyone should follow. |
It’s important to specify that at OpenClassrooms, the evaluation of your projects remains individual. Your deliverables must be personal and different from those of your peers!
As a friendly reminder, please note:
- Your knowledge will be verified by an assessor during your defense. You will need to share the thought process behind your work. Any suspicion of fraud, plagiarism or cheating will be reported and subject to consequences.
- By copying the work of others, you risk the early termination of your training.
- It isn't in your interest, nor that of the learning community, to reproduce someone else's code or work. In a professional setting, you will need to demonstrate that you have mastered the skills required to complete our projects.
For additional information, please see this article
Availability of your repository
We recommend that you keep your repositories in public mode so that your evaluator and the jury can access and evaluate them efficiently.