So when it says to comment your code..?

[xhoneyskye]

Am I supposed to comment every single line explaining what it does? Major portion of my code repeats the same thing over and over again.

[Fubarable]

Am I supposed to comment every single line explaining what it does?

No, most definitely not. Your goal should be to write code that is "self-commenting" where the variable and method names are so logical that they almost make it obvious what is going on. You should comment most methods, especially public ones, anything that may be confusing, and anything that your instructor says should be commented.

Major portion of my code repeats the same thing over and over again.

That sounds like code that should be refactored then. You might want to place the repeating bits into a method and then use loops as needed.

[ecliptical]

What Fubarable is on point, but if actual commenting

//comment goes here

is needed, then I'd suggest block commenting.. At the head of every code which is similar, have a comment saying what the function of that block of code does.

[xhoneyskye]

No, most definitely not. Your goal should be to write code that is "self-commenting" where the variable and method names are so logical that they almost make it obvious what is going on. You should comment most methods, especially public ones, anything that may be confusing, and anything that your instructor says should be commented.

That sounds like code that should be refactored then. You might want to place the repeating bits into a method and then use loops as needed.

Thanks. Informative, but I still refuse to use loops. I suck at it. Majorly.

:)

[xhoneyskye]

What Fubarable is on point, but if actual commenting

//comment goes here

is needed, then I'd suggest block commenting.. At the head of every code which is similar, have a comment saying what the function of that block of code does.

Oh, okay. That makes sense, thank you.

[[RaIdEn]]

if it may help

//comment 1

non-javadoc comments

/*
*/

javadoc comments

/**
*/

[Tolls]

I have a tendency to comment as part of the design (which goes back to the days when I had to do sequence diagrams). So a key method would look something like this before I even added any code to it:

public void processSomething() {
    // First get the data.
    // loop over it.
        // call the thing.
        // call the other thing.
    // finally send data somewhere else.
}

The advantage (in my mind) is that you can see to turn each of those comments (bar the loop) into a call to another method, thus breakig up the work done by a single method, and you've also commented your thought processes which led you to write this in the way you have. I'm a firm believer on writing comments based on the fact the reader is going to be a bit thick...even that reader is going to be you in a few weeks time.