This is a rough thought, I don’t know how technically hard this is. I was thinking (for kinda long ever since I started learning on fCC) that the purpose of the no solution sharing policy can be heavily ruined by only copying someone’s correct part of code they shared.
Here’s a prototype of my suggestion. The original code should be only visible if (edit: all of these are or’s):
The user has passed that test already. (Probably requires linking progress to forum?)
The user wants a hint on the exact same problem; in this case, other code “irrelevant” to the problem should be omitted (I know it’s probably hard and takes extra work to define irrelevant).
The user wants to help; to detect this intention, the user must click a certain button & perform some further action.
learn and forum are different platforms, and people can setup separate user accounts for each, so linking the two may not be feasible for all users.
Even if someone hasn’t completed a challenge, doesn’t mean they cannot provide some assistance to the OP. The extent may depend on their knowledge and skills, not on curriculum progress. I’ve help users with syntax errors and to understand the lab, workshop, project, or daily coding challenge requirements, without completing that particular challenge.
Learning to code is tough, and if people want to help other people a good way is to remove barriers.
There is a blur effect posters can use to avoid spoiling other peoples learning opportunity.
Copying and pasting code snippets won’t help to learn to code. Part of coding is debugging, troubleshooting, problem solving, planning, understanding the problem, handling emotions, and patience.
I think the idea behind not posting solutions is so that the learner can work though the problem on their own, with guidance and suggestions from forum members.
I didn’t expect this quick post to be treated so seriously so thank you for providing much more insight!! I’ve thought of some of the subtlities mentioned beforehands (e.g. if a user learned from different sources already) but was a bit hurried addressing thoughts.
Appreciate your terrific work as always, and happy coding >U<