Please tell me that when you programmed for a living that you didn't do it for a nuclear waste disposal company.
First of all, thank you for insulting my ability to do my job, something I take pride in, based solely on the fact that I'm challenging a position you have taken which, as you have admitted, you've got no support for other than how you "feel".
So basically you've never thought about this issue before I mentioned it, did no analysis, conceded that of course it's theoretically possible, then came up with a strong opinion that it just didn't happen.
Sorry, but you don't get to take the high ground here. After all, I have looked into this before, you have done no analysis, you know my solution is theoretically possible, and you have a strong opinion that it just didn't happen. The only difference is WIS pays people money to make sure my solution is the one deployed (though obviously we can't know beyond a shadow of a doubt without seeing the code).
LOL. I used to be an EDP auditor, so I know a bit about how truly difficult it is to ensure that a constantly updated system is and remains true to spec. And yes, most of the programmers were incredibly naive about the whole thing.
How long ago was this? Software development is a young science, and QA/QC systems have undergone a pretty significant facelift even within the past decade. Unit testing, code reviews, bug tracking, etc. all handled by the programmers themselves with the intent of producing better code in fewer tries. Of course, I can't speak to the quality of programmers or QA/QC that WIS employs, but on the whole the science has advanced quite a bit, in case it's been a while since you were an EDP auditor. It can never be perfect obviously but at least there are systems in place now to add discipline to the task. Also, thank you for the gross generalization of all programmers as naive based solely on the ones that you had contact with.
Now, to the part where you aren't being holier-than-thou:
They uncover bugs all the time, some are new and some are old. Right now there's a thread in the forum about a possible Medical bug similar to the old Training bug. IIRC, the Training bug took about half a year to show up (as owners ramped up training budgets) and at least another half year for them to verify, isolate and fix after the first reports come in.
This is a fair example. Back then the game was young, the understanding of which systems were working and which were not was less known. Even then the problem was identified and solved in about a year's time, according to your estimates. I don't know when HBD launched, but it's been 3 years at least, right? No real evidence or even low grumblings have surfaced in that time, you're the first I've heard such an argument from. Apparently there are others who feel as you do, but I guess I've missed them somehow.
The issue is rather subtle - it's not that regular health players are getting too many major injuries, just that low health players don't seem to get as many as you'd expect. Since there aren't that many sub-50 health players to begin with, and many owners understandably shy away from them, most owners won't even be directly exposed to the situation. Unlike the Training bug, for example, it's not something that anyone can easily check out for himself - you've got to invest in acquiring such a player first. As it is, over the past couple of years I've heard several comments from other players that suspect that the algorithm isn't working properly. Perhaps you haven't been listening as closely.
This gets to the heart of the issue. We both seem to agree that a low health rating, on average, indicates a player will have more injuries over his career. Severity of injury is determined by random probability and a team's Medical budget. And so, the way it should work, as we both agree, is that a more frequent exposure to getting injured equates to a greater likelihood of suffering a major injury over a career.
The fact that there does tend to be a small sampling of the particularly low health players, makes basing assumptions about the inner-workings of the system being out of whack a little dangerous. If you go look at the 60-day DL in a world, for example, you'll see a fair number of "good health" players on there. You might start to think the system is out of whack. But of course, the percentage of "good health" players sitting on the 60-day is going to be much lower than the percentage of "poor health" players sitting on the 60-day, because there are significantly fewer low health players.
If you find players who play an entire career with 30-40 health, there's a really good chance you'll see a 60-day DL appearance if you check their DL History (assuming the owner was actually putting his injured players on the DL). On the other side of the coin, a large majority of 80-90 health players feature no such trip to the 60-day, even over their entire career. Sure you may sign a low health guy and he might stay perfectly healthy over a full 5-year contract. But over his entire career, minors and majors, it's almost a matter of "when", not "if", he'll suffer a 60-day setback. That is why I believe it is working as intended.
5/13/2011 10:43 AM (edited)