Working code #3
Open
Working code #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
is a day and a half into using git - hey, I had it forked perfect the first time, did my commits, pushed back to the remote repository... went in to send the pull request and noticed that the instructions were written by Richard B. Then I realized you had forked from his original branch and saw that he was with Cox Media and jumped to a conclusion - deleted this fork, went and forked from him, repeated process, figured I was set. Now I hear I had it right the first time? Hey - that's only two strikes! Anyhow, hope you like the code itself. I know that actually using tables (models.py) was total overkill, the app actually zeros out the tables at the end of each game, but I figured it was a chance to show familiarty with Django's MVC structure. Also - hey, the presentation is plain jane, I didn't take the time to add any fancy front-end stuff, hoping you're more concerned with the classes and methods - the logic of the app. It's fine along those lines - I don't think anyone can beat it, anyhow - but I also think the decision making is too... mechanical. It's too much description of all possible moves and appropriate reactions, it would have been way cooler to come up with a general decision making algorithm or a couple that would apply to large sets of possible states. Something to think on. Maybe something where the AI looks at all possible upcoming moves two moves deep and responds appropriately. Anyhow, while the lack of fancy CSS and HTML bothers me not a bit, the possibility that there is likely a more elegant AI algorithm does - something I'll have to think on. Cheers! Derek Thompson
and updated AI. Test framework simply fills player's role and displays situations were player wins. Ran it on 1000 game loops until it stopped revealing flaws. Then ran it 100000 times. No wins. Looks good. Should have built test framework first. Cheers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thought all my command-line 'git commit -a' stuff was coming through to you, but now not so sure. Apologies - I'm new to Git, although I'm comfortable with subversion. Anyhow - code works, not the greatest interface, not really a "pretty html and css" guy to be honest. And although nobody will beat the AI, I'm certain that there must be a better decision-making algorithm - mine is quite mechanical, just works through possible board configurations, not really an... elegant solution. That is my thing - I'll probably obsess on this problem for a couple more days until I can find a more appealing solution.
Thanks for the opportunity!
Derek Thompson