News for hackers. Stuff that matters.
Re:How to win the coding interview by hvidgaard on Tuesday May 31, 2016 @08:17AM (#11806083)
You can see my reply to the parent comment. I always sit down and talk with the students, but for us to talk about the code, we need to be able to read the code. Unneeded comments make it significantly harder to read code.

First time we talk about why I don't want "the what" comments, only "the why" comments. If they still do it in the next handin it's a fail unless they've explicitly provided me with a reasonable reason to do it.

Re:How to win the coding interview by tamana on Tuesday May 31, 2016 @11:00AM (#11806885)
In science, there is no such thing as why, there are only deeper levels of what. And those levels are subjective and relative to personal experience.

Your comment merits a failing mark, downvotes, because you made the same subjectively wrong statement twice.

Re:How to win the coding interview by hvidgaard on Wednesday June 01, 2016 @02:32AM (#11812438)
Programming is not a science. "Pad to multiple of 256 otherwise libX will fail" is exactly what a comment is for, and it is the "why", no the "what" - the what is already readable in the code.