Forums » Suggestions
every programmer read this
I've a suggestion. Every programmer on the project read this website, and steal some of the ideas.
http://www.extremeprogramming.org/rules/unittests.html
http://www.extremeprogramming.org/rules/bugs.html
http://www.extremeprogramming.org/rules/overtime.html
etc etc etc
yes i am arrogant.
http://www.extremeprogramming.org/rules/unittests.html
http://www.extremeprogramming.org/rules/bugs.html
http://www.extremeprogramming.org/rules/overtime.html
etc etc etc
yes i am arrogant.
oh i get it!
This belongs in Suggestions, why?
Facts:
1) XP is common sense.
2) Guild has excellent programmers.
So:
ananzi, do you have a purpose? At all? or are you just trolling?
Facts:
1) XP is common sense.
2) Guild has excellent programmers.
So:
ananzi, do you have a purpose? At all? or are you just trolling?
Hooray for three coders on a dev team! Hooray for the lack of a dedicated testing team and the time/money to do it fully!
Unit testing is a fine idea, and I'm quite sure that the devs do plenty of that for their low-level stuff. However, designing a unit testing suite for the underlying AI (which would probably only be used once, since I doubt that the AI will be changed much later. It's behavior, yes. The code? No?) is much more complicated- probably moreso than designing the AI itself. You can't just make assertions based on data, since this is a learning AI. Finding things like pathfinding bugs would be damned near impossible unless your unit testing suite constructs at least a partial universe, then populates it. Big bother. As for the rest of the XP stuff, I'm not a huge fan. I'm more of a fan of the "develop it until it works, test it, and fix it" method than the "hold staff meeting to decide number of hours to work to prevent overtime, then develop it, then spend twice as long on a unit test suite, then test it, then fix it, then write a separate test suite to detect recurrences of the original bug, then test it again, then continue". But to each his own, and perhaps the devs really are XP fans. Perhaps.
Nooooo, we've never ever heard of extreme programming before.
Anyway, our unit testing suite executes hundreds of tests in parallel, and then forms its results into natural language and posts messages here. We call it "releasing a patch".
Anyway, our unit testing suite executes hundreds of tests in parallel, and then forms its results into natural language and posts messages here. We call it "releasing a patch".
Awesome reply. *stunned* Just awesome.
lol go a1k0n
rotf. that has to be one of the best replies i've seen.
And it's cheap, too... LOL
i've just added this thread to my "a1k0n's funny posts" favorites folder along with the garbage truck.
Oooh, BURN!
Hehe. a1k0n ++