June 12, 2011: This post completely fraks up the calculation of David Smyth's Base Runs statistic. I've now fixed that, and added the data from 2009 and 2010. You can find all the updated tables here.
I'm a big fan of Sabermetrics, the use of statistical information to understand how baseball teams win games. Part of this is my love for the game, part my natural tilt toward numerical data, and part is that I've always enjoyed reading Bill James's work (full disclosure: he and I overlapped at KU, though we never met). Not to mention the fact that, from my desk, I can see several editions of both The Baseball Encyclopedia and Total Baseball.
But … in the old days, we judged batters by average (> 0.300 is good), home runs (> 30), and runs batted in (> 100). That was it. These stats have some problems: batting average doesn't tell you how many times a guy gets on base by walking, you can only bat in runs when your teammates are already on base, and as for home runs — well, OK, home runs are a pretty fair way to determine part of a players value.
The inadequacy of the traditional trio of AVG/HR/RBI led to the development of new measures for player performance: On-base percentage, slugging average
, runs created, etc., etc. The problem is that off the top of my head I don't know what's a good number for any of these statistics. OK, a slugging percentage of 0.900 is better than 0.400, but is a player who slugs 0.500 a power hitter, or just Joe Shlabotnik?





