I'm not sure that the math doesn't work out. I'd think that 80% of the part of the military that actively engages in combat is well below 5% of the population. I'd consider it obvious that psychopaths would be much more likely to join a group of people where they would be tolerated, perhaps even glorified while also giving them an outlet for their tendencies.
Exactly. The key difference is how advanced the statistics that matter are in the different sports. Only very advanced stats will really tell the story in basketball whereas it is much easier to see in baseball with just baseline stats. Most laymen take that to mean that watching games is the only way to tell when, in reality, they just need to get the right stats and formulas.
By most statistical measures, the Lakers are an elite defensive team. They allow only 0.458 efg% and 101 points per 100 possessions. I'm not exactly sure where that rates overall in the league, but I'd guess they are both in the top 15% or so.
The nice part about named params is that it can make your code more clear if you have a lot of parameters on a method... but you could do the same thing by introducing a parameter object and be as clear and more resistant to change.
Not that I agree with his proposal, but youre assuming that someone wouldn't pirate something that they weren't willing to pay money for. That almost certainly isn't true for a significant population.
The real failure that opened you up to this race condition is naming. Initial is not specific enough and thus colided with another variable, that was also not named specifically enough.
Although your point on efficiency stands (at least with data structures that have to reshuffle contents on deletion), the type of loop that you use has nothing to do with the order that you delete the elements. You could easily do something like:
while (MyControl.TabPages.Count > 0) {
MyControl.TabPages.RemoveAt(MyControl.TabPages.Count-1);
}
For loop are nothing more than while loops with:
(1) an assignment (int i = MyControl.TabPages.Count in this case)
(2) an extra command (i-- in this case) added to the end
Sure. Though if we're talking about efficiency, I would imagine that counting backwards would be slightly faster than getting the current count each time. Though in reality this depends on way too many factors - I imagine TabPages would be stored in cache and getting the count is just as fast as counting backwards. Micro-optimization and all that.
Regarding for vs while, I find the choice is important only in the intent they emphasize: while puts emphasis on the condition, whereas for puts the emphasis on the iteration. I think in this case the condition (that the list is not empty) is deserves more emphasis than the iteration through the elements of said list - hence why I find the while version to be more readable. YMMV and all that :)
Exactly. For example in JavaScript doing a something.length would result in re-counting the number of elements, while doing the loop in this style would efficiently store the count in a variable that is fast to access and manipulate. I suppose if you want to be a real optimization junky you'd also use --i instead of i--.
What do you mean by "relatively easy to create"? If anything, I'd say that an MMORPG is probably the hardest (and most time consuming) genre of game to create.
The man advantages of an RPG style MMO are simple gameplay mechanics, lag tolerance, low server utilization, cheap content, a built in learning curve, built in constructive player interaction, and diminishing returns on extreme gameplay. I could go into each of these to see why MMO golf / the sims / FPS / chess / poker / just about any other game type is much harder to adapt into an MMO framework. But my main point was not that it's easy to create a 3D MMO RPG just that RPG's naturaly work better in the MMO format than just about anything else.
I can appreciate continuancy of mind, but red squiggles shouldn't be a deterrant to that. Rather, it is simply saving you the step of compiling before giving you information. You can just as easily train yourself to not worry about red squiggles until you're finished with the task at hand.
As for variable naming, the better question is:
Why would you willingly choose less descriptive variable names when there are editors that will help you produce more readable code?
editors that will help you produce more readable code?
The problem is your editor helps you produce more code, readable or not. The goal is to produce a good program, not more code.
