Re: When my script doesn't work, I ...

[blue_cowdawg]

in reply to When my script doesn't work, I ...

There's a process for that:

1. Cuss like a sailor asking the Universe why the <BLEEP!> this thing ain't working??????
2. Smack monitor
3. Go for more coffee
4. Cuss some more
5. rerun the code and hope the problem isn't still there.
6. cuss more when the problem remanifests itself.
7. try blaming the input data.
8. go for more coffee
9. re-run code
10. Turn on script's built in debug logging
11. stare at terminal
12. Go to lunch
13. read debug output
14. Add more debug logging in strategic locations
15. Get Diet Mountain Dew from vending machine
16. rerun script
17. found bug, fix.
18. Go home

And the next day we start all over again!

[cavac]

Sound familiar.

Although lately, working with big databases and data files, more often enough the story ends more like "realize that the script does exactly the right thing, but $OTHERSCRIPT supplied broken data. (Junk in/Junk out principle)".