It’s easy to mistake a model with the real world. For example, the authors argue that their model helps to disprove “General Equilibrium Theory.” It does no such thing – all it does is show that their code doesn’t abide by that particular theory.
” I realized something else – most casual players don’t want in-depth storylines, extensive dialogue, or overly difficult challenges.”
“Moving pieces around according to complex rules is fine for board game night but not a computer game.”
“I had a web page hosted on Heroku, being forwaded to GoDaddy, and grabbing data from mLab.”
“So there’s the cruel tradeoff – eloquence vs. performance.”
“Who would have thought that I’d have to pull out my old artificial intelligence textbook to make a simple game?”
“This blog entry is easily the most boring I’ve written. It’s also one of the most important.”
“I’m a great fan of mystery novels and treasure hunts, but recreating the essence of such a puzzle within a video game is very difficult.”
“This approach, as simple as it looks, has the potential to create extremely rich dialogue without resorting to long dialogue branching code.”
“If you create little one-scene casual mobile games with canned graphics and plugin-powered features, yes, maybe you can create a game quickly. Anything more complicated, though, and you need some coding skill.”
Source Code Thoughts 