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
Explore this link on the map →related reading
- Reading 9: Debuggingweb.mit.edu
- Reading 13: Debuggingweb.mit.edu
- Everything is Fertilenickcammarata.com
- Reading 4: Code Reviewweb.mit.edu
- Reading 1: Static Checkingweb.mit.edu
- Reading 1: Static Checkingweb.mit.edu
- CSC 151 - Hypothesis-driven debuggingeikmeier.sites.grinnell.edu
- Transcript – Debugging: Techniques for Uncertain Times – Chelsea Troychelseatroy.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- The Debugger's Toolkit - by Addy Osmani - Elevateaddyo.substack.com
- Reading 3: Testingweb.mit.edu
- Your Debugger Sucksrobert.ocallahan.org