The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.

I have often heard it stated that there are some writers whose primary goal in covering a subject matter is to learn enough about it before they can try it out themselves. Like a form of distance learning, through talking to the right people and discussing the right subjects, eventually one can garner enough knowledge in order to tackle a task first-hand. While I am willing to believe that these types exist, I do not consider myself to be one of them.

I have been writing about games in various capacities for approximately three years. Not much time at all, in cosmic terms at least. When I started, my hope was to become to a professional games writer –in any sector of the industry. As time has progressed, even over such a short period as these three years, I have begun to find myself being lured ever deeper into the mechanics behind making games.

I put myself off the idea with a variety of effective excuses such as:

Not knowing how to code (at all)

Not owning a Windows PC

Not owning a PC

Not owning a mouse

Having no tangible computer science background

Not knowing how to create art assets

Not knowing how to implement anything

Probably having stupid ideas

Likely having unrealistic goals

While many of those have remained the same, a few notable challenges have been overcome within the past few months.

Own a mouse

Took a short class in Python where I learned how to make a frame

I place those in order of their use up until now. The mouse is in a shoebox behind me. It's an electronic mouse, and not an animal. It turns out I still opt for a trackpad even when I no longer have to rely on it for navigation.

Strictly speaking, these are more akin to 'Choose Your Own Adventure' novels. Novellas, even. They're short and quick and easy to digest, but they're a heck of a lot of fun to make. In the short space of around a week or thereabouts, I created three of them. Here they are:

It's worth going ahead and taking a few moments to play through them. It won't take much longer than a half-hour for all three to be completed.

The most notable aspect is that, whilst all three are functionally the same experience, each entry iterates on the previous method. These are three experiences that took me approximately 4 hours to assemble, in total.

The joy of Twine, and what gives it serious value for anyone interested in game design, is the instant gratification that Team Meat's Tommy Refenes has described as being so crucial in learning's early stages in his Gamasutra piece 'How do I get started making games???'. I didn't even use that aforementioned mouse.

I have previously taken tutorials in Unity, confused myself with where to start in GameMaker, and entangled myself in a web of declaratives with Inform7.

If you've been doing as much reading as I did in order to prepare for designing that big first game, I implore you to take a break this afternoon, download Twine, and break the ground. It's January 10, 2013. I have released three games this year. What about you?