>I would have thought it patently obvious that debugging a program is
>directly analogous to scientific experimentation:
1. Create an hypothesis about the bug
2. Design a data/test framework in which to extract information
3. Execute constructed test and obtain data
4. Relate new data to hypothesis to create information (or not)
5. Decide whether bug is fixed
6. Goto 1 if necessary.
Yes it may be obvious, but as you explained, not to everyone.
And there is a lot of subtlety involved in scientific research
which is not at all obvious and which is not on your list.
PC
>
>====================================================================
>Dr Russel Winder Chief Technology Officer
>OneEighty Software Ltd Tel: +44 20 8680 8712
>Cygnet House Fax: +44 20 8680 8453
>12-14 Sydenham Road [EMAIL PROTECTED]
>Croydon, Surrey CR9 2ET, UK http://www.180sw.com
>====================================================================
>Under the Regulation of Investigatory Powers (RIP) Act 2000 together
>with any and all Regulations in force pursuant to the Act One Eighty
>Software Ltd reserves the right to monitor any or all incoming or
>outgoing communications as provided for under the Act
>
>Content-Type: application/pgp-signature; name=signature.asc
>Content-Description: This is a digitally signed message part
>
>Attachment converted: Polly HD:signature.asc (????/----) (000A466F)
- Automatic footer for [EMAIL PROTECTED] ----------------------------------
To unsubscribe from this list, mail [EMAIL PROTECTED] unsubscribe discuss
To join the announcements list, mail [EMAIL PROTECTED] subscribe announce
To receive a help file, mail [EMAIL PROTECTED] help
This list is archived at http://www.mail-archive.com/discuss%40ppig.org/
If you have any problems or questions, please mail [EMAIL PROTECTED]
