I bought a rechargeable SCUBA light. When the charger burst into flames, I looked inside and found that someone replaced a 1A fuse with 12 Ga wire.
I complained to the seller and was told "it sucks to be me".
"At least when I buy something in a store and it doesn't go my way I can confront the store owner directly [usually get exchange/refund at that point;-)]."
How many times have you been ripped off on ebay? Do you actually know anyone who has?
It may have something to do with the kind of code that gets dumped on me, but most of the bugs I run into aren't insidous pointer over-runs and writes to free'd memory, they're logic errors and plain bad code.
The most useful tools I have are a roll of Scotch Tape(tm) and an assortment of highlighters.
The first task is to print out the thousand lines of code that should have been dozens of functions/classes/modules, tape it together and put it up on the wall.
Then I use the highlighters to mark the control blocks, and see why it's not working.
Until I can understand how the code runs on a macro level, it's useless to watch it with a debugger at a micro level.
While it's facinating to watch a counter run down to 0, it's not especially useful unless you know what it's counting, and why, and what's supposed to happen.
Slashdot Mirror
I bought a rechargeable SCUBA light. When the charger burst into flames, I looked inside and found that someone replaced a 1A fuse with 12 Ga wire.
;-)]."
I complained to the seller and was told "it sucks to be me".
"At least when I buy something in a store and it doesn't go my way I can confront the store owner directly [usually get exchange/refund at that point
How many times have you been ripped off on ebay? Do you actually know anyone who has?
It may have something to do with the kind of code that gets dumped on me, but most of the bugs I run into aren't insidous pointer over-runs and writes to free'd memory, they're logic errors and plain bad code.
The most useful tools I have are a roll of Scotch Tape(tm) and an assortment of highlighters.
The first task is to print out the thousand lines of code that should have been dozens of functions/classes/modules, tape it together and put it up on the wall.
Then I use the highlighters to mark the control blocks, and see why it's not working.
Until I can understand how the code runs on a macro level, it's useless to watch it with a debugger at a micro level.
While it's facinating to watch a counter run down to 0, it's not especially useful unless you know what it's counting, and why, and what's supposed to happen.