config.json: Assign and order problems by difficulty #402

petertseng · 2016-10-19T08:10:52Z

As part of the work in #274.

To discuss: Are all these difficulties right for us? I got lazy sometimes and looked at what difficulties F# track assigned them, since they are also functional and have all exercises except lens-person. there are some notable exceptions

bank-account is significantly higher for us since we use IO monad for it
our robot-name is significantly higher - we use IO monad
our nth-prime may be lower since we can be lazy
our accumulate/strain may be higher since we require laziness
our clock is higher - it introduces a typeclass

Should we strictly order the exercises by difficulty, or is there sometimes a situation where we want to send a harder problem before an eaiser?

petertseng · 2016-10-19T08:16:15Z

config.json

      ]
    },
    {
-      "slug": "sublist",


sublist as the third problem was an interesting choice... how has that worked out for us?

I think it was too hard to be at the start, because people don't have yet a good understanding of recursing.

petertseng · 2016-10-19T08:20:12Z

Increase difficulty of our robot-name (edited into PR desc). We use IO monad, and #193 (comment) indicates there is difficulty jump.

petertseng · 2016-10-19T08:23:17Z

Maybe I should insert the topics in this PR too so we can easily justify the placements. That involves combining our lists though, a lot of work right now.

rbasso · 2016-10-19T08:29:25Z

Feel free to leave the classification for later if you like. It's really a lot of work.

The dificulties and reordering are already huge contributions. Thanks! 😄

petertseng · 2016-10-19T08:29:30Z

Another approach I can take, if this PR is too confusing, is to first make one PR to assign difficulties to the exercises (which we can discuss). And then after we have decided the difficulties, we can figure out individual reorderings we want to do. That is probably most useful if we don't think we will strictly order by difficulty.

rbasso · 2016-10-19T08:32:56Z

Even if we decide not to order by difficulty, we can do it later.
There is really not reason to preserve the current order, because it is not good at all.

The only reason I can think to avoid reordering is if we intent to reorder everything again soon, so we two changes.

petertseng · 2016-10-19T08:33:15Z

config.json

    {
-      "slug": "list-ops",
-      "difficulty": 1,
+      "slug": "beer-song",


really? Is beer song really easier than house? Of the three, I thought the difficulty is house < beer song < food chain.

I am proposing we switch beer-song and house difficulties and thus positions.

If I remember correctly, in beer-song the paragraph is just a function of a number. But the paragraphs have a lot of small variations.
In house we have a cumulative song, which is not that hard in Haskell, but the repeating pattern is a little more complex to get.

That said, I don't really care about the order, but it would be nice to put all thee far from each order, so that people don't get tired of the same type of exercise.

I think that food-chain is the hardest by far.

petertseng · 2016-10-19T08:35:39Z

config.json

    {
-      "slug": "custom-set",
-      "difficulty": 1,
+      "slug": "simple-cipher",


this does have an IO monad, because of the random aspect. Thus, should we make it even higher than a 5? Compare against bank-account and linked-list both are 6.

Random is hard...specially if people don't know IO yet.

Maybe we are missing an exercise to introduce IO without other complications...like random or mutable state.

I'll move it to 6.

Maybe we are missing an exercise to introduce IO without other complications...like random or mutable state.

Hmm, any ideas on what we would do? Console interactoins seem simple but probably a bit hard to test. File operations a bit more complex.

Maybe package silently can do it, but I didn't tested it.

If it works we can choose an interesting exercise to change and print the results. It would be a good introduction to the IO monad.

petertseng · 2016-10-19T08:36:56Z

config.json

    {
-      "slug": "pythagorean-triplet",
-      "difficulty": 1,
+      "slug": "bank-account",


bank--account and robot-name (both IO monad) next to each other - is that OK, or should they be separate? is it good to have two consecutive to reinforce the concept, or apart so that people get a break?

Maybe having at least one exercise between exercises of the same type is a good idea.

OK, moved them apart.

petertseng · 2016-10-19T08:37:49Z

config.json

    {
-      "slug": "saddle-points",
-      "difficulty": 1,
+      "slug": "queen-attack",


a bit borderline on this one being a 6, it could be lower, maybe a 5. the math is not too hard, do have to print out the borad though.

Follow your instincts! 😄 👍

I decided to move it to 5, then.

petertseng · 2016-10-19T08:38:52Z

The only reason I can think to avoid reordering is if we intent to reorder everything again soon, so we two changes.

All right, I'll try my best to get something we like now, then, to reduce the chance of having to change it again later.

petertseng · 2016-10-19T08:39:43Z

config.json

    {
-      "slug": "connect",
-      "difficulty": 1,
+      "slug": "say",


I think say can be decreased. maybe even be a 6. It's not that bad...

Certainly! It takes a lot of work, but is not that hard.
connect is hard.

Yeah, down to 6 with you, say.

petertseng · 2016-10-19T08:40:36Z

config.json

    {
-      "slug": "zipper",
-      "difficulty": 1,
+      "slug": "lens-person",


lens-person 9 or 10? If you really want to understand the types, they can take a while to wrap your head around. But once you understand them the rest of the problem is not so hard.

humm...I would go for a 9.

As part of the work in #274.

petertseng · 2016-10-20T04:56:43Z

Okay, I'm done with this round of changes.

rbasso

Looks perfect! 👍

Merging...

petertseng commented Oct 19, 2016

View reviewed changes

config.json: Assign and order problems by difficulty

de29f79

As part of the work in #274.

rbasso approved these changes Oct 20, 2016

View reviewed changes

rbasso merged commit 8b50610 into exercism:master Oct 20, 2016

petertseng deleted the difficulty branch October 20, 2016 05:32

petertseng mentioned this pull request Dec 2, 2016

difference-of-squares: Last test may be too hard for beginners #449

Closed

petertseng mentioned this pull request Jan 6, 2017

grains: add topics to config.json, update difficulty exercism/go#430

Merged

Uh oh!

config.json: Assign and order problems by difficulty #402

config.json: Assign and order problems by difficulty #402

Uh oh!

Conversation

petertseng commented Oct 19, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

petertseng commented Oct 19, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

petertseng commented Oct 19, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rbasso commented Oct 19, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

petertseng commented Oct 19, 2016

Uh oh!

rbasso commented Oct 19, 2016

Uh oh!

petertseng Oct 19, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

petertseng Oct 19, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

petertseng commented Oct 19, 2016

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

petertseng commented Oct 20, 2016

Uh oh!

rbasso left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

petertseng commented Oct 19, 2016 •

edited

Loading

petertseng commented Oct 19, 2016 •

edited

Loading

petertseng commented Oct 19, 2016 •

edited

Loading

rbasso commented Oct 19, 2016 •

edited

Loading

petertseng Oct 19, 2016 •

edited

Loading

petertseng Oct 19, 2016 •

edited

Loading