7

From the beginning, I liked the impact measure (aka: people helped), but I must to admit that my personal case is pretty much inexact. A shadow grows between the datetime of the question and my answers. My impact measure take in account views made before that I answered.

My SO profile show ~405k of impact, but my linear estimation is less of ~140k.

Here are two examples:

Question: 1401 days from Q - 115k total views

Answer: 253 days from A - 20k estimated views (linear estimated)

Difference: 95k views

Question: 523 days - 240k views

Answer: 154 days - 70k views

Difference: 170k views

Total difference: ~405k - 95k - 170k = ~140k

So late answer should not be taken into account, or we need some kind of function to adjust this measure.

What do you think?

Personally I won't lie to my grandma.

Improve this question
0

1 Answer 1

Reset to default
6

I suspect the problem here is technical: there is no record of views over time, only raw views counter.

So, to be able to fulfil your request first step should be change the code so that it starts recording when each view took place. However, with millions of views every day (hour?) it means consuming lots of resources, not to mention development time required to make it all work quickly.

All in all, I think the current way is fine. So you don't tell the whole truth so your granny, just an estimation - that's why they added a ~ in front of the value and clearly saying "estimated number".

Improve this answer
1
  • 1
    Probably simpler to store number of views present at the time something was posted and subtract from current views to get reach.
    – Mitch Goshorn
    Jun 15, 2015 at 13:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .