Principles of debugging

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

cojak replied

4 December 2013, 15:49
Originally posted by d000hg View Post

It bloody well isn't me, how rude.

It may well be, doohgie.... (sigh)
Leave a comment:
d000hg replied

4 December 2013, 15:46
Originally posted by cojak View Post

It may well be doohgie, I'll keep an eye on him...

It bloody well isn't me, how rude.
Leave a comment:
cojak replied

4 December 2013, 15:40
Originally posted by d000hg View Post

Bot?

It may well be doohgie, I'll keep an eye on him...
Leave a comment:
russell replied

4 December 2013, 15:23
Ceteris paribus
Leave a comment:
d000hg replied

4 December 2013, 14:32
Bot?
Leave a comment:
Cowboydave started a topic Principles of debugging

4 December 2013, 14:31
Principles of debugging

I just wanted to reach out to you guys, with what I have learned about debugging complex systems.

Debugging systematically is about simplifying the problem to the smallest possible number of moving parts, without masking the problem. So if there are three moving parts I lock down two of them (part A, part B) with a snapshot of their dynamic states (*) and then I observe the behaviour of the third (part C). If that is correct, then I rotate the test through to the next part, locking down part A and part C and observing part B.

This is otherwise known as a "process of elimination". This works for electronics, software, interpersonal issues in teams

(*) you must lock the moving parts down in a valid state to keep the debugging scenario realistic.
Tags: None