-
-
Notifications
You must be signed in to change notification settings - Fork 556
Is "write a program" accurate? #321
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
Comments
Perhaps "write a program" is the most generic way to address this? In the case of Ruby, I don't think I have yet to see a "Write a method" request, on its own, the final result is usually a class or a module, and many solutions don't require either, which is perfectly fine with me. It leaves the implementations open. Most generically, it may be "write instructions" to accomplish something. Once you ask for a function or procedure or method, you are probably being too specific, even the tests in many cases may be considered too specific, driving a certain way to solve something, which may be impossible to avoid, or just may be hard to avoid. |
What were if we ask for writing a library? This leaves everything open KOTP [email protected] schrieb am Sa., 6. Aug. 2016 12:20:
|
"write some code"? (Library sounds big and scary.) |
"Write code" sounds cryptic... just kidding. But yeah, the same "generic" flavor. |
I agree that library seemed potentially too large in scope. It's admitted to me that there are some tiny libraries, but maybe such a thing would not be as apparent to students. "Write code" seems suffciently generic. I think I would prefer it to "write a function". Here is another possible suggestion I have: Just remove the words completely. As an example, binary-search, before:
Binary search, after:
Seems to avoid duplication if every exercise has "write code" in common |
I agree with this, the removal allows the "obvious" interpretation regardless of terms the individual user should choose to replace with the implied statement. We don't care if they write it or craft it or conjure it, whatever it is, as long as the tests pass and they get the learning experience from it. (And even the tests passing are only a guide and a common reference, in their experiences context.) |
I like the idea of removing the words where possible, and if not, go with a super generic "some code" to avoid the but this is not an X argument. |
Here's a PR for this: #528 |
Removes "write a program" from descriptions to address #321
Looks like it was merged in, so closing. |
Thanks @kotp I forgot to close this. |
No problem. Don't forget that if there is a "fixes #000" in the commit, it will do so automatically when they are brought in. |
Thanks for the explanation @kotp. I had "addresses #000" in the commit, so it didn't pick that up as a keyword. |
Pull Request exercism#775 prepended a problem's blurb to its description. This resulted in a few descriptions having obvious duplication in the first few lines. This PR reviews all descriptions and: * Removes gratuitous duplication. * Ensures the first line does not exceed 80 characters. * Fixes a few spelling/grammar errors. * Re-arranges a few descriptions for clarity. * Removes a few occurrences of 'write a program' Refs: [PR 775](exercism#775) [Write a program](exercism#321)
Pull Request #775 prepended a problem's blurb to its description. This resulted in a few descriptions having obvious duplication in the first few lines. This PR reviews all descriptions and: * Removes gratuitous duplication. * Ensures the first line does not exceed 80 characters. * Fixes a few spelling/grammar errors. * Re-arranges a few descriptions for clarity. * Removes a few occurrences of 'write a program' Refs: [PR 775](#775) [Write a program](#321)
We have a lot of descriptions that say "write a program". As exercism/exercism#2746 explains, this may set up a wrong expectation from students that they are writing e.g. something with a main function (or equivalent entry point in language of choice).
But it seems that most tracks I've seen simply ask the student to write a function. Most languages then verify the behavior with unit tests against that function.
In the interest of setting up expectations correctly, shall we replace "write a program" with "write a function"?
Things I would like to check before doing that:
Anything else I'm missing?
Appendix:
The text was updated successfully, but these errors were encountered: