mit 计算机科学及编程导论(11)
2012-07-28 14:12
411 查看
words:
fake , ambiguity , readily , physics , theoretical , subtlety , alias , pragmatic , quantum , supreme , validation , nail , unwarranted , weave , facilitate , feasible , relay , moth , trap , epiphany , laboratory , diagnosis , disabuse , crawl , breed
, mate , eliminate , be hung up about/on sth , stamp someone out , whack a mole , tray , cockroach , evolve , probe , subtle , skeptical , refute , flawed , intermediate , slip-up , prune , kneel , ascertain , integration
notes:
two topics : testing(testing & reasoning to check whether the testing is enough or not) & debugging(function & performance)
testing:
1. two ways of testing : unit testing & integration testing
2. test suit: small enough to test in reasonable time & large enough to give enough confidences that the problem is ok(how to trade off)
debugging :
1. goal : not to eliminate one bug but to move towards a bug-free program (so we need a debug
strategy)
2. what we should ask when we debug:
how could it have produce this result?
is it part of family?(一类错误)
how to fix it?
scientific method(我不是很了解,暂时不贴,但是这好像是他们高中教的如何做科学研究的方法)
ps:
how to use a debug strategy to write a bug-free program is very crucial , we must think "is it a family" when we ascertain a bug to eliminate a kind of bug(以前都是一个一个的解决,解决后就运行,不行再找下一个,这样看来还是不够系统systematic)
fake , ambiguity , readily , physics , theoretical , subtlety , alias , pragmatic , quantum , supreme , validation , nail , unwarranted , weave , facilitate , feasible , relay , moth , trap , epiphany , laboratory , diagnosis , disabuse , crawl , breed
, mate , eliminate , be hung up about/on sth , stamp someone out , whack a mole , tray , cockroach , evolve , probe , subtle , skeptical , refute , flawed , intermediate , slip-up , prune , kneel , ascertain , integration
notes:
two topics : testing(testing & reasoning to check whether the testing is enough or not) & debugging(function & performance)
testing:
1. two ways of testing : unit testing & integration testing
2. test suit: small enough to test in reasonable time & large enough to give enough confidences that the problem is ok(how to trade off)
debugging :
1. goal : not to eliminate one bug but to move towards a bug-free program (so we need a debug
strategy)
2. what we should ask when we debug:
how could it have produce this result?
is it part of family?(一类错误)
how to fix it?
scientific method(我不是很了解,暂时不贴,但是这好像是他们高中教的如何做科学研究的方法)
ps:
how to use a debug strategy to write a bug-free program is very crucial , we must think "is it a family" when we ascertain a bug to eliminate a kind of bug(以前都是一个一个的解决,解决后就运行,不行再找下一个,这样看来还是不够系统systematic)
相关文章推荐
- mit 计算机科学及编程导论(9)
- mit 计算机科学及编程导论(6)
- mit 计算机科学及编程导论(2)
- mit 计算机科学及编程导论(7)
- mit 计算机科学及编程导论(1)
- 计算机科学与编程导论小习题-MIT
- mit 计算机科学及编程导论(14,15,16)
- MIT公开课---计算机科学及编程导论
- mit 计算机科学及编程导论(17,18,19)
- mit 计算机科学及编程导论(12)
- mit 计算机科学及编程导论(13)
- mit 计算机科学及编程导论(1)
- mit 计算机科学及编程导论(10)
- 学习日记-MIT[计算机科学与编程导论]-7,8
- MIT 6.00.1x 计算机科学和Python编程导论 Set 2
- 笔记:udacity计算机科学导论- 课程11/19 python取幂, DRAM 存储原理、容量、速度
- MIT 6.00.01X 计算机科学和Python编程导论 bolg参考整理
- MIT 6.00.1x 计算机科学和Python编程导论 Set 1
- 计算机科学与Python编程导论_MIT 学习笔记(二)
- 计算机科学和编程导论-week3-递归