Skip to content

Conversation

@Platika
Copy link

@Platika Platika commented Mar 21, 2012

Our group went through an added line comments for each of the solution files to the problems. We thought that this would help people who looked at the solution files understand what was going on through each step, and make the solutions more beneficial for somebody who is having a hard time understanding what is going on.

Platika and others added 8 commits March 14, 2012 15:27
Standardized grammar in DieRoll solution
Fixed a few grammar and spelling mistakes in comments, formatted
comments to be in keeping with the rest of the code (line breaks and
extra, empty comment lines).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you might want to be clearer here, since it's a little ambiguous whether you're checking the equality or asserting it. What I think you mean is that this line sets the variable num to be equal to the value returned by rollDie(). Just make sure you're explicit. Compare:

// *checks* whether num is equal to the value of rollDie()
num == rollDie();

to

// sets num equal to the value of rollDie()
num = rollDie();

@WilDoane
Copy link
Owner

Can you edit your comments so that that do NOT restate implementation details (e.g., "uses parseInt", "sets the variable authorsName", etc), but instead focus on explaining the meaning of the code.

In other words, tell me what the code means .... not what it does ... because the code itself tells me what it does.

Platika and others added 4 commits March 21, 2012 15:04
@WilDoane
Copy link
Owner

WilDoane commented Apr 8, 2012

Has there been any progress on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants