I started FCC several years ago (2014~15ish) and was working hard on the JS algorithm challenges. This shutdown has finally given me the time to come back to my dev study. My progression does show the challenges I submitted as being complete, but the code is nowhere in sight. Have our solutions been archived anywhere, if we didn’t download them at the time? I did download many of them, but not all.
Solutions are not saved on the FCC server. They disabled that after discovering it took up too much space.
Thank you, nhcarrigan. Appreciate the heads up. I’ll download them all, from here on out, if they haven’t been developed outside the FCC site.
I don’t download all of mine, but some of the harder ones I’ll save and put on GitHub.
right… that’s more what I meant. The ones that have tricky logic and so on. The bigger projects will be in codepen or elsewhere anyways.
There are two different types of saved progress for Free Code Camp: your profile and your browser cache.
A list of your completed challenges is saved to your account in the FCC database. You can see the list of completed challenges by looking at your public portfolio. With a growing curriculum already over 1,400 lessons and a community of millions of people, FCC does not store every solution to every challenge in its database. When you complete a challenge, there is a modal that gives you the option to download your solution. This gives you the option to save a copy of any solution that you may want to reference later. There are some challenges which are classified as projects required for certifications. Your solutions to those can be viewed on your settings page.
Your in-editor code is saved in your browser’s local storage. Recent in-progress code from the challenge editor is also saved in your local browser cache when you run tests. If you are completing lessons and do not see your recent code, then your local storage has been cleared or something is preventing FCC from writing to your browser’s storage. This could be a browser setting, a privacy extension, or a browser version incompatibility. Especially as you get to more complicated challenges that may take multiple sessions, I strongly recommend saving your in-progress work outside of the browser cache.
This is a good opportunity to learn the ins and outs of your GitHub account, but you can also just save locally or use a service like repl.it which allows for versioning.