You might conclude that these features are evidence of multiple authorship a good deal of revision which points itself to a kind of composite structure different layers maybe, different sources.

所以这些特点会让你认为有很多作者,很多次的修改,会让结构看起来世合并而成的,不同的层次，不同的素材。

耶鲁公开课 - 旧约导论课程节选

We'll talk more about this later, but it often happens that when you change your program to solve one problem you break it, and things that used to work don't work.

我们以后会更多的去讨论者一点，但是经常发生的情况是当你因为,一个问题修改你的程序的时候,你修改了程序,但原来没问题的模块。

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

That revisions may have been made, so that you might have different sources that have been revised or put together in different ways. Right?

这些修订，以便于你可以对,不同的素材，以不同方式，进行修改或者重组？

耶鲁公开课 - 旧约导论课程节选

So I hit control X. It's very unnecessarily arcanely saying save modified buffer, and then answering no will destroy changes.

敲入控制键X，它会很罗嗦地,问你是否保存所做的修改,如果回答为NO，就不保存修改过的部分。

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

All right. What do you do when you've found the bug and you need to fix it?

好了，当你发现错误并修改它们的时候,你该怎么做？记住一个古老的法则？

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

I will tell you that a good programmer, at least in my mind, may actually go back and modify the pseudo code as they realize they're missing things, but it's easier to do that when you're looking at a simple set of steps, than when you're in the middle of a pile of code.

至少我认为是这样的，如果他们发现遗漏了,一些步骤的话会,回过头去修改伪代码,但这当你面对一些大致的步骤时,这个过程就会比,面对一堆代码要简单的多。

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

Ask yourself, will it fix all of the symptoms you've seen?

你第一个想到的修改方案,它能否解决你看到的所有症状？如果不行？

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