I have noticed that the solution submitting and viewing system in Brilliant has changed. But I don't think this is for the good. Here are a few suggestions:
The window for previewing solutions is too small. This makes previewing solutions difficult, as the sizes of the preview window and final solution box are wildly different.
The box for typing the solutions has gotten tinier, to accommodate the tips box beside it. That makes writing solutions even harder, as we cannot adjust the size of the text box as per our requirements.
Whenever we would click on the "show solutions" button, a confirmation box would appear, which would warn that access to the solution discussion costs some points, and would ask the user whether he would like to proceed. I see no such thing in this new system. In fact while working on this problem, I accidentally pressed that button, and now I cannot solve it. :(
I would be grateful if the Brilliant staff looks into these problems, and change the solution writing (and viewing) system to the way it was (or atleast almost the way it was). Thanks! :)
Easy Math Editor
This discussion board is a place to discuss our Daily Challenges and the math and science related to those challenges. Explanations are more than just a solution — they should explain the steps and thinking strategies that you used to obtain the solution. Comments should further the discussion of math and science.
When posting on Brilliant:
*italics*
or_italics_
**bold**
or__bold__
paragraph 1
paragraph 2
[example link](https://brilliant.org)
> This is a quote
\(
...\)
or\[
...\]
to ensure proper formatting.2 \times 3
2^{34}
a_{i-1}
\frac{2}{3}
\sqrt{2}
\sum_{i=1}^3
\sin \theta
\boxed{123}
Comments
Hello,
We have widened the solution composing/previewing box, and reformatted the guidelines as requested.
As to the third point, we have eliminated the point penalty for viewing solutions. We felt that charging people points for viewing a solution, was more of a deterrent toward people learning than a fun challenge.
If we continue to see evidence that lots of people are unintentionally entering the solution discussion before solving the problem, then we will consider putting the warning box back in.
Log in to reply
Eliminating the point cost is a good idea, I agree. However, I still think the warning should appear (or maybe only in problems in your own set), because there have been lots of people (me included) who have accidentally clicked it.
By the same argument, isn't a point penalty for viewing a problem a deterrent toward people trying new problems?
I think that rating should decrease, however, if someone wants to view the solutions. This generally means they cannot solve the problem, so their rating should decrease.
I prefer spending points for the solution......but since the free solution is a better idea...I also support it
But it'd be better if there was a dialogue box asking "Do you want to view the solution for 0 points?" or something like that......
Sorry but I couldn't understand the reason in keeping this free solutions
then there is no reason in stopping people to discuss this problem in the discussions
I completely agree with you.
Regarding your third point-The same thing happened with me in the same question! :(
Log in to reply
That's a strange coincidence. :)
Same for me too. Woah.
Completely agreed with all the points... and Brilliant should lay stress most on the third point, because last week I mistakenly clicked on the "View Solutions" button instead I wanted to write one
I don't understand why there is a strict partition between choosing "view solution" and "enter discussion". Is there some way to allow for a user to view the currently existing solutions, or at least what their "key technique" is before deciding to write one themselves? It is a pain to spend time writing a solution only to find that the same exact argument has already been made in detail by another user.
Log in to reply
The "enter discussion" option is for those who haven't solved that problem (and it costs some points). Once you have solved a particular problem, you can either look at the other solutions, or write one yourself. There's no way you can view other solutions before writing yours (unless you make a fake account, which, of course, is prohibited). In case you find out that the same arguments are used in detail by another user, you can choose to keep your solution private, and write a solution to another problem instead.
Log in to reply
Hah, yes, I know! That is what my post is meant to complain about.
I don't know how much free time you have, but a good solution can take me a while, sometimes up to 45 minutes. With a job and people to feed and things, it is pretty annoying to spend so much time on a solution only to learn it was totally redundant to what's already been posted.
The solutions are all timestamped so it should be obvious if someone solved the problem and then attempted some funny business to ride the coattails of another solution, right? I don't understand what the reason is to prevent people from reading the other solutions before making their own.
Log in to reply
I usually prefer to write as many solutions I can within Wednesday, since the solutions are sorted by the number of upvotes after that. But I've noticed that it seldom makes a difference. Often solutions submitted in Thursday/Friday get voted up to the top. Usually it takes me half an hour (of course it is not an invariant!) to write a proper well-formatted solution, and I never ever keep a solution private, even if I am sure it won't get any upvotes. :)
Log in to reply
I don't remember that being the case, but let's say it was. If it is the policy that solutions are viewable and that the solutions are time-stamped, there is not so much mystery as to whether somebody saw another solution and tried to hock it as their own.
A compromise could be to allow the key technique to be visible to people who've solved the problem. There is only so much time in a day and it would be nice to spend time on solutions that will help the most people or provide a missing insight rather than to unwittingly recast a line of reasoning that's already been well presented by another user.
Log in to reply
I've accidentally clicked that button twice...