commit-sudoku
commit-sudoku copied to clipboard
xiegeo
What's next?
What do we do after we finish this puzzle? This is an open-ended question for now. All suggestions welcome.
I did my PR's with help of my own sudoku solver that I wrote, I will post it at the end.
Let's do another one. Maybe a different size? A different game entirely?
Perhaps a variant of Sudoku? See: https://en.wikipedia.org/wiki/Glossary_of_Sudoku#Sudoku_variants
Btw the first one is done! 🎉
| 1 | 5 | 7 | 2 | 9 | 6 | 8 | 3 | 4 |
| 8 | 9 | 2 | 3 | 4 | 5 | 6 | 1 | 7 |
| 4 | 3 | 6 | 1 | 8 | 7 | 2 | 5 | 9 |
| 7 | 4 | 1 | 6 | 5 | 2 | 3 | 9 | 8 |
| 9 | 2 | 8 | 7 | 3 | 4 | 5 | 6 | 1 |
| 3 | 6 | 5 | 8 | 1 | 9 | 4 | 7 | 2 |
| 6 | 8 | 4 | 9 | 7 | 3 | 1 | 2 | 5 |
| 2 | 1 | 9 | 5 | 6 | 8 | 7 | 4 | 3 |
| 5 | 7 | 3 | 4 | 2 | 1 | 9 | 8 | 6 |
Good job everyone. It's gone better than I had hoped, except we didn't get into a dead-end, what would have been interesting to resolve.
I want to try something a little different next, starting in a new repo. I don't know what that should be yet.
There were some properties of the game that I liked :
- Easy to get into: everyone already knows the rules of Sudoku.
- Easy to contribute: no additional tooling needed to send a pull request. (This probably generates the most complaints, since we don't have any tools to make the table look better or easier to fill.)
- Cooperative, git merge friendly: concurrent contributions can be merged and stay valid most of the time. (This places a limit on the layout of the textual representation of the game states. I also don't see how pvp, imperfect information, or chance-based games could be fairly played.)
I see two directions to take with different trade-offs. Make the game more fun, treat git as a database where both game programming and player state lives, or keep the game simple as an aid to learn and experiment with git.
If anyone wants to create a commit-sudoku inspired repository, I will be happy to add links to it from the readme.