3 ms·
Have you encountered a hardware defect yet? If/when you do, it represents a lot of technically dead time that was spent looking at code. I'm not saying either p
by Quarrelsome 15y ago
Have you encountered a hardware defect yet?
If/when you do, it represents a lot of technically dead time that was spent looking at code. I'm not saying either premise is right but I can appreciate his philosophy here.
For the record, I killed four weeks digging through code and running tests and it turned out that temperatures in winter coupled with some bad soldering was the cause of the issue. D:
- JoeAltmaier 15y agoYes, you have to track them down, yes it takes forever for the hard ones. But most of the time it Isn't hardware, most of the time it my own bug and I can fix it. It definitely takes some experience to be good at debugging. I guess that's why all the emphasis on development environments these days, where the hard stuff is being debugged by someone else and I can work on my app-level stuff in peace.
- wccrawford 15y agoI have definitely encountered bugs that I could not track down, which very well might have been a hardware problem. I was eventually forced to give up on it. (And I've gotten better at giving up earlier when something is going to be impossible to find.) But I have never said, 'I won't look into a bug until multiple people have it.'