tautvidas

Gamozo focuses on security and optimization topics.

While his content is not structured as a tutorial, he explains his line of thinking very well.

https://www.youtube.com/user/gamozolabs/videos

https://www.twitch.tv/gamozo

The point is to break out of the startTimer() function call, e.g.:

    startTimer('');foo();//');

The remaining '); can be commented out in order to not create any syntax errors.

Adding a space just before the URL works just as well.

While I do agree to some extent that great code doesn't need any comments, it raises some questions. How can one be sure at the time of writing that the code is easy enough to understand for others? I'm sure that it's understandable for the author, who's been staring at it for a few hours, but will the same hold for a future maintainer?

I agree with other commentators that with comments one can at least express the intent and reasons for particular decisions.

And on a side note, it's wonderful to strive to write great code, but I believe it's easy to misjudge and think "Oh, I clearly write understandable code, thus I'll skip comments" even when it's not that clear. That certainly has happened to me, very likely to others at some point as well.

DB Class: http://db-class.org/ Machine Learning Class: http://www.ml-class.org/