Birthed out of our Slack org, The Reformed Devs have begun monthly coding challenges for its members, hoping to encourage critical thinking and problem and solving and foster community. You can see our previous challenges here:
Given a random string of letters whose length is between 4 and 7, inclusive, what is the highest scoring valid word that you can make using the group of letters? Scoring is based on Scrabble letter point values (see data/letters.json). Word validity will be based on a dictionary included in the repo (data/dictionary.txt).
Inputs will be given as a lowercase string. Dictionary file is all lowercase as well.
Examples:
Given the input letters abc your max score would be 7. A=1, B=3, C=3, and there are multiple words that can be formed using all letters.
Given the letters iisq, your max score would be 10. I=1, S=1, Q=10, and none of the multi letter words that can be formed score higher than just Q itself.
What should be timed? Generally speaking, nearly everything. Historically the following are excluded from your timer: Importing libraries/modules, setting constants, setting test input, printing the solution. Everything else should be inside your timer, including loading the dictionary.
Running your solution should output your info in the following format: username, language, word formed, score, time in ms, notes.
Using the first example from above, example output might be: specs, Python3, cab, 7, 130, these are the notes.
Important: Make sure your solution can take an input. The letters to handle will be sent as a string in a BASH variable. See example folder for details on how this will work.
Each solution will be run 5 times with same input and the time and solution recorded. Any solution that doesn't submit the same score every time for the same input will be counted as invalid.
There will be 5 randomized valid inputs (i.e. each solution will be run 25 times.) The times will be averaged. Ranking will be based on average time. If your calculated highest score is not the same as the rest of the solutions, your solution will be counted invalid.
A dump of all solution data will be put into a JSON file in this directory, and the Leaderboard and Oops sections will be updated below with summary data.
Put each of your submitted solutions in its own directory at the root of the project. Any directory that is named alphanumeric-alphanumeric will be picked up by the test container, but general convention is use yourlanguage-yourname/handle.
Your solution directory should include the following:
build.shfile (only if you need to build/compile your solution)run.shfile (a shell file that has the command to execute your solution)- Important: Make sure your solution can take an input. The letters to handle will be sent as a string in a BASH variable. See example folder for details on how this will work.
- the file(s) needed to build and run your solution.
See the example directory for more guidance.
Note: You might need to update the Docker build file if your language is not yet supported (see below.) If you need help, ask in #monthly-challenge in Slack.
The Docker image is now moved to its own repo and is hosted on Dockerhub.
The image tagged 2019.10 currently supports these languages:
- C/C++
- Node 11
- Python 3.6
- Ruby
- Rust
If you want to add support for another language, you can make a PR to the Source repo referenced above. If you need help, come on over to the #monthly-challenge channel on our Slack.
You can build the container locally by running ./build_docker.sh.
You can run the container lcoally by running ./run_docker.sh after building the container.
You can run the tests locally (assuming you have all the language support installed) by running python(3) run_solutions.py.
If you only want to run specific directories on a local run (i.e. just test your solution), run python(3) run_solutions.py comma-separated,list-of,solution-dirs.
Test timestamp: 2019-10-08T13:54
Inputs: hdai, inerl, morqu, nhywc, uffvtd
| Author | Language | Word | Score | Time (ms) | Notes |
|---|---|---|---|---|---|
| plusuncold | C++ | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 5.56 | |
| pard68 | Rust | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 13.920847880000002 | Give me iter() or give me death |
| pard68 | Python3 | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 49.54075807999914 | snek can snek into snek |
| cco3 | javascript | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 63.8 | sparse arrays |
| cork | Node | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 63.8421604 | Put some FP and async on it |
| zombeej | Node | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 72.76000000000002 | small gainz at 10/8/2019 |
| specs | Python 3 | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 96.97626953125 | strolling down the yeet |
| Kyle Nweeia | Python 3 | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 101.32387483999949 | |
| basking2 | ruby | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 106.752978515625 | ARG: ["hdai"] |
| cco3 | javascript | dhai, liner, quo, why, duff | 8, 5, 12, 12, 11 | 161.28000000000003 | obscure |