So long as you keep the old code on screen or printed out next to you as you re-code, you shouldn't go wrong.
This effectively will re-factor the code you already wrote but should train you into writing clean code at a first sitting. If you can see the old code and think "duh, should have done..." whilst you're sat in front of Blitz, it should turn out OK.
I break my projects up into multiple includes. For instance, my Spheres project has sound, graphics, particles, meanies and menu source files which are all separate and just get Included in spheres.bb (which then handles the main loops).
I recently scrapped the particle system and I will be rewriting it in a much better way (objects, types, 3D sprites). I will have old code and new code side by side on the monitor when I do it though.
This effectively will re-factor the code you already wrote but should train you into writing clean code at a first sitting. If you can see the old code and think "duh, should have done..." whilst you're sat in front of Blitz, it should turn out OK.
I break my projects up into multiple includes. For instance, my Spheres project has sound, graphics, particles, meanies and menu source files which are all separate and just get Included in spheres.bb (which then handles the main loops).
I recently scrapped the particle system and I will be rewriting it in a much better way (objects, types, 3D sprites). I will have old code and new code side by side on the monitor when I do it though.