Jump to content
Site Stability Read more... ×
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views

Ready, Fire, Aim

Sign in to follow this  


While listening to Steve Pavlina's podcast, "Kick Start Your Own Business", I heard him use the phrase "Ready, Fire, Aim" as a better approach to developing your business as opposed to "Ready, Aim, Fire". While listening to the podcast I realized how the same approach can be applied to people starting out in game development. I always see posts on forums with someone coding some sort of game "engine" and than get caught up in the design, trying to do everything the right way the first time, but never completing anything, I'm guilty of this as well. I think it is much better, at least when your working on your first couple of games, to just get a working, finished game. Having a finished game with crummy code is better than having a half finished game with great code.

Now I am not saying design isn't a good thing. It's important to have a solid design behind your games especially when the games become larger. The problem is that until you have completed a few games, how do you know what the best design is? There are many aspects to game programming and it can be hard to see how everything fits together at first. After you have completed a couple of games, you will start seeing the underlying connections which will make the design questions a lot easier to answer.

I think it is a mistake to start off trying to create a game engine. If you have never completed a game, don't try creating an engine. Just create a game, but focus on reusability where you can. Create a reusable Image class or Sprite class that you can use in another game. This is one of the major points of using Object Oriented design, reusability. By your second game you will probably have a bunch of components that you can group together to form a framework for further games. Let the "engine" evolve from your games, not your games from your engine. Sure, not everyting is going to be perfect, but you shouldn't always expect it to. Code can always be rewritten or redesigned later if it needs to be, and through this process you will have a couple of games already completed and the beginnings of a solid foundation to build future games off of.

I am changing my outlook on game development to better use the "Ready, Fire, Aim" approach. It's already helping me out with my own coding as I am actually working on a game and not just a bunch of code. This is only a slight shift in thinking but one that I feel is very useful.

Cross-Posted from Somewhat Structured Thoughts
Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!