Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of Out of Scope opportunities #21

Open
Mwnesbitt opened this issue Sep 5, 2016 · 0 comments
Open

List of Out of Scope opportunities #21

Mwnesbitt opened this issue Sep 5, 2016 · 0 comments

Comments

@Mwnesbitt
Copy link
Owner

Mwnesbitt commented Sep 5, 2016

I'm very happy with the quick progress we made on shipping a tightly scoped project. The goal as described in the readme file was definitely achieved, but in the course of building this, a few possibilities for additional improvements were identified and I'll list them here in case I ever want to play around more with this project.

  1. Remove the cap of colors at 10. Getting to 36 or even 62 would probably be fairly easy.
  2. Improve/add to the library of codebreaking and codemaking strategies. Specifically, implement beSmart, as well as cleaning up/organizing the dontBeDumb family of strategies. Deeper analysis of the different runtimes for this would be very interesting.
  3. Implement a way to use nonrandom codes when simulating/iterating games-- run through all possible codes, e.g. (This would probably be done by adding to the codemaking strategies-- the improved increment guess function should be written to provide the guesses.)
  4. Error check user input by finishing and implementing helperfunctions.isWellFormed
  5. CSV name includes timestamp and the username of the computer that created it
  6. Play around more with file i/o: possibly create output.xlsx directly from the code.
  7. Rewrite the internal workings of the game to handle codes and guesses not as strings but as integers with a base of "colors." I would imagine this would really help with runtime of games because ints can just be added and a modulus applied if necessary.
  8. General cleanup-- the dontBeDumb suite is messy and so are some of the helper functions. You can consolidate some code, streamline some approaches, and also add better comments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant