{"action":"created","issue":{"url":"https://api.github.com/repos/exercism/x-common/issues/71","labels_url":"https://api.github.com/repos/exercism/x-common/issues/71/labels{/name}","comments_url":"https://api.github.com/repos/exercism/x-common/issues/71/comments","events_url":"https://api.github.com/repos/exercism/x-common/issues/71/events","html_url":"https://github.com/exercism/x-common/issues/71","id":69215971,"number":71,"title":"Subtracks, 2.0 exercises, tags","user":{"login":"canweriotnow","id":387693,"avatar_url":"https://avatars.githubusercontent.com/u/387693?v=3","gravatar_id":"","url":"https://api.github.com/users/canweriotnow","html_url":"https://github.com/canweriotnow","followers_url":"https://api.github.com/users/canweriotnow/followers","following_url":"https://api.github.com/users/canweriotnow/following{/other_user}","gists_url":"https://api.github.com/users/canweriotnow/gists{/gist_id}","starred_url":"https://api.github.com/users/canweriotnow/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/canweriotnow/subscriptions","organizations_url":"https://api.github.com/users/canweriotnow/orgs","repos_url":"https://api.github.com/users/canweriotnow/repos","events_url":"https://api.github.com/users/canweriotnow/events{/privacy}","received_events_url":"https://api.github.com/users/canweriotnow/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-04-17T20:56:14Z","updated_at":"2015-04-18T06:14:59Z","closed_at":null,"body":"Related to this [gitter convo][gitter1]\r\n\r\nAlso maybe related to #63 \r\n\r\nI've been thinking about the possibility of interest tracks or subtracks:\r\n\r\n**Example Case:** There's a lot of interest in logic programming and one of the popular things I see people doing is working through the exercises in [The Reasoned Schemer][trs] in Clojure [core.logic][logic]. Now that we have a [Scheme track][xscheme], making those exercises available in appropriate languages, with appropriate lib deps, would be a great way to work through them with others.\r\n\r\nI also like the idea of iterative approaches to problems in the above-cited gitter convo. I think this might be orthogonal to subtracks, but I figured this issue would be a good place to tease out those distinctions.\r\n\r\nAs for #63 - right after the discussion about subtracks, it occurred to me that a tagging system might be a really useful thing. Classification like focus/practice/challenge is one area, but tags could also cover topical areas problems address, like string manipulation, list comprehension, iteration/recursion, etc.\r\n\r\nTags could also cover exercises that fall outside CS instruction justification; e.g., I was thinking about how differently I would implement ROT13 in Ruby, Scheme, C, etc. ROT13 is of course, at this point, a historical curiosity, but I think there are probably other things that would make for an interesting exercise with odd trivia in the README, e.g.:\r\n\r\n```\r\nBack in the olden days of USENET, it was considered courteous to obfuscate potentially \r\noffensive posts with ROT13 \"encryption\", which simply rotated characters 13 places so \r\nA becomes N, B becomes O, C becomes P, etc.\r\n\r\nImplement ROT13 cipher for alphabetic characters, preserving case.\r\n```\r\n\r\nIt's not useful, but could involve character encoding, modulo arithmetic, etc., depending on the implementation. Things like this could be tagged `historical` or `curiosity`.\r\n\r\nAnyhow, just a few ideas on evolving both the granularity and scope of exercises on exercism.\r\n\r\nThoughts?\r\n\r\n[gitter1]: https://gitter.im/exercism/support?at=552fb77508c7a53a4a1d835a\r\n[trs]: http://mitpress.mit.edu/books/reasoned-schemer\r\n[logic]: https://github.com/clojure/core.logic\r\n[xscheme]: https://github.com/exercism/xscheme"},"comment":{"url":"https://api.github.com/repos/exercism/x-common/issues/comments/94133061","html_url":"https://github.com/exercism/x-common/issues/71#issuecomment-94133061","issue_url":"https://api.github.com/repos/exercism/x-common/issues/71","id":94133061,"user":{"login":"Dog","id":5172592,"avatar_url":"https://avatars.githubusercontent.com/u/5172592?v=3","gravatar_id":"","url":"https://api.github.com/users/Dog","html_url":"https://github.com/Dog","followers_url":"https://api.github.com/users/Dog/followers","following_url":"https://api.github.com/users/Dog/following{/other_user}","gists_url":"https://api.github.com/users/Dog/gists{/gist_id}","starred_url":"https://api.github.com/users/Dog/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Dog/subscriptions","organizations_url":"https://api.github.com/users/Dog/orgs","repos_url":"https://api.github.com/users/Dog/repos","events_url":"https://api.github.com/users/Dog/events{/privacy}","received_events_url":"https://api.github.com/users/Dog/received_events","type":"User","site_admin":false},"created_at":"2015-04-18T06:14:59Z","updated_at":"2015-04-18T06:14:59Z","body":"I put together a small problem to show what I was thinking regarding a problem that could be expanded upon. A couple ideas for expansion were changing requirements, expanding the feature set, a second customer, etc. I hadn't read any of pminten's ideas when writing the gist. \r\n\r\nI was thinking you could give a story for a bit of engagement. Having a customer also means that we can do things like suggest what may be best for them in nitpicking. The readme could then focus on what is going on in the problem conceptually.\r\n\r\nhttps://gist.github.com/Dog/a257729d6c2e99b6685a"}}