Skip to content

Making the Haskell track more gradual #193

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

Closed
rbasso opened this issue Jul 10, 2016 · 6 comments
Closed

Making the Haskell track more gradual #193

rbasso opened this issue Jul 10, 2016 · 6 comments

Comments

@rbasso
Copy link
Contributor

rbasso commented Jul 10, 2016

Making the Haskell track more interesting for beginners #192
Making the Haskell track more gradual

Anyone would like to take the humongous task of solving at least part of this?

  1. Check what knowledge is needed to solve each of the exercises.
  2. Reorder the exercises creating the most gradual progression possible.
  3. Change and move some exercises to make it even more gradual.

If we did this at least for the first 20 exercises it would be nice. If we did this for the entire track it would be fantastic.

@rbasso
Copy link
Contributor Author

rbasso commented Jul 13, 2016

Comment from a user about robot-name:

This exercise was brutal! :)

I found the jump in difficulty from the last exercise to this one to be quite severe!

...were do you think we could put this exercise, to make this track more gradual?

...I would say it is not really any easier than the bank account question, so it should really be somewhere around there

@petertseng
Copy link
Member

I went through and tried to write down a few notes for each exercise. Each line has the exercise name, a space, then a list of notes. I could not be exhaustive, and for some exercise I was too lazy to figure out what to write so I only wrote "?"

Stars mean I think the exercise is quite involved.

I don't know how useful this list will be. It is likely it will be need to be improved and completed. I would say big things to pay attention to are the problem that use the IO monad, and stuff I marked with stars.

accumulate reimplement library, recursion, test enforces non-strict
allergies bitwise
all-your-base Maybe, math
anagram filter, String manipulate
atbash-cipher String manipulate
bank-account IO monad
beer-song repetitive String generation
binary we should deprecate soon, math
binary-search-tree make a data structure, recursion
bob String manipulate
clock math
connect searching, **
crypto-square String manipulate
custom-set make a data structure
difference-of-squares math
etl combine library functions
food-chain repetitive String generation
forth parser, **
gigasecond math, time
go-counting partition grid, **
grade-school make a data structure (kinda)
grains math, Maybe
hamming simultaneous iteration, Maybe
hexadecimal we should deprecate soon, math
house repetitive String generation
kindergarten-garden ?
largest-series-product ?
leap math
lens-person lens, if you just use the library maybe it's easy, maybe interesting learning about the types if you implement yourself, *
linked-list make a data structure, IO monad
list-ops make a data structure
luhn ?
matrix ?
meetup date manipulation
minesweeper count grid, *
nth-prime math, filter
nucleotide-count Either
ocr-numbers ?
octal we should deprecate soon, math
palindrome-products ?
parallel-letter-frequency parallel
pascals-triangle ?
phone-number Maybe
pig-latin String manipulate
pov searching, *
prime-factors math
pythagorean-triplet math
queen-attack ?
raindrops math
rna-transcription Maybe
robot-name IO monad, random
robot-simulator ?
roman-numerals ?
saddle-points ?
say ?
scrabble-score ?
secret-handshake typeclass to make it work with both Int and String seems tricky
series
sgf-parsing parser
sieve ?
simple-cipher String manipulate
simple-linked-list make a data structure
space-age math
strain reimplement library, recursion, test enforces non-strict
sublist reimplement library
sum-of-multiples math, filter
triangle math
trinary we should deprecate soon, math
word-count ?
wordy parser
zipper make a data structure, *

@rbasso
Copy link
Contributor Author

rbasso commented Jul 19, 2016

Thank you very much, @petertseng! 👍

I'll be forced to take another at each of the problems to rewrite test suites to fail-fast with rspec. It will be a good opportunity to complement your work. 😄

@kytrinyx
Copy link
Member

Also check out the blog post by @IanWhitney
http://designisrefactoring.com/2016/07/09/exercism-shouldnt-make-you-cry/

@rbasso
Copy link
Contributor Author

rbasso commented Jul 25, 2016

Great post! Thanks!

@rbasso
Copy link
Contributor Author

rbasso commented Sep 18, 2016

With the new config.yaml format (#274), there is no need to discuss categorization of the exercises here anymore. After that, reordering the exercises will not be so hard.

Considering that this issue is dead for more almost two months, I will close it so e can focus on what needs to be done now! #274

I anyone opposes, I'll immediately reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants