Troubleshooting programming code is like

A segment of lights will go out, and you still have to check all through that module. And maybe it isn't one burnt out light, but the module itself is bad.

With Internment's that's the way it's always been.

Is it any wonder I stopped looking at Code to find problems?

I can remember a bank once where if you stood on the right leg when the wind was blowing the wrong way at 3.56 in the afternoon and entered the wrong digit you could bring the entire system down country wide. 300,000 lines of code to find the addition that had been added that caused this to happen only took several weeks to make certain that I had gone [b]COMPLETELY INSANE.[/b]

Honestly chasing Apprentices around with 14 inch long Phillips Screwdrivers to kill them with was just so much easier not to mention safer. You never tried to tear your hair out when the Apprentice who knew so much more than you did screwed things up yet again and added several hundred thousand $ and weeks to the [b]Absolutely Urgent[/b] repair. :0

Col

When i used to do some coding back in the days of old, i used to do 2000 lines of code, and you are correct, if you miss out one number, punctuation or letter (or many) then the program would not work but at least when you hit "run" it would flag up "Line error so or so". Many a times i have to slot in a question mark, letter or number depending on what was needed and then hit "run" again to test it out until it ran good and true, so yes it takes sometime to do, until someone buggers it up. :)

Hard at first but it gets easier as you learn and understand the basics.
Read, understand, learn and test (Rulat).