knight10071

From your post, what you describe as accuracy, seems to be a failure rate. (This does not matter for the margin of error, but it's something to keep in mind.) This margin of error you're talking about is known as a 'confidence interval' in statistics. For this particular application, you'll want confidence intervals for the binomial distribution: http://en.wikipedia.org/wiki/Binomial_proportion_confidence_interval In this case, the 95% confidence interval is: 0.683 +- 1.96*sqrt(0.683*(1-0.683)/{number of trials}) = 0.683 +- 1.96*sqrt(0.683*(1-0.683)/477) = 0.683 +- 0.042 So, with 95% certainity you can say the failure rate is between 64.1% and 72.5% If you want to know, for example, how large your sample should be to know with 95% certainity, the failure rate within 1%, you solve 0.01/2 = 1.96*sqrt((0.683*(1-0.683))/n) (wolfram alpha says n=33269.9) Sorry but... What's sqrt? square root

From your post, what you describe as accuracy, seems to be a failure rate. (This does not matter for the margin of error, but it's something to keep in mind.) This margin of error you're talking about is known as a 'confidence interval' in statistics. For this particular application, you'll want confidence intervals for the binomial distribution: http://en.wikipedia.org/wiki/Binomial_proportion_confidence_interval In this case, the 95% confidence interval is: 0.683 +- 1.96*sqrt(0.683*(1-0.683)/{number of trials}) = 0.683 +- 1.96*sqrt(0.683*(1-0.683)/477) = 0.683 +- 0.042 So, with 95% certainity you can say the failure rate is between 64.1% and 72.5% If you want to know, for example, how large your sample should be to know with 95% certainity, the failure rate within 1%, you solve 0.01/2 = 1.96*sqrt((0.683*(1-0.683))/n) (wolfram alpha says n=33269.9)

99 ranged :D Thanks to Dat Booty, A Mace and Ezeei for coming :)

I'd like to share some of my experiences. I started with Visual Basic, which was pretty good for me. Made a lot of small projects with it and making buttons etc. is really easy with it. Then I learned Python though this: (http://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-00-introduction-to-computer-science-and-programming-fall-2008/index.htm Video lectures + exercises) Python has a ton of libraries for practically anything you can think of, from writing excels to reading xml files. If the friends you want to give the programs to have knowledge of programming, you'll prolly want to give them the source code anyway, so they can just download Python, it's not like it's big or anything. If you just want to show them stuff, http://www.portablepython.com/ . I have a little experience with C++ and the main difference between C++/Java and Python is development time vs time/resources used for running. If you have finally finished a C++/Java project, you compile and you can just run it whenever you want to. If you want to do projects in Python, you can easiliy write a bit of code, but it needs to be interpreted when you run it, which can cause slow down.

I think he's right, actually, it would be similar to swimming, except in, you know, air. I used to think there were people with huge control panels controlling all traffic lights in the city. This resulted in: - Pressing the button multiple times, because the controller had to get annoyed from that flashing light/annoying beep that he saw/heard when I pushed it. Therefore he'd let me go first. - Me saying that I understood why traffic lights were switched off at quiet times: The guys who controlled it would want a day off every now and then. (My parents still quote this to me to this day. I'm 17 and this was at like 4 xD)

Besides the fact it would take a huge amount of time to rewrite everything, I think you should consider the following: If my observations are correct, practically anything that is a desktop-application can be hacked. Hacked as in altering the game itself, not stealing passwords or any of that nonsense. I would gladly take the slowish performance and sub-par graphics over a bunch of hackers/scriptkiddies any day.