Return to Video

The Devils Guide to Debugging - Software Debugging

  • 0:00 - 0:05
    All of these strategies come from a chapter named "The Devil's Guide To Debugging,"
  • 0:05 - 0:09
    which was written by a guy named Steve McConnell.
  • 0:09 - 0:16
    The book is being called Code Complete in 1993 and it encompass all the wisdom
  • 0:16 - 0:19
    about programming that Steve McConnell had at that time.
  • 0:19 - 0:23
    What we've seen so far is just three of these rules.
  • 0:23 - 0:28
    The first one is to scatter output statements everywhere in the code.
  • 0:28 - 0:33
    Output whatever you want, where you want it, just put it in there such that
  • 0:33 - 0:37
    you will always be able to figure out what was going on or not.
  • 0:37 - 0:41
    The second one is to debug the program into existence.
  • 0:41 - 0:46
    Just keep on adding statements and removing statements until it works.
  • 0:46 - 0:49
    Never ever backup earlier versions of your code.
  • 0:49 - 0:54
    I mean who can't remember what he or she has done just 7 minutes ago.
  • 0:54 - 0:59
    Rule number 4, don't bother understanding what the program should do.
  • 0:59 - 1:04
    I mean, it's obvious isn't it. If it's not obvious, make it obvious.
  • 1:04 - 1:11
    My all time favorite though is number 5, use the most obvious fix.
  • 1:11 -
    That means fix the symptom instead of the problem.
Title:
The Devils Guide to Debugging - Software Debugging
Video Language:
English
Team:
Udacity
Project:
CS259 - Software Debugging
Duration:
01:16

English subtitles

Revisions Compare revisions