Reading 13: Debugging
Sometimes you have no choice but to debug – particularly when the bug is found only when you plug the whole system together, or reported by a user after the system is deployed, in which case it may be hard to localize it to a particular module. For those situations, we can suggest a systematic strategy for more effective debugging.
Reading 13: Debugging Reading 13: 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 systematic debugging. Sometimes you have no choice but to debug – particularly when the bug is found only when you plug the whole system together, or reported by a user after the system is deployed, in which case it may be hard to localize it to a particular module. For those s
related reading
- Reading 9: Debuggingweb.mit.edu
- Reading 9: Avoiding Debuggingweb.mit.edu
- Debugging Reinforcement Learning Systemsandyljones.com
- Computers can be understood - Made of Bugsblog.nelhage.com
- The Debugger's Toolkit - by Addy Osmani - Elevateaddyo.substack.com
- CSC 151 - Hypothesis-driven debuggingeikmeier.sites.grinnell.edu
- Reading 2: Testingweb.mit.edu
- Some ways to get better at debuggingjvns.ca
- An Exploratory Study of Debugging Episodesarxiv.org
- Software Engineering at Googleabseil.io
- CS106B Backtracking Warmupweb.stanford.edu
- How to read a codeiamjonas.me