Getting past the 'coding random crap' stage?
category: general [glöplog]
spinor: looks like you're in the right direction. And the best is you don't seem to overestimate your time and dedication. Ambition and trying to get everything perfect the first time is the usual pitfall.
As for your designer he might not be as motivated as you are but that just mean you'll have to practice your leadership. Just try to keep your demo development in short bursts. At least that's what been working best with me so far.
And about tools, framework and shit: unlike video games, demos are pretty much just an excuse to experiment and do cool stuff. Sure being able to build on what you've previously done is a must, but also you need to be able to afford to trash everything and restard in a completely different way. Something we haven't seen so often with both ASD and MFX, so I guess code, even if good and reusable or ugly as hell, is not good enough of a motivation :)
As for your designer he might not be as motivated as you are but that just mean you'll have to practice your leadership. Just try to keep your demo development in short bursts. At least that's what been working best with me so far.
And about tools, framework and shit: unlike video games, demos are pretty much just an excuse to experiment and do cool stuff. Sure being able to build on what you've previously done is a must, but also you need to be able to afford to trash everything and restard in a completely different way. Something we haven't seen so often with both ASD and MFX, so I guess code, even if good and reusable or ugly as hell, is not good enough of a motivation :)
krabob: Karate looks like a very nice framework. are you saying it's not good for demos at the end of the day? are you for or against frameworks since developing Karate?
