Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That scenario happens so often as a programmer.

You could read the docs or find the right person to talk to but its just faster to poke the black box and watch it's behavior.

Aka the scientific method of debugging



I think this method skips step one.

1) You turn it off and then on.

2) You look at one that works.


Nobody ever taught me step 2, and I learned step 1 from the IT Crowd (ok, not really).

Seriously though: are there are any other steps that everyone knows?


There's always

* change stuff at random, look for observable differences




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: