Academic Dishonesty in FCC Projects

I have a question. In this page FCC team says “While you do this, our team will code review each of your code portfolios to ensure that all user stories have been completed, and that there are no signs of academic dishonesty.”

I’m trying to do my first tribute page, but i’m looking from codepen example. I’ve copied some of those codes, is this cheating or academic dishonesty? I can’t write a web page from scratch. I don’t know too many coding.

Thank you.

If you have completed all the challenges up through where you start the first projects, you will have at least 95% of the knowledge it takes to complete the first 3 projects. It does not have to be exactly like the demo. It just needs to meet the User Stories’ requirements. The demo uses features which you would not have already been exposed to, but don’t worry about that. You can always go back later and use other features which you will learn later.

The best advice I can give you is do the challenges before attempting to do the projects. When you finally start the projects, try to write as much code as possible. If you get stuck, you can always post your code so far and someone will try to help point you in the right direction when you get stuck.

1 Like

Thanks for the answer. So i can look at the codepen but my projects need to be my own code. I got it :slight_smile: I’ll try my best ^^

For learning purposes, you are advised not to look at the code behind the projects. The idea is to take what you have learned through working on the challenges before the projects and apply what you have learned to try to achieve what is required in the User Stories. In my experience, until you learn the basics, looking at the code does not help you to learn how to code. Being able to write the code without looking at FCCs complete solution will help you learn in the long run. Anyone can copy/paste the FCC code and “modify” it to the point that it looks different. If you expect to pass an interview when all you have ever done is copy/paste solutions from some other source and “tweaked” them, the interviewer will quickly be able to know you don’t understand why code is working a specific way. These are just my opinions based on how I have learned to code over the past 16 years.