The funny thing is that I was so sensitized to this behavior that when I actually found a hardware bug in a chip, it took me forever to convince myself that the problem wasn't actually my code.
replyFinally contacted the manufacturer's rep, expecting to be called an idiot, only to find out that "yeah, we know about that bug. It's going to be fixed in the next revision."
The modern version of "It must be a compiler bug!"
replyUsing c++ templates wrong in the year 2000 exposed me to real compiler bugs in the Microsoft c++ compiler at the time, the kind that would make the compiler crash.
replyCompiler bugs are not as rare as they are quipped to be on forums. I mean, more rare for the quippers due to allocation of time.
replyI've actually identified a real compiler bug that led to a compiler fix. But then, a broken clock is right twice a day :).
replyI thought it was cosmic rays which always cause the bitflip when you least expect it.
replyThe modern version is "LLMs produce bad code"
replyLLMs aren't nearly mature or deterministic enough to earn that distinction. I've had an agent tell me it read a link I gave it, when actually it lied. I don't see how you could possibly compare that to a compiler where thinking "maybe it's a compiler bug" means you've almost certainly missed something.
replyReminds me of something that made me cringe that I heard from an architect at a medium sized IT shop, "even Google couldn't handle our scale".
reply