The best part of application development is when you find out that it is critically flawed, and needs to be totally rewritten... Especially when that moment comes when you are presenting the app... And the best thing is that 5 minutes before that moment, the program was working perfectly... And then 5 minutes later, my 3D Engine became a 2D Sprite engine... And all I did was re-build it....
What Fun. After that, I Shift-Deleted the program, and started re-writing it from the ground up...
I have recently discovered that both the Flu and my Algebra teacher have exact the same effect on my health: it quickly degrades.
Well it's sod's law that something will always go wrong during a presentation
If there was a fundamental flaw then it seems your design process should have picked it up, but i assume you didn't do one of those, so you've only got yourself to blame heh
I'm really bad at doing designs too... as are most programmers i should think, much more fun to get stuck in with some actual coding but in the long run it costs you more time!
I don't really know where the *original* problem came from, only that it had to do with textures and that it caused some models not to be shown at all... And the best thing is - it ONLY showed up when built with MinGW for WIN32... Compile under Linux - Voila! works perfectly...
with Visual C++ EE - Voila! Works perfectly...
But what the problem lead to, when I found it... (not fixed it, mind you) is that on the next build all my models, except 1, were flattened out. So instead of a 3D engine... I ended up with a srpite engine...
I have recently discovered that both the Flu and my Algebra teacher have exact the same effect on my health: it quickly degrades.
RustyNail wrote:But what the problem lead to, when I found it... (not fixed it, mind you) is that on the next build all my models, except 1, were flattened out. So instead of a 3D engine... I ended up with a srpite engine...
Screenshot please? I would realy like something like this as a feature
Well make sure you're thoroughly prepared beforehand and have a few working backups that you can revert to if you need to, and recompiling at the last minute is probably a bad idea, especially on a different platform
dejai wrote:Jp you could say that taking more time with no design and fixing complex problems makes you a better "programmer" just a worse "developer".
That's a fair point
If you're going into the industry i guess you may well be a programmer and not a designer so you get told the design and just have to implement it but i would think that design skills would still be important as the designers may not be very good programmers so might overlook certain things that you have to cater for.
JP: heh, maybe that was my problem... but it's too late to think about it now
Anyway: I now have a clearly defined project: Make a Cube Clone
As if one needs many Cubes... I have until Friday to make an UML diagram of my planned engine... And then... Endless hours of thankless coding... and for what? to get a wimpy clone of Cube, delete it and start cloning Cube 2!
What fun.
I have recently discovered that both the Flu and my Algebra teacher have exact the same effect on my health: it quickly degrades.