This repository has been archived by the owner on Aug 31, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 163
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SaschaMann
changed the title
julia: add notes on progression
Julia: Notes on progression
Dec 13, 2019
@SaschaMann I think this document could be placed in the |
SaschaMann
force-pushed
the
julia/progression
branch
from
January 16, 2020 17:59
12db6bd
to
7949d6f
Compare
SaschaMann
force-pushed
the
julia/progression
branch
from
January 16, 2020 17:59
7949d6f
to
ccbb044
Compare
Haven't done as many changes as I expected, so I think we can merge it. |
The CI failures are unrelated:
|
ErikSchierboom
approved these changes
Jan 17, 2020
BethanyG
added a commit
that referenced
this pull request
Dec 12, 2020
* First * Add : config.json authors & editor * Add : exchange file exchange_test / exchange * Fix : typo Line 2 from .exchange import * -> from exchange import * * Fix : Forder Name * Fix : Folder Name * Added example and instructions. (#6) added : currency-exchange/.meta/example.py added : currency-exchange/.docs/instructions.md * Added design.md (#7) * added design.md added : currency-exchange/.meta/design.md * Added hint.md (#8) Added hint.md (#8) * Add : hint.md (#10) * Delete .DS_Store * Add : hint.md (#9) Add : hint.md Solving Conflict * Add introduction.md (#8) * Fix: typo (#11) fix exchangable to exchangeable fix "Chandler want" to "Chandler wants" in instructions.md * Change File_name & Prettier (#12) * Fix : Prettier (#13) * Add : slug to config.json (#14) * Fix config (#15) * Fix introduction.md (#16) * Fix instructions.md (#17) * Fixed instructions.md Fixed grammatical errors in instructions.md based on BethanyG's review. Co-authored-by: Limm-jk <201602057@cs-cnu.org> Co-authored-by: Junkyu Lim <57378834+Limm-jk@users.noreply.github.com> * add testcase * Added problem "6. Calculate unexchangeable value" (#19) * Added new problem "Calculate unexchangeable value" Added modular arithmetic problem Calculate unexchangeable value * Added new problem "Calculate unexchangeable value" (example.py, exchange.py) Modified example.py, exchange.py * Modified Calculated unexchangeable value Modified `unexchangeable_value()` function's expected return type to be `int` * added new lines at the end of file * applied prettier on instructions.md Co-authored-by: Limm-jk <201602057@cs-cnu.org> Co-authored-by: Junkyu Lim <57378834+Limm-jk@users.noreply.github.com> * Add : Problem Design (#20) * Update languages/python/config.json we changed the concept name, so needed to update file. * Update languages/python/exercises/concept/currency-exchange/.docs/introduction.md * Update languages/python/exercises/concept/currency-exchange/.docs/introduction.md * Update languages/python/exercises/concept/currency-exchange/.docs/introduction.md * Update languages/python/exercises/concept/currency-exchange/.docs/introduction.md * Update languages/python/exercises/concept/currency-exchange/.meta/config.json we've decided to name the stub and test files for the concept and not the story. * Update languages/python/exercises/concept/currency-exchange/.meta/design.md minor typo * Update languages/python/exercises/concept/currency-exchange/exchange_test.py * Update languages/python/exercises/concept/currency-exchange/exchange_test.py * Update languages/python/exercises/concept/currency-exchange/.docs/introduction.md Co-authored-by: Yunseon Choi <science_co@naver.com> * Update languages/python/config.json removed arithmetic as a concept until we get the about.md file made. * Update languages/python/exercises/concept/currency-exchange/.meta/config.json reverting file name change and deferring to different PR. This is currently breaking a CI test. Co-authored-by: Yoggy <wjdek88@naver.com> Co-authored-by: Seunghun Yang <Yabby1997@gmail.com> Co-authored-by: Ticktakto <50654571+Ticktakto@users.noreply.github.com> Co-authored-by: Yunseon Choi <science_co@naver.com> Co-authored-by: wnstj2007 <43427152+wnstj2007@users.noreply.github.com> Co-authored-by: BethanyG <BethanyG@users.noreply.github.com>
OMEGA-Y
added a commit
to OMEGA-Y/v3
that referenced
this pull request
Dec 22, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't merge this, please
These are notes I took while thinking about how the Julia track's progression could go and what content the concept exercises might have.
I don't know if these will be useful to anyone else, but I find it helpful to see how others approach concept exercises, so I figured I might as well share my approach/notes.
If you're interested in contributing to the Julia track, perhaps you can add your ideas to it as well. The format isn't fixed or anything, feel free to add info in whatever way you want.
It will change frequently over time, when new exercise are implemented, issue arise, or new ideas/notes are written down etc. Having it on a separate branch but findable as PR seems a lot less noisy and easier to maintain than an issue. Perhaps we can merge it at some point when more exercises are implemented and it's more stable, but not quite yet.
This is not meant to be a proper roadmap like #1 or #2, it's focused on the progression only.
The markdown editor I use (Typora) live-renders mermaid-js blocks as flowcharts. Right now it looks like this: