3 ms·
The problem with analytics I've experienced, is that they often aren't actually good at picking out the something they're targeting. They're actually good at pi
by stcredzero 14y ago
The problem with analytics I've experienced, is that they often aren't actually good at picking out the something they're targeting. They're actually good at picking out something like what they're targeting. When I use Pandora, I just get hollow dopplegangers of bands I like, not bands I actually like.
That said, and no doubt this will be controversial, I think there's great potential for Moneyball style statistical analysis of programmers. (Though there are significant organizational and cultural issues involved.)
The reason why stats work in baseball, is that there's ample empirical data: baseball players are up to bat, or have a chance to catch a ball again and again. Like baseball players, there are certain actions that programmers do again and again -- namely commits going to production. If one could get accurate stats on a large enough population, with automated metrics for function points and bugs, it should be possible to produce meaningful stats on programmers working with a given technology.
- hooande 14y agoThis sounds interesting, but I think the difference in the two situations is a repeatable experimental environment. In baseball every at bat is the same...a batter, a pitcher and 8 defenders. This lends itself well to statistical analysis. In programming, every commit is different and under wildly varying circumstances. I think the same logic might apply to the OP. Looking at a startup investment through the lens of a credit score makes some sense, but it seems more likely to avoid predictable losses than it is to identify the next facebook or google. As an aside, there's something I've always wondered about companies who predict the success of other companies...what score did they get from their own algorithm?
- stcredzero 14y agoThis sounds interesting, but I think the difference in the two situations is a repeatable experimental environment. In baseball every at bat is the same...a batter, a pitcher and 8 defenders. This lends itself well to statistical analysis. In programming, every commit is different and under wildly varying circumstances. You could argue this both ways. The situation at bat varies quite a bit. You can have different pitchers, different lighting, different wind speed and direction, different umpire, different situation on-base, etc... However, this all comes out in the wash because there are so many iterations. Programmers commit a lot. If you can get reliable data including bug rates for a given programming environment, I think you'd have good data.