I love the new coding challenges. But something I’d like, is the ability to look at other learners’ solutions. This would allow us to see if there might be a more elegant way to handle a challenge. (“Oh, I never would have thought of using a .map()!”) I guess alternately, it lets us feel smug if other learners’ responses aren’t as elegant as ours. Perhaps we could upvote particularly elegant solutions, and they could be ordered by popularity?
1 Like
you can try to propose this on github
but be aware that freeCodeCamp is not saving challenges for a while now, as they occupy too much server space and is not in the budget, so I am not sure this would be implemented either
1 Like
Back-of-the-napkin math suggests that the whole database to store solutions would fit on a readily-available hard drive, at least if my guesses as to the numbers involved are close.
_But,_ I’m aware that proselytizing an idea to a nonprofit like FCC eventually results in, “Okay, you do it then.” And, well, I’m still learning. I don’t have any exposure to the back-end stuff I’d need to learn to work with that kind of database.
Something I’ve seen on another site, I’d really have no idea at all how to implement. When you looked at other people’s solutions, you’d see, “Doug submitted: [code]. Larry, Mary, Terry, and 128 others submitted substantially similar solutions.” I can’t even imagine how to determine that two pieces of code are “substantially similar.”
I think it’s a good idea and it’s a good way to learn to read other people’s code and see different approaches to a solution.
It sounds like you are referring to codewars? I would just do that that there, if that’s what you’re looking for. It’s already implemented and designed that way. Not sure if leetcode works the same way?
Might compare the text using a diff or timing them to see how fast they execute.
1 Like
originally freecodecamp used to store all solutions submitted on the server, and that’s the reason it stopped being possible to save solutions, it was consuming too much resources. Consider it’s not just storage space, it’s also requests to the server to save and retrieve the code.
Plus it’s the amount of people involved. At the time saved data was grewing a few GBs per day
3 Likes