Jay McGavren's Journal

Code Koans Pecha Kucha

The Geek ‘n’ Eat group at work had a Pecha Kucha day, and I prepped a quick presentation on learning Ruby/Clojure/Scala/Javascript through koans. (It’s also secretly about flow and how to achieve it in your coding.) I had recently learned how to record audio and export video from Keynote, and applied my newfound knowledge to do a Youtube-ready version:

http://www.youtube.com/watch?v=mG6NsCIRKAk

mountain.rb wrapup book...

The mountain.rb (henceforth to be known as Rocky Mountain Ruby) Chronicles are finally out. Pretty darn honored to occupy a page opposite Jim Weirich. (Many other illustrious names in there too.) Great wrapup of a great event.

Hmmm… How about a puzzle game where pieces are “if” statements, and the branch evaluates as soon as they’re “true”? That makes other statements true, causing them to evaluate, which makes other statements true… forming a combo - er - cascade.

CC-licensed Ruboto presentation...

Here’s the latest version of my Ruboto presentation… An earlier version of these slides was used by Charlie at JRubyConf 2010, and I updated them for my talk at Philly Emerging Tech.

Pre-rendered HTML

Source (for Showoff presentation software)

These are Creative Commons-licensed, so you’re encouraged to steal these slides for use at your favorite technology user groups!

The Reference Games Manifesto

A couple nights ago, I was playing Score Rush, a twin-stick shooter on XBox, and thinking what an exemplary game it was. Simple, but with highly polished gameplay. Something that other designers and developers could stand to learn from.

That started me wishing there was an open-source game in each genre that was playable and fun, but was first and foremost a reference for developers to learn techniques from. Web framework standards have reference implementations, why can’t games? All the needed infrastructure is out there - freely available game libraries in a variety of languages, GitHub and other source code sites for forking and improving on projects, and a great many motivated (but largely disorganized) open-source game developers. What if we joined forces to make something bigger than any one game?

And so resulted this initial draft of The Reference Games manifesto:

• We seek to meet the needs of both casual and experienced gamers where possible.
  • We believe that affordances for casual gamers should never be obstructive to experienced gamers.
  • In the rare event that needs are mutually exclusive, we strive to provide for both markets through multiple configurations of the same game.
• We prove our assertions through appropriate testing.
  • Example: A/B testing to prove that a particular control scheme reduces player error.
• Although we support innovation, we are a platform for sharing proven best practices first.
  • The reference game codebases can be forked and customized, but only proven techniques usable by a wide audience should be incorporated into core reference games.
• We value gameplay over graphics.
  • The majority of maintenance and development time should be spent on game mechanics.
  • We support users with low-power or low-cost hardware.
  • We allow graphical improvements through abstracted rendering interfaces.
• We are open.
  • We do not rely on proprietary frameworks or formats that are not freely available or could become unavailable in the future.
• We work with the tools most commonly used by the development community.
  • While respecting the openness principle, we choose the tools and languages most widely used by game developers.

I don’t know if I’ll have an opportunity to go anywhere with this, but it’s something I’d love to see. Any enterprising developers out there that want to take this and run with it?