"Readable" - is a too vague word. "Best practice"/"Clever" voting is not always objective, but having "Readable" button will lead to newbies upvoting bad code because "I don't know if this solution is efficient but I understand what's happening, so it should be good".

Yeah, I can attest to that, in retrospect I shouldn't have voted up things that I did. I have basically stopped voting as I just can't see voting up a solution until I have a much better grasp of the language to be able to judge between solutions, so perhaps in like a decade I will start voting again :). But yeah my idea of what is "best practices" has changed a lot and as I have only been coding for 2 years, will I am sure continue to evolve.

One of the things I have started doing is going on the leaderboard and finding people on there that are ranked high in the language I'm learning and following them. Then when you get to the solution page after I check out the top rated ones, I click on the "see solutions of people you are following". This way you often get to see quite quickly how someone who is a dan or a 1kyu coded the solution. I hadn't been using the "follow" feature, but it is definitely helpful.

The problem is, most people have a bad idea what "readable" is.

I mean, lots of people complain about short, golfy solutions but it's really the ridiculously long, imperative spaghetti code that should be put more blame on. Short solutions can be bad if by getting shorter they become either relying on tons of obscure tricks or inefficient algorithms, but shorter solutions have a fundamental advantage: they're faster to read. I want to read a 1-line code than reading some 20+ line code some people can write for just a simple thing, just because I can read less.

(Not like it'd stop people making passive-aggressive disagreements on "best practice" anyways. Acquiring a good taste is arguably even harder than doing katas.)

Best Practice should be readable

Me too. Mistakes make me sad.