Study: A Ford Escort will accelerate at more than twice the speed of a Ferrari F-50

According to a study performed by the Michigan Institute of Engineering last fall, a Ford Escort's acceleration capability exceeds that of many expensive sports cars. A few key phrases from the study follow:
1. "Despite conventional wisdom, the Ferrari took 2.34 times longer to reach 30 MPH than the Escort and a shocking 3.45 times longer in the quarter mile race."
2. "Beyond those stats, drivers consistently said that the Escort also handled better at every speed."
3. "It's clear to us that a Ford Escort with 4 wheels is a much better buy for a customer seeking performance than a Ferrari F-50 with 2."

Okay, yes, I made this study up (I'm not even sure if the Michigan Institute of Engineering exists). However, studies of this style are disturbingly common. In fact, I just read one today: Study: Single Parents May Do as Well as Two

The headline is effective in making people believe that the study showed that a stable, two-parent household isn't significantly superior to a single-parent house, in defiance of common sense.

However, if you actually read the article, the comparison is between a single parent who stays single vs. one who starts single but starts shacking up or going through failed marriages. In other words, the study started with a headline that's meant to surprise people but moves to actual details that anybody with half a brain already knew. Basically, it follows the exact same format as my car study above.

Okay, so readers of this blog might wonder: "How does that apply to programming or game development?" Well, this is kind of a stretch, but it applies to everything. The point of this post is to tell people: "Think", "Use your brain", and "Don't blindly trust the 'experts'". The world around you is teaching you to shut off your brain as movies get stupider, schools replace problem solving with rote memorization, and people who dare question the 'experts' are ridiculed.

Take a little time every day to shut off all of your machines and think. Make a point of reading material that challenges your current points of view. Learn to listen and understand before you even begin forming your response. That way lies wisdom, and we can all use more of that.

Quotation marks: Why the English rules are Wrong.

For those of you familiar with the English language rules regarding quotes, you know that you are supposed to put punctuation inside of the quotes. This is bad.

I'll start with a simple sentence; consider this example: Did you read the article "How David Beat Goliath?"

The meaning of the question mark at the end is ambiguous. Is the sentence a question, or does the article have a question as its title? In the English language, these are punctuated the same way.

What if you put that question mark on the outside of the quotes like this: Did you read the article "How David Beat Goliath"? Here, we've made it clear to the reader that the sentence is a question and the article title is not. According to the English language, that's wrong. According to me, the English language is wrong.

Where this gets messy is in nested questions. Try this sentence: The teacher just asked, "Which students read the article 'Why do we forget things?'"

I'm not even sure how that should be punctuated. The article and the teacher's statement are both questions, but that isn't clear from the punctuation. Given the choice, I'd use two question marks (one for each), but I'm pretty sure that doing so violates the language rules.

"So what?" you think. "I can still tell what's being said."

Yes, you can in this example. Let's modify it a little bit with a shortened quote: "You read 'Why do we forget things?'" Is the speaker informing the listener that they read the article, or are they saying it with a questioning tone? When writing dialogue, punctuation such as question or exclamation marks empower the writer to show the tone in which something was said. When the language makes it ambiguous what your punctuation belongs to, the writer's hands are tied.

It gets even better, though, when you get into the fine rules for quotes because not all punctuation is supposed to go inside of the quotes. A semicolon, for example, is supposed to go outside of the quotes. Why? What is accomplished by making arbitrary rules on what goes inside and what goes outside for people to remember?

All of the rules about quote punctuation placement could be entirely encompassed by a single rule: "If it's part of the quote, place it inside of the quotation marks. Otherwise, place it outside of them."

Thus, I've chosen to do all of my writing according to that rule, unless it's absolutely necessary for me to please some English professor. Join me, and perhaps we can turn the English rules into something more sensible.

Blog, which art my creation: I command thee to live!

Well, this brings forth the existence of my first blog. Basically, my nefarious scheme is to use this to post my latest thoughts on the creation of entertainment (books and video games, primarily).

Essentially, writing books and designing games of all sorts have been my lifelong hobbies since I was a young warthog, and I'm highly opinionated on both. I'm also highly opinionated on politics(libertarian), religion (Church of Jesus Christ of Latter-Day Saints), education (homeschooling), finances (live cheaply and stay out of debt), food (sushi, though that one tends to conflict with my previously mentioned finances theory), and water (definitely H2O). However, this blog will be primarily devoted to my hobbies of writing and game programming/design.

So, onto my first game-related post:

XNA is (almost) awesome.

For the uninitiated, XNA (stands for XNA's Not Acronymed) is a programmer's framework that allows them to create game for the Xbox 360. The philosophy behind XNA is to let the game's creators focus more on designing their game and less on the exact behavior of the hardware. Thus, a lot of long and difficult tasks that are normally part of game programming are basically done for you or at least made a lot simpler. The trade-off is that you lose performance, so the XNA games are never going to be as visually impressive as their C/C++ counterparts.

Now that that's out of the way, the question is "How good is it?" First, the positive:

XNA code is written in C#, which I find to be more sensible, easy, and straightforward to code in than most other languages. On top of that, XNA itself is fairly straightforward (at least, as much as it is possible to be in game programming, which is inherently quite difficult). I got more done in a few hours on XNA than a week on DirectX. On top of that, most of the same code will run on both Windows and the Xbox 360, which is quite pleasing.

So what are the negatives? First off, 3d animation. While trying to create my first meaningful 3d game, things were going fairly well for the most part. I had my objects in the game, my physics, my collision detection, etc. Then I tried to animate one of the models...

Instead of finding a nice Animation class that could look into your 3ds max files, find animation data, and convert it to something XNAish, I discovered that animation was practically a cut feature (at least as far as any web searches went). I found occasional third party libraries that were confusing as heck and even more confusing when I tried to understand what they were actually doing, but the whole theory of "Let the programmer focus on creating his game" seemed to be completely lost. The code samples I found seemed to be re-creating in code what the artist had already done in his modeling program. If you're making a 3d space shooter or puzzle game, I guess you don't really need animation, but otherwise...Well, animation is actually the reason that I shelved my 3d game and started on a 2d one. I'm actually making progress, now.

Well, there's my wall of text for the day. Fare thee all well