= 27d567bc2d48d9f40e9ccc20ea370b15)
DaFranker comments on Natural selection defeats the orthogonality thesis - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (71)
One thing that I would like to see is + and - separated out. If the article received -12 and +0 then it is a looser. But if it received -30 and + 18 then it is merely controversial.
It's pretty much already provided, there's just that minor inconvenience of algebra between you and the article's vote counts, which IMO is a good thing.
As of 10/15, the article sits at -13, 24% positive (hover mouse over the karma score to see %).
That's 24x-76x = -13 -> 4x = 1:
6 upvotes, 19 downvotes, net -13.
If you have up-down=d and up/(up+down)=p -- these are the two pieces of information you get -- then:
(up+down)/up = 1/p
(up-down)/up = (2*up-(up+down))/up = 2-1/p
up = (up-down) / [(up-down)/up] = d / (2-1/p) = dp / (2p-1)
and then down = up-d = d(1-p) / (2p-1).
So knowing vote difference (= score) and vote ratio (= percent positive) is the same thing as knowing #up and #down -- except in the special case where the vote difference is 0, in which case you're always exactly 50% positive and you can't tell the total number.
It seems to me that making the hover-text say something like "+5 -3" would be strictly more informative, and at least as user-friendly, as having it say "63% positive" or whatever it says right now.
Of course there are any number of other changes it might be good to make to the code, and approximately zero effort available for code changes. But this one's a one-liner. (Actually, I think it's a two-liner; there are two things in strings.py that look like they'd want the same modification.)
Thanks for making it way clearer than I did. And yes, I forgot the 1:1 edge case.
As for modifying, a minor edit or bug similar to this is always 60% formulation and specification, 10% code modification, and 30% testing and making sure you're not breaking half the project. It sounds like you've already done around 75% of the work.
(deployment not included in above pseudo-figures, since the proportional deployment hurdles varies enormously by setup, environment, etc.)