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

Create stub files for all exercises #150

Closed
kytrinyx opened this issue Aug 3, 2019 · 2 comments
Closed

Create stub files for all exercises #150

kytrinyx opened this issue Aug 3, 2019 · 2 comments

Comments

@kytrinyx
Copy link
Member

kytrinyx commented Aug 3, 2019

We have decided to require all file-based tracks to provide stubs for their exercises.

The lack of stub file generates an unnecessary pain point within Exercism, contributing a significant proportion of support requests, making things more complex for our students, and hindering our ability to automatically run test-suites and provide automated analysis of solutions.

We believe that it’s essential to understand error messages, know how to use an IDE, and create files. However, getting this right as you’re just getting used to a language can be a frustrating distraction, as it can often require a lot of knowledge that tends to seep in over time. At the start, it can be challenging to google for all of these details: what file extension to use, what needs to be included, etc. Getting people up to speed with these things are not Exercism’s focus, and we’ve decided that we are better served by removing this source of confusion, letting people get on with actually solving the exercises.

The original discussion for this is at exercism/discussions#238.

Therefore, we’d like this track to provide a stub file for each exercise.

  • If this track already provides stub files for all exercises, please close this issue.
  • If this track already has an open issue for creating stubs, then my apologies. Please close one as a duplicate.
  • Otherwise, please respond to this issue with useful details about what needs to be done to complete this task in this track so that people who are not familiar with the track may easily contribute.
@SaschaMann
Copy link
Contributor

SaschaMann commented Aug 3, 2019

@kytrinyx Does this refer only to the file itself (even if it's empty) or also to function signatures in the stub files?

If it just refers to the file, this track already has them.

@kytrinyx
Copy link
Member Author

kytrinyx commented Aug 3, 2019

We're leaving that up to the track maintainers. Essentially, if it seems like people are mostly fine with implementing function signatures etc in the language based on the tests or error messages, etc, then it's probably fine to leave it empty as you've done 👍

I figure, if we notice that some people are getting stuck, we could consider adding a bit more context to earlier exercises, and then wean people off it (as we do in certain other tracks).

I'm going to go ahead and close this one, as I think that for the Julia track what you have is good.

@kytrinyx kytrinyx closed this as completed Aug 3, 2019
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

2 participants