NatPat

  1. I’ve realised what my problem is.

    In short, it’s most game devs’ problem. Not being able to finish things. But it’s not only that I’m not able to finish a complete game, it’s the fact I’m not able to finish the little parts of the game as well.

    I often find myself charging in to add a feature without really thinking through how I’m going to implement it. Then, it turns out that it doesn’t quite works, but works some of the time. I think “That works well enough, I’ll come back to it later” and leaving it half done. So right now, I basically have a whole load of half finished features, and I have no idea what needs doing.

    Also, I’m far too concerned with optimization and proper coding practises. I worry about whether I should use getters and setters, whether I should rewrite that as a function or have that as a static variable, etc. I need to stop doing that too.

    Oh. And I don’t comment my bloody code. That probably doesn’t help.

  2. 1 Comment

    1. nick says:

      I’ve found a good cure for wanting to make pretty-looking code rather than games is to look a the source of finished games. I enjoy browsing John Carmack and Notch’s code, specifically.

      Slightly relevant article:

      http://notch.tumblr.com/post/15782716917/coding-skill-and-the-decline-of-stagnation

      As for commenting, check out the source code for QuickDraw (on the original Mac) if you get a chance… those comments are a work of art.

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>