Been there, done that, would not recommend
-
Its definitely a bad idea writing new code that builds up on your old code, that has not been tested properly, because you quickly have to start debugging multiple layer is code at once.
Should I finally write a game for my game engine?
Should I test its existing functionalities?
No, it's time to add a physics subsystem (which I'll be needing for some of the games anyways).
-
Should I finally write a game for my game engine?
Should I test its existing functionalities?
No, it's time to add a physics subsystem (which I'll be needing for some of the games anyways).
Testing means, that you dont trust your coding abilities. Dont be a pussy and dont test your code /s
-
There are dozens of us! But also, I have a masochistic tendency to update my old code to use the new language features and make it somewhat readable.
Shouldn't you write tests for your code before using the new language features though?
