http://www.perlmonks.org?node_id=174253


in reply to 'Experience: non yet' is wrong

From an engineering point, I'm sure that the code that returns that string simply examines your current experience value, instead of your entire experience history. While it might be more accurate to include that search in the code, I would recommend against it because of the presumed hit on performance it would impose for all home node hits.

Update: A patch has been applied to the relevant section. When you have no XP, the system now reports, "None earned."

I'm sure that as you continue to participate, you'll work past this little problem. It might be worthwhile to take a gander at Turnstep's home node for links to other nodes outlining some participation strategies.

Hope this helps...

--f

Replies are listed 'Best First'.
Re^2: 'Experience: non yet' is wrong
by particle (Vicar) on Jun 13, 2002 at 17:54 UTC
    From an engineering point, I'm sure that the code that returns that string simply examines your current experience value, instead of your entire experience history
    might a check on current xp value and number of posts be a closer approximation to xp history without sacrificing (much) performance?

    i don't know much about what goes on here behind the scenes, but i can't imagine this solution would cause a noticable performance degradation. i would argue, however, that this is an edge case, and i'm sure there are more important issues which affect the experience of a larger number of users--there would be little gain from this change.

    ~Particle *accelerates*