Ludum Dare 38 is currently hurtling through space on a direct trajectory with next weekend. Impact is estimated at 9PM on Friday, and the result will be a chaotic, harebrained, and fun-filled weekend. Coincidentally, it is also Science March slash Earth Day weekend. Here’s how we’re preparing.
First, for anyone unfamiliar…
Ludum Dare is one of the worlds largest and longest running Game Jam events. Every 4 months, we challenge creators to make a game from scratch in a weekend.
With so little time to work, preparation is very important. Only so much preparation is allowed, however. Any direct work on the game we’ll be making can’t begin until Friday evening, but putting our tools in order is allowed. The more comfortable we are with the tooling, the more efficiently we can work.
Here are some of my pet rapid development principles. They’re ever-evolving and some specific to Web games.
Rapid development checklist
1. No build
But they’re not free. Setup takes time, debugging occasional oddities takes time, and most importantly, the builds themselves take time. Eliminating all build steps is a big step towards optimizing the feedback loop.
Fortunately, browser support for ES6 has arrived, allowing us to run ES6
natively with no need to transpile. The only thing missing is the module
system, forcing us to write
<script> tags. It’s a small price to pay. On a
short-lived project like this, manual management of script tags is a cakewalk.
I do include a babel transpilation script to run before deploying the game, but it’s not needed during development.
Step two in optimizing the feedback loop is much easier. Use
Browsersync or LiveReload. When you save a file, the browser will
refresh immediately to reflect the changes. This will save you from invoking
Alt+Tab F5 five-hundred-thousand times during the weekend.
3. Focus on one thing at a time
With so much to do, staying focused is very difficult. I’m no good at it, but I hope Jared won’t mind me saying that he’s a paragon of focus.
Sticking to one thing at a time is simply more time-efficient than riffing. Avoid riffing. Riffing is stream of consciousness programming, hopping from one minor feature/tweak/bug to the next as soon as you think of it. It’s like Yak shaving but not nested. Also, unlike Yak shaving, riffing is entirely avoidable through discipline.
It helps me to write down (on paper) what I’m about to work on. “Create placeholders for all sprites”, for example.
4. The obvious ones
Know your tools. Get enough sleep. Drink enough water. Eat healthy. Take a short walk once in a while. Make science-themed signs during the week. Go outside and get caught up in the Science March (only valid during LD38 weekend!).
Hopefully the act of writing these down will influence our efforts this Ludum Dare weekend. See you all after the dust clears!