Skip to content
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

Allow users to self-identify themselves as newbies, experts, etc. #16

Closed
ryanplusplus opened this issue May 18, 2016 · 11 comments
Closed

Comments

@ryanplusplus
Copy link
Member

ryanplusplus commented May 18, 2016

Many of the submissions I review are people from my office that I know personally. I've found that I tailor the types of review comments I make based on what I know (or at least suspect) they're looking to get out of exercism. I can't usually make the same adjustments for the vast majority of users on exercism, so I try to limit the types of comments that might be appreciated by an expert but could be discouraging for someone who is just starting out.

If there were some way to identify yourself and your goals with a badge, label, etc., I think it would make it easier for submitters to get kind the feedback they're looking for and for reviewers to make more effective suggestions. It may also make it easier for newbies to become reviewers because they can focus on reviewing submissions from people they can relate to.

Thoughts?

@petertseng
Copy link
Member

I would see if there are any prior takeaways from exercism/exercism#2164 and exercism/exercism#2594 worth mentioning here; I do not yet have time to evaluate these myself and/or contribute new thoughts to this discussion; will be next week at the earliest before I am able

@ryanplusplus
Copy link
Member Author

Thanks @petertseng, I hadn't seen those issues.

I think this is pretty clearly related to exercism/exercism#2164, but focuses more on what the user is looking for than declaring mastery to short-circuit the requirement to actually do the exercises.

I think it's more or less a duplicate of exercism/exercism#2594, but that was closed as a duplicate of exercism/exercism#2164 which I think has important differences. So... :)

@petertseng
Copy link
Member

I see. It seems clear to me now that when I suggested the two issues may be duplicates, I only looked at the end result and not the reason why the result was wanted. Indeed you are right that the reasons for requesting the change are different. Nice catch.

@kytrinyx
Copy link
Member

Can we extract the main ideas from both of those issues here, close both and then figure out what the best action item(s) would be to actually address the underlying issues? Then we can create new, focused issues that are easier to tackle.

@ryanplusplus
Copy link
Member Author

I haven't forgotten about this, but I want to quickly add that the inclusion of newbie and experienced badges/tags/whatever here is intended to gel with these two "paths" for onboarding users as discussed in #18.

@kytrinyx
Copy link
Member

Having thought more about this I think it's incredibly important that we do this, in particular because the kind of feedback you typically are looking for is different depending on your context. I watched a talk by Alex Harms last week and they mentioned that great feedback is information intended to help the person receiving it achieve their goals. For that to work you have to have some idea what their goals are.

@ryanplusplus
Copy link
Member Author

I think the two tickets are different enough to stay separate.

The goal of this ticket is to enable giving and receiving better feedback. I think this can be achieved by communicating your goals and background to other users.

I think the goal of the other ticket is to increase reviewer participation by allowing a reviewer to communicate to Exercism that they are expert enough to review exercises without having done them.

While both involve communicating one's level of expertise, the targets are different and one can be accomplished without the other.

@kytrinyx
Copy link
Member

Yeah, that's a good observation.

@kytrinyx
Copy link
Member

kytrinyx commented Jun 5, 2016

Ref: #34

@stantoncbradley
Copy link

stantoncbradley commented Jun 10, 2016

I think this would go a long way for #2803 as well

@kytrinyx
Copy link
Member

This is being tracked as part of the nextercism redesign (see #113 and #154).

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

4 participants