search

exercism / problem-specifications

Shared metadata for exercism exercises.
MIT License
326 stars 541 forks source link

Simplifying HighScores #1456

Closed emcoding closed 5 years ago

emcoding commented 5 years ago

In the Ruby track, High Scores works great as an easy exercise for students, but the report method makes it a pain to mentor. We want to simplify it such that it doesn't need the giant if/else statement/extracted method/unreadable interpolation anymore.

Is this interesting for more tracks? In that case, we can change the canonical data. If it's only an issue in Ruby, we'll change it only there.

It's in ~@exercism/dart~ , @exercism/csharp @exercism/python @exercism/scala @exercism/delphi @exercism/javascript @exercism/fsharp ? (cc @pgaspar)

SleeplessByte commented 5 years ago

Not core (yet) for us (js/ts), but makes sense. I really like the simplicity of space-age and I think it'll helpt this as well so you can focus on the data structure instead of the formatting.

rpottsoh commented 5 years ago

I am fine either way. I may leave the report cases and flag them as optional.

ErikSchierboom commented 5 years ago

I'm also in favor of removing the report cases, for the same reasons as @SleeplessByte: it allows focusing on the data structure. It will also make reviewing/auto-approving easier.

pgaspar commented 5 years ago

This sounds great to me :+1: I'm ok with either removing the method entirely or finding a simpler replacement. Also found it to be a pain point for mentoring.

emcoding commented 5 years ago

Thanks all! @pgaspar we're going to tackle this, yes?

emcoding commented 5 years ago

Heads up: there's a PR up to remove the method, meaning the exercise focusses on array query methods. https://github.com/exercism/problem-specifications/pull/1459