Progress / answers not saved

You bring up a good point, Roma. I hadn’t thought of that, but as you say, it’s not really necessary to save the HTML and CSS solutions. And mostly because there’s only one solution to those questions. But with JS, especially the algorithms, there’s multiple ways of solving the same problem. And a previous algorithm often is very helpful in solving newer ones and also we might want to improve our old algorithms as we learn new things. And it’s very hard to remember how a problem was solved, even a day before. Or maybe it’s my memory that is so bad.

But taking that into account, and considering that probably an even smaller percentage of users even get to the algorithms, it means even less hard disk space is needed.

repl.it, github, and any other method of saving our work is great. We just have to know from the beginning that it won’t be saved on FCC so we do save it in any of those other ways ourselves.

Interesting that for you and maybe others, the download button kinda told you that you wouldn’t see your code again unless you clicked it. For me, and probably many others, at least those posting here wondering about their answers as well, that button was basically invisible. Like ads or signs on the streets become, which we just ignore from the beginning. My own bad, but I just never stopped to wonder why that button was even there. Especially that the problems did get saved in the past.

1 Like