📓 1.0.0.09 Independent Projects and Code Reviews
In this lesson
- What independent projects (code reviews) are and why they matter
- Expectations, the 8-hour work requirement, and how to submit
- What happens if you need to resubmit—and where to get help
Overview
At the end of each course section (1.1. for instance) you will complete an independent project. This project will demonstrate the concepts covered during the section. It will also act as an example of your coding ability in your growing portfolio.
This lesson will walk through the entire independent project process, including expectations, feedback, and submission.
Code Reviews
At Fidgetech, we use "independent project" and "code review" interchangeably. A code review is the activity of someone other than yourself reviewing your code for mistakes. We also simply refer to "code reviews" as "CRs".
In the tech industry, code reviews are commonly used for quality assurance. Before your code gets added to production, your colleague or manager will review your logic, code structure, and ensure that you are following best practice and convention. Often, your colleague or manager will ask you to make changes to your code before they approve it to be added to production. By the way, "production" or "production code" is a way to describe software and code that is actively being used by customers.
At Fidgetech, your coding instructor will review the independent project you submit for each course section as your "code review". Also, in some class exercises, we invite you to do peer code reviews, in which you and your pair reviews another pair's code.
Academic Honesty
We want you to succeed, and independent projects are how we give you honest, personalized feedback on your skills. Submit your own work. You may reference online resources, the Fidgetech curriculum, and your own code, but you may not view or copy current or former students' work.
As explained in our Student Handbook, these projects help you build skills for jobs after graduation. Copying someone else's work skips that practice and can leave you unprepared for interviews and on-the-job expectations.
AI tools are subject to the same honesty rules as other references. If you can't explain your code, you're not ready to submit it. See Using AI Responsibly at Fidgetech and Academic Honesty for details.
If you are struggling or feel overwhelmed, do the best you can and submit what you have. Failing projects may be resubmitted (see Resubmission below). Your instructor can help you improve and resubmit—see How to Ask for Help and the next lesson, Academic Honesty, for what you can reference and what to do when you are stuck. Plagiarism is never the only option.
The next lesson goes into more detail about academic honesty, including general guidelines. Projects are reviewed to confirm work is your own. Plagiarism or receiving unauthorized help on an independent project is grounds for expulsion, as described in the student handbook.
Course Requirements
Successful completion of independent projects is required to pass courses and graduate. Keep the following in mind:
-
All independent projects must be completed and passing to pass a course.
-
You must pass your current course to advance to the next course.
-
You must pass all courses in the program to graduate.
-
You are also required to verbally walk your instructor through at least one independent project codebase in-person or by video at least once in the program. At your instructor's discretion, you may be asked to do this more than once. Your instructor will determine which project to discuss and set up a meeting.
Expectations
In general, we have the following expectations for independent projects.
-
All independent project objectives should be successfully completed. If you are unable to complete all objectives, you will have a chance to fix and update your independent project.
-
The completed project must use the provided prompt. For instance, you cannot simply create your own prompt because you do not want to work on the prompt provided. As an example, if the prompt asks you to create an application for an imaginary storefront, you cannot instead turn in a choose-your-own-adventure application, even if the completed project demonstrates understanding of the course materials.
-
You must work on the project during the time frame allotted and for the required hours (see Time on project below).
-
All projects must include a complete README. We'll go over the requirements for a README in a future lesson.
Time on Project
For full-time students, you are expected to work at least 8 hours on each independent project during the allotted time frame. Instructors may use your Git commit history (Git tracks changes to code) to confirm you spent adequate time.
If you finish the required objectives early, use the remaining time for Further Exploration (optional stretch goals in each project), polish, or extra practice. Do not stop at the minimum if time remains in your project window.
Further Exploration
Each project includes a Further Exploration section with optional objectives. These extend your application beyond the minimum requirements. Tackle them if you complete the primary objectives with time to spare, or you wish to continue building.
Remember, the purpose of completing these projects isn't just to pass your courses! In the future, you will need to demonstrate your coding skills to potential employers. By creating polished, professional projects in each section you will exit the program with a diverse, well-rounded portfolio before you even begin your job search!
Submission
Before submitting, use this checklist:
- All required objectives are complete (or you have noted what is still in progress)
- You used the provided project prompt (not a substitute topic)
- You worked at least 8 hours on the project (full-time students) during the allotted window
- Your README is complete
- Code is pushed to a GitHub repo
- You are ready to add your GitHub link and notes for your instructor in Code Central
Do a final polish pass: check indentation, remove commented-out code, and make sure the project feels complete.
When everything is in order, complete the following steps to submit your project:
- Push the final code to a GitHub repo.
- Login to Fidgetech Code Central and select your current course.
- Select the link for this section's code review.
- Paste the link to your GitHub repo in the provided field.
- In the large text field below the link, include a brief note to your teacher about your process during this project, and any questions or concerns you may have. This content will be sent with your project submission to your teacher, and is not anonymous.
- Submit your independent project for review!
Evaluation & Feedback
Your teacher will review your project as soon as they can. You'll receive general written feedback, and each objective will be rated on the following scale:
- The code does not meet this standard.
- The code meets this standard most of the time.
- The code meets this standard all of the time.
To pass a code review, you must receive meets this standard most of the time or meets this standard all of the time on all objectives. If any objectives receive a does not meet this standard the project does not pass. You will be required to complete further work and re-submit.
Resubmission
If you fail to pass any of the objectives, your teacher's feedback will identify why the objective(s) are not met, and what can be improved to meet them. Take the opportunity to check in with your teacher regarding anything you don't understand, work through those problems, then resubmit using the same steps listed above. In the Notes field, document exactly what work you've done since your last resubmission.
Group Work
You will work in groups on two cumulative, collaborative projects at some point during your time at Fidgetech, it could be in Javascript or React. Your instructors will keep you informed about how that will work.
Students will present on their group projects upon completion and will be expected to submit an independent project (in lieu of a Friday project) with a link to the group project.