But here, if I decide I'm going to store things not in x and y, but with some other set of names, for example, I've gotta go back into these pieces of code that use the points, and change them. So I've lost modularity.

除了要改下借口,但是这里，如果我决定，我不把值放在x和y中，而是和其他一些变量名进行绑定,例如这样的话,我就得回到使用这个点的代码，那儿去做更改了。

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

Last year for the pieces that do vary year to year a bit, last year's first problem set challenged students to write their first or maybe second or third program using this environment called Scratch.

去年的教材有些地方有略微改动，去年的第一个问题集是让学生,在Scratch环境下,写下自己的第一或第二个或第三个程序。

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

And odds are if a week hence, two weeks hence just for fun you decide to reimplement your Scratch project -- or some tiny piece of it, it wouldn't be surprising -- or shouldn't be -- if you end of implementing the same game or animation or whatever using a completely different set of puzzle pieces Same deal we'd see here.

可能一周之后，两周之后，为了好玩,你决定重新实现你的Scrtch工程,或者其中一小部分，它将不会是令人惊讶的-,本来也不应该是--如果你运行相同的游戏,或者是动画，亦或是用完全不同的设置,来运行拼图游戏,我们将看到相同的处理。

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