Is there a kind of rule to post only those answers which offer a solution with a needed time investment that is in good proportion with already available answers? So that a working answer may get downvoted just because other answers are much faster?
####
Context.
This is referring to How can I change the case of a Windows 7 user name?.
I got a downvote for a clearly working answer to the question "How can I change the case of a Windows 7 user name?"
Especially if you have a fresh system and you realise a small capitalisation mistake, my answer is straighforward help. Instead of changing the username capitalisation directly, you should rename your current user to some unneeded name, create a new user, switch to the new and delete the old. So easy. This would change your official Windows username capitalisation, which is the answer to the question, even if it is a lot of work and could be done just in a minute in the user preferences, admittedly.
What is more (but apart from anything said before), in my opinion, the question does not exclude changing the username path as well, even if it is not mentioning this directly. And that is done with this approach automatically. Even if the user did not actually want to find a solution for this, she might also just have forgotten about changing the username path as well. It should be mentioned at least. My answer thus adds value, in a very simple way, and then I ask myself why this gets downvoted.
Now the question.
Is there a kind of rule to post only those answers which offer a solution with a needed time investment that is in good proportion with already available answers? So that a working answer may get downvoted just because other answers are much faster?