Re:Sometimes the bug isn't in your code, it's in the CPU
by sparsevector on Monday March 05, 2012 @06:58PM
(#3669045)
I think what VBprogrammer meant is that thinking you've found a bug in a compiler / OS / CPU is often a warning sign you're a poor programmer. Often times a beginner will have a bug in their code that is too subtle for them to identify, so they end up attributing it to some external factor. Actually finding a bug in a compiler / OS / CPU is as you suggest likely a sign you're doing something advanced or unusual and therefore are perhaps more knowledgeable than most.
[ Parent
| on HN ]
Re:Sometimes the bug isn't in your code, it's in the CPU
by VBprogrammer on Monday March 05, 2012 @08:34PM
(#3669262)
Yeah, that's exactly what I meant. Sorry if the sarcasm didn't quite carry.
I know these things can and do happen. I've come across one or two of these strange ones before, but too often I've seen people jump to the conclusion that someone / something else was to blame. Without any other real evidence other than that they have exhausted their shallow back of talent.
Re:Sometimes the bug isn't in your code, it's in the CPU
by arethuza on Tuesday March 06, 2012 @04:27AM
(#3670274)
I think that's often called the "select isn't broken" rule:
http://pragprog.com/the-pragmatic-programmer/extracts/tips
However, I did once work with someone who did find a bug in select on SunOS... (this was '89 or so).