Skip to content

Commit 545e588

Browse files
Add representer feedback document (#385)
1 parent 8991aa2 commit 545e588

File tree

3 files changed

+29
-0
lines changed

3 files changed

+29
-0
lines changed

mentoring/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,5 @@ Welcome to the Exercism Mentoring Team. Follow the links below for guides on how
44

55
- [Choosing a Solution](/docs/mentoring/choosing-a-solution)
66
- [How to give great feedback](/docs/mentoring/how-to-give-great-feedback)
7+
- [How to give feedback on representations](/docs/mentoring/how-to-give-feedback-on-representations)
78
- [How to use Markdown in mentoring](/docs/mentoring/markdown)

mentoring/config.json

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,14 @@
2323
"title": "How to give great feedback",
2424
"blurb": "You've chosen an exercise to mentor - now give some great feedback."
2525
},
26+
{
27+
"uuid": "80d6d993-ccf8-433f-af03-44b171328470",
28+
"section": "mentoring",
29+
"slug": "how-to-give-feedback-on-representations",
30+
"path": "mentoring/how_to_give_feedback_on_representations.md",
31+
"title": "How to give feedback on representations",
32+
"blurb": "Considerations for giving feedback on representations."
33+
},
2634
{
2735
"uuid": "57f323a6-29ea-43ef-9936-af44162ccc64",
2836
"section": "mentoring",
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# How to give feedback on representations
2+
3+
Giving feedback on a representation is different from giving feedback on a single solution.
4+
5+
## Representation feedback applies to multiple solutions
6+
7+
The key thing with representation feedback is that they apply to _multiple_ solutions.
8+
Anything that the representer normalizes should not be commented on, as you have no way of knowing what the original syntax was for a particular solution.
9+
10+
As an example, many representers normalize a solution's white space.
11+
Therefore, even though the solution shown in the representation feedback UI might have formatting issues, you shouldn't comment on it as other solutions with the same representation might not have those formatting issues.
12+
13+
Another example is naming of variables, functions, methods or classes.
14+
As representers could normalize identifier names, you shouldn't comment on them.
15+
Even if your representer currently does _not_ normalize identifier names, you still should not comment on it, as this is a normalization likely to be added to a representer later.
16+
17+
## Don't duplicate analyzer comments
18+
19+
As students will get to see both representer _and_ analyzer comments, make sure that you don't duplicate comments.
20+
To help with this, the analyzer comments are shown on the representation feedback page.

0 commit comments

Comments
 (0)