If you can read the code a year later, even code you wrote yourself, it's a good sign that you put good comments in, right?

如果你还能读懂1年前的代码，就算是你自己写的代码，这也说明了你放进去的注释,已经非常好了，对不对？

麻省理工公开课 - 计算机科学及编程导论课程节选

Give you some examples. What have we talked about? We've talked about things like using comments to highlight what you're doing in the code, to make it easier to debug.

给大家举些例子,我们一直在强调什么来着？,我们讲过要用注释来说明,你在代码中进行的操作，以便于调试。

麻省理工公开课 - 计算机科学及编程导论课程节选

Because as you'll soon find, when you're writing programs 0 that aren't just four lines long but are 40 or 400 which very quickly becomes easy, you'll find that even you the next morning have no idea what this code does for whatever reason, and just having some English comments is a huge boon to comprehension for yourself and others.

你们自己写程序时就会发现,用40行甚至400行代码来代替繁杂拥挤的4行代码0,将会让事情简化许多，你会发现，即使由于某些原因,你不知道如何写代码，先写些注释，于人于己，都是好事,易于理解嘛。

哈佛公开课 - 计算机科学课程节选

This also, by the way, in some sense, gives me the beginnings of my comments for what the structure of my code is going to be.

顺便说一句，在某种意义上这也是我,对于我的代码结构的,讲解的开始。

麻省理工公开课 - 计算机科学及编程导论课程节选

So let's take a look then at somewhere where this is actually a useful thing to know so this is compare1.c. So, in compare1.c I've stripped out the comments in my version but in your version you do have comments for reference and it's actually pretty self-explanatory if you just read through the code.

那么再然我们看一看,一些有用的东西,这是compare1。c，所以在compare1。c中，在我的版本中,我吧注释去掉了,但是在你们的版本中是有注释的,这是相当容易理解的,如果你通读这段代码。

哈佛公开课 - 计算机科学课程节选