Comments on: The illicit thrill of rapid prototyping http://acornheroes.com/2009/07/the-illicit-thrill-of-rapid-prototyping/ iPhone Development from the Ends of the Earth Thu, 19 Jan 2012 09:23:01 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Rapid Prototyping Rule #5 - Acorn Heroes http://acornheroes.com/2009/07/the-illicit-thrill-of-rapid-prototyping/#comment-440 Rapid Prototyping Rule #5 - Acorn Heroes Wed, 30 Sep 2009 20:44:28 +0000 http://acornheroes.com/?p=199#comment-440 [...] your think-code-test cycle.  Save the efficient coding for production, right now is a time for rampant hedonism. :Rapid [...] [...] your think-code-test cycle.  Save the efficient coding for production, right now is a time for rampant hedonism. :Rapid [...]

]]> By: Risk Driven Development - Acorn Heroes http://acornheroes.com/2009/07/the-illicit-thrill-of-rapid-prototyping/#comment-166 Risk Driven Development - Acorn Heroes Thu, 06 Aug 2009 10:54:46 +0000 http://acornheroes.com/?p=199#comment-166 [...] Rapid prototyping is a great way to prove your basic game design is sound. [...] [...] Rapid prototyping is a great way to prove your basic game design is sound. [...]

]]> By: George http://acornheroes.com/2009/07/the-illicit-thrill-of-rapid-prototyping/#comment-110 George Mon, 13 Jul 2009 21:47:21 +0000 http://acornheroes.com/?p=199#comment-110 Noel - I agree that building the prototype helps avoid writing unnecessary 'real' code. It really is time well spent, even though it's designed from the outset to never see production. Hi Elliot, thanks for the comment. Obviously it's a case of choosing the right method of attack for a given problem. I find that even my best ideas normally end up changed and improved after being given to other people for feedback - and that's why I try to prototype as fast as possible. And as Noel says, it's great fun. The Global Game Jam (http://globalgamejam.org) was a great example of this - our team of about 12 people built 3 games in 48 hours - it was a blast. Noel – I agree that building the prototype helps avoid writing unnecessary ‘real’ code. It really is time well spent, even though it’s designed from the outset to never see production.

Hi Elliot, thanks for the comment. Obviously it’s a case of choosing the right method of attack for a given problem. I find that even my best ideas normally end up changed and improved after being given to other people for feedback – and that’s why I try to prototype as fast as possible.

And as Noel says, it’s great fun. The Global Game Jam (http://globalgamejam.org) was a great example of this – our team of about 12 people built 3 games in 48 hours – it was a blast.

]]> By: Noel http://acornheroes.com/2009/07/the-illicit-thrill-of-rapid-prototyping/#comment-109 Noel Mon, 13 Jul 2009 10:49:09 +0000 http://acornheroes.com/?p=199#comment-109 Rapid prototyping is crucial to any good game (because you're going to make 10 prototypes before you find a good idea). I also love the thrill of programming really fast and getting lots of stuff done. And frankly, I've learned a lot from programming that way. It made me realize that a lot of the things I thought I needed in "production" code, I really don't. And if I do, I can always refactor them. Have a blast! This is one of the most fun parts of the process! Rapid prototyping is crucial to any good game (because you’re going to make 10 prototypes before you find a good idea). I also love the thrill of programming really fast and getting lots of stuff done.

And frankly, I’ve learned a lot from programming that way. It made me realize that a lot of the things I thought I needed in “production” code, I really don’t. And if I do, I can always refactor them.

Have a blast! This is one of the most fun parts of the process!

]]> By: Elliot http://acornheroes.com/2009/07/the-illicit-thrill-of-rapid-prototyping/#comment-107 Elliot Mon, 13 Jul 2009 06:19:47 +0000 http://acornheroes.com/?p=199#comment-107 I think I'm pretty good at imagining a game in my head, and determining that way whether it would be fun. When I write code, I'm usually somewhere in the middle; I'm coding really fast, but not so fast that the code must all be thrown out before production. The code is usable, but it will need to be gone over at least one more time to make sure the hacks are ironed out. But much of the code does make it into the final version, so I can feel happy and productive all along. I think I’m pretty good at imagining a game in my head, and determining that way whether it would be fun. When I write code, I’m usually somewhere in the middle; I’m coding really fast, but not so fast that the code must all be thrown out before production. The code is usable, but it will need to be gone over at least one more time to make sure the hacks are ironed out. But much of the code does make it into the final version, so I can feel happy and productive all along.

]]>