Reading 9: Avoiding Debugging

The topic of today’s class is debugging. More precisely, we’re going to look at ways to write code that either avoids debugging entirely, or at least makes it easy when we have to do it.

Reading 9: Avoiding Debugging Reading 9: Avoiding Debugging Software in 6.031 Safe from bugs Easy to understand Ready for change Correct today and correct in the unknown future. Communicating clearly with future programmers, including future you. Designed to accommodate change without rewriting. Objectives The topic of today’s class is debugging. More precisely, we’re going to look at ways to write code that either avoids debugging entirely, or at least makes it easy when we have to do it. First defense: make bugs impossible The best defense against bugs is to make them impossible by design. O

related reading

• Reading 9: Debuggingweb.mit.edu
• Reading 13: Debuggingweb.mit.edu
• Reading 16: Mutual Exclusionweb.mit.edu
• Reading 2: Testingweb.mit.edu
• TypeScript: Documentation - The Basicstypescriptlang.org
• Destroy All Values: Designing Deinitialization in Programming Languages - Faultloregankra.github.io
• Reading 4: Specificationsweb.mit.edu
• Reading 4: Code Reviewweb.mit.edu
• Reading 10: Abstract Data Typesweb.mit.edu
• Reading 3: Testingweb.mit.edu
• Reading 11: Recursive Data Typesweb.mit.edu
• Reading 6: Abstract Data Typesweb.mit.edu