An assortment of commonly asked questions
Exercism was originally founded by Katrina, a polyglot developer and winner of the "Ruby Hero" award who accidentally became a developer while pursuing a degree in molecular biology. She began nitpicking code back in 2006 while volunteering at JavaRanch, and got hooked. When programming, her focus is on automation, workflow optimization, and refactoring. She cares deeply about open source and contributes to several projects outside of Exercism.
In 2016, Jeremy joined as co-founder, and he is currently Exercism's CEO. Jeremy is a social entrepreneur and software developer, passionate about equality and creating opportunity for everyone. In addition to Exercism, he is the co-founder of the Wellbeing and Teambuilding platform, Kaido.
In addition to this leadership team, Exercism has a small full- and part-time team, and is supported by thousands of wonderful volunteers who have crafted the various language tracks and exercises that made Exercism so popular.
Despite being one vowel away from "exorcism", the name has nothing to do with demons or fixing "evil code".
Instead, it's a pun on exercise. The way Katrina came to think about each exercise is that they are small, trivial, and seemingly simple. However, when it comes to solving an exercise, the devil is often in the details. In other words, that simple exercise is suddenly more challenging once you think about the finer details.
You're in luck. Here's a step-by-step guide to get you started.
If something is still unclear for you or not working then it might be the same for others so we'd appreciate you letting us know. Refer to Opening an Issue below for instructions on how you can help us help others.
This means that GitHub isn't willing to verify who you are. That can be because you chose not to give permission or it might be because your GitHub account is not properly configured. A common problem is that you haven't verified your email address on GitHub. You can check that in your GitHub email settings.
We now have a dedicated Teams site.
The new site has a brand new command-line client, and also needs some extra metadata for your exercise. Read about how to upgrade your command-line client and migrate your solutions for the new site.
If that doesn't help, or you didn't use the old version of the command-line client, please read through the command-line client Walkthrough. If that doesn't help either, open an issue and we will help you get it sorted out.
The version command
exercism version outputs the running version of the Exercism command-line client. By running the version command with the latest flag
exercism version --latest you can check if there is a newer version available.
exercism upgrade will upgrade to the latest available version of the command-line client if one is available.
If you are receiving permission denied errors when trying to upgrade the command-line client, chances are the binary was installed via a system package manager (e.g Homebrew) or has been installed into a directory that you no longer have write access to.
If your command-line client was installed via a package manager please use your package manager for upgrading, as opposed to running the
exercism upgrade command.
If your command-line client was installed manually, please check the path of the Exercism command-line client
which exercism on Linux and MacOs,
where exercism on Windows and ensure that the returned path is a directory you created. If so, use the tools provided by your system to change the permissions of the directory to grant write access to your user and trying upgrading again. If you are not sure if you created the directory, or the returned path is a system path, please use your system tools to uninstall the command-line client and reinstall using the interactive walkthrough.
Prior to version 3.0.5 of the Exercism command-line client, there was a bug in the upgrade command that would replace the command-line client binary file with a single text file causing the "16-bit MS-DOS Subsystem" error. To resolve this issue remove the corrupt binary and reinstall the command-line client using the interactive walkthrough.
While wait times can be longer than normal for a number of reasons (number of mentors, time of year), it can also appear that the queue is not updating. This is not unusual and you should see movement fairly soon. If you your wait is far longer than the average, refer to Opening an Issue below.
The website only shows mentors who have provided bio information for the website, not the actual number of mentors who are actively reviewing solutions. Rest assured, there are mentors working through their queues so hang in there!
There isn't a way to delete submissions so just submit the right file and it will show up as a new iteration in the queue. Feel free to leave a note for your mentor with the original submission clarifying what happened.
Please check our Code of Conduct for more information about our expectations of conduct. If you would like to report something, please reach out to us at firstname.lastname@example.org and we will try to fix or resolve the issue respecting both you and your privacy.
There are a few different ways - becoming a mentor, managing a language track or reporting (or addressing!) issues on GitHub. You can see more on the How to Contribute page. Version 3 of Exercism is also being built right now and needs lots of help. The v3 repository has more information.
A new language track gets created when a member of the community takes the lead on it and becomes a maintainer of the track. If you'd like to get involved in helping set one up, there are instructions here.
Version 3 of Exercism is being actively worked on, which means that contributors and maintainers are splitting their time between the current version (V2) and the next.
Before submitting an issue, be sure to check the relevant GitHub issue tracker to see if it has already been reported or resolved:
You can search through issues (remove the
is:open filter to include closed/resolved issues). Try a few different keywords.
If your problem hasn't been resolved or reported, then create an issue in the appropriate repository by selecting the green New issue button.
Make sure to include the following information:
exercism troubleshootcommand (for CLI issues)
If your issue pertains to an exercise in your language track, then please find the correct language track from this list and submit an issue there. Please specify if the issue is with the instructions or something language specific, using the template below.
If you have spotted a typo or if you have a suggestion for clearer language or instructions on the general website, then create an issue for Exercism Website Copy with the following information: