I worked on an Xbox title many years ago, when I was still a bit inexperienced, and one of the requirements was that it had to run the attract mode for a week without fucking up. I accept the fact that we all make mistakes and make bugs, but that wasn't a mistake bug, that was consciously sucking out of laziness and not even bothering to gracefully handle failure. But even if you didn't have this experience, I'd have a hard time respecting any programmer who would have left that pool unreplentished and called it a finished project. My father got me the cheaper one and since then I've had a religious hatred of arbitrary limits in programs. One of the first programming environments that I used was MicroWorlds LOGO, and they had a cheaper version which allowed a maximum of 200 turtles, and a more expensive version that differed only in that the number of turtles was unlimited. It is shocking to me that someone set a hard limit on a pool and didn't add any code for replenishing it. I don't know if it is sped up or not, my only experiences with windows now adays are through my non-technical relatives computers which I'm asked to fix, but I was surprised at how quick windows appears to be in this video.īut what bothers me, is the bug itself. The video is amazingly well put together. I'd like to see more of this on HN, actually interesting technical content.

Guitar hero 3 dlc file numbers