Timeline for How can I avoid tons of if/else statements dealing with settings?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2015 at 0:41 | comment | added | david van brink | @akaltar (y) It's all tradeoffs. If it works, then, AOK! | |
| Aug 9, 2015 at 20:26 | comment | added | akaltar | Mine is a one man project, and as I realized, the main greatness of TDD comes from better teamwork. In small teams, where everyone knows what he has to do clearly, I believe TDD is just a slowdown. But with larger projects and more contributors it definitely is a great idea. | |
| Aug 9, 2015 at 13:20 | comment | added | david van brink | @akaltar On graphics code I agree with you. For game logic, physics engine, level loading and such, I've had good success with TDD. Doing so also guides you towards a cleaner separation of logic & graphics. "Testing slows us down" is a common fallacy. Here's one: jamesgolick.com/2007/8/22/… | |
| Aug 9, 2015 at 10:21 | comment | added | akaltar | I don't think unit testing is suitable for games. Its extremely hard to unit test graphics code, and thats one of the key points of games. I speak from experience, I have tried, but abandoned testing because it slowed down my progress by a factor of 10. | |
| Aug 8, 2015 at 16:30 | history | answered | david van brink | CC BY-SA 3.0 |