Sloppy code is easily refactored.
Sloppy architecture should be refactored - or if it's really flawed, rewritten. Keep in mind that there's no point in starting a rewrite until you know exactly what you're going to fix. Play around with psuedocode examples of interactions between the parts of your program until you're happy with the design.
Rewrites aren't always scorned: a prominent book on software development I read (sorry, don't remember the name) suggested that you "build one to throw away" when prototyping. The idea being that you can find out where all the challenges will be before worrying about architecture.
vinylpusher: you don't want to use Blitz's Sprites for particles, or much of anything. They each get their own surface. Surface counts will kill you much faster than triangle counts.
Sloppy architecture should be refactored - or if it's really flawed, rewritten. Keep in mind that there's no point in starting a rewrite until you know exactly what you're going to fix. Play around with psuedocode examples of interactions between the parts of your program until you're happy with the design.
Rewrites aren't always scorned: a prominent book on software development I read (sorry, don't remember the name) suggested that you "build one to throw away" when prototyping. The idea being that you can find out where all the challenges will be before worrying about architecture.
vinylpusher: you don't want to use Blitz's Sprites for particles, or much of anything. They each get their own surface. Surface counts will kill you much faster than triangle counts.