{"assets":[],"author_link":"author\/puzzlem00n\/","author_name":"Tim Bumpus, aka Puzzlem00n","cat":"LD #24","categories":["LD #24"],"comments":[],"epoch":1344711840,"event":"LD24","likes":14,"metadata":{"p_key":"77785","p_author":"Tim Bumpus, aka Puzzlem00n","p_authorkey":"0","p_urlkey":"286636","p_title":"A Massive Postmortem","p_cat":"LD #24","p_event":"LD24","p_time":"1344711840","p_likes":"14","p_comments":"0","p_status":"WAYBACK","us_key":null,"us_name":null,"us_username":null,"event_start":"1345766400","event_key":"12","event_name":"LD24"},"source_url":"2012\/08\/11\/a-massive-postmortem\/","text":"

A wise man learns by the mistakes of others,\u00a0a fool by his own.<\/strong><\/p>\n

-Latin Proverb<\/strong><\/p>\n

You\u2019re all in for a treat, because I have been working on a HUGE post over the past few days just for you guys! It\u2019s basically a postmortem of all my experiences in game jamming, as a relative\u00a0amateur, and what I\u2019ve learned from them. I wanted to make this post for two reasons: to focus on how to make my own jamming skills better (I\u2019m the fool!), and, as a secondary goal, to help other people with their jamming (that makes you wise!).<\/p>\n

Of course, I\u2019ve done a lot of failing, so the post is a little long to put here! So, instead, I\u2019ve put in on my blog to trick you into giving me more hits- I mean, keep my post from taking so much space. With my luck, this will be off the front page in a few days (CURSE YOU FOLIS), but oh well.<\/p>\n

Here\u2019s the link<\/a>, and an excerpt from the summary near the end:<\/p>\n

So, here\u2019s a summary of all the lessons learned, or, as I like to call them, THE THIRTEEN COMMANDMENTS.<\/p>\n

    \n
  1. Plan ahead.<\/li>\n
  2. Do something you\u2019re comfortable with.<\/li>\n
  3. Let\u2019s admit it, there are stupid questions, you just shouldn\u2019t feel stupid about asking them.<\/li>\n
  4. Make someone play through the game.<\/li>\n
  5. Have all core features done by midnight on Saturday.<\/li>\n
  6. Don\u2019t use libraries if you find they need \u201cminor modification\u201d before doing what you want. Code it from scratch, or find a library that does exactly what you need.<\/li>\n
  7. Don\u2019t make a game without first knowing what you need to know to program it.<\/li>\n
  8. If you\u2019re sure you have absolutely no idea how to program it, don\u2019t try.<\/li>\n
  9. Don\u2019t overestimate yourself. Make sure your design is small and well-polished and does what it can well.<\/li>\n
  10. Have a very clear idea of how the game will turn out in the beginning. Especially when you\u2019re working with a team.<\/li>\n
  11. Know exactly what tools everyone is using. Seems obvious enough, but trust me, make sure you know them.<\/li>\n
  12. Don\u2019t\u00a0immediately\u00a0take someone else\u2019s solution for your bugs. Try and solve it yourself until all else fails.<\/li>\n
  13. Motivate yourself every second, before, during and long after the competition.<\/li>\n<\/ol>\n<\/blockquote>\n

    Tags: tips<\/a><\/p>","time":"August 11th, 2012 7:04 pm","title":"A Massive Postmortem","title_was_empty":false}