Ad
  • Custom User Avatar
  • Custom User Avatar

    +1 for downvote. It's really unfortunate when solutions that are problematic have lots of best practices upvotes.

    I rather like the idea of upvoting best practice comments, rather than directly upvoting a best practice, as having a solution voted best practice doesn't really do much for most folks.

  • Default User Avatar

    +1 for downvote. I've seen a lot of inappropriate "best practices".
    I think it's a really shame.

  • Custom User Avatar

    What about the following alternative to downvotes: allow "Issue" comments on solutions.

  • Custom User Avatar

    +1 for downvote.

    I don't think it's enough to just add a constructive comment to a bad solution that has a tonne of upvotes. I doubt if a large number of users even read the comments.

    I've only been a member for a day and already noticed the problem described by others here.

    I like the idea of requiring a comment for a downvote, and I like the idea of requiring one for an upvote too. I find the solutions disappointingly devoid of discussion, this may help.

  • Custom User Avatar

    Upvote comments sound good, but you can get upvotes with "Wow, so short -> best practice", so I still think down-vote isn't a bad idea.

  • Custom User Avatar

    What about having a best practice upvote require either making a comment that's linked to the best practices upvote, or upvoting a best practices comment? I think that the best practice feature would be much more useful if we could see why a solution is considered to be using best practices.

    For what it's worth I don't think clever needs a similar system since it's usually self evident and it's not as important a vote as best practices.

  • Custom User Avatar

    It's a joke. They just submitted enough times for the "random()" call to return 10, but they said their lucky number was 10 so it looks planned.

  • Custom User Avatar

    @jhoffner conceptually, your solution doesn't make much sense - when you're storing the temperature, you add a timestamp to it which is the date at which the next-to-be-stored temperature was taken, not of the actual temperature you're storing. Also, you store a null value as the first temperature. Seems to me the test cases aren't very well written.

  • Custom User Avatar

    Working, now!

  • Custom User Avatar

    Try it now.

  • Custom User Avatar
  • Custom User Avatar

    Sorry, didn't know you could also resolve suggestions.

  • Custom User Avatar

    Do you want to mark this suggestion as resolved or whatever?

  • Default User Avatar

    Issue still persists. Edit profile > link acc to Github results in:

    Uh oh! Something went wrong! (500)

  • Loading more items...