King Rat (gkr) wrote,
King Rat

October 2002 I.E.E.E. Computer

Debug rules to live by, kiped from Bob Colwell:

  • Change one thing at a time.. If you fix the problem, you won't know which thing fixed it.
  • Don't ignore the unexpected.
  • Follow the bug trail. I tell my developers, You get one chance with the shotgun. After that, no more guessing. Follow it systematically.
  • Reduce complex phenomena to simple absolutes. Isolate the problem. Strip out anything that's not affecting the system, and then debug only what's left.
  • Keep accurate lab notes.
  • Debug is an immersion activity. Don't allow distractions. If you are interrupted, you'll likely have to start over.
  • Bugs almost never live alone.
  • Test your test equipment.
  • Know when you're stick, and call in the cavalry. Simply getting another pair of eyes on a problem often removes your blinders. My rule of thumb for developers is, don't spend more than a half hour if you are stuck. And there are those who are good at debugging. Be nice to them, so you can ask for their help later.

Not much else interesting this issue.


  • Last post

    I don't plan to delete my LJ (I paid for permanent status, dammit), but this will be the last post. I don't plan to read it anymore, either…

  • The Fighting Lady

    The first image is a screenshot from The Fighting Lady at 6:55. The subject at that moment is the maintenance and operation of the ship's…

  • Operation Hailstorm

    Last summer my aunt requested the military file for my grandfather. It finally came through last month. I scanned all 600+ pages a couple weeks ago…

  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

  • 1 comment