3 ms·

It reminds me of my younger self when I encountered inexplicable behavior in my own software, “I think I found a bug in Firefox!” … “Oh, nope. I forgot to add a

It reminds me of my younger self when I encountered inexplicable behavior in my own software, “I think I found a bug in Firefox!” … “Oh, nope. I forgot to add an event handler.”

glimshe 5mo ago
The modern version of "It must be a compiler bug!"
- consp 5mo ago
  I thought it was cosmic rays which always cause the bitflip when you least expect it.
- bagels 5mo ago
  Using 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.
- admissionsguy 5mo ago
  The modern version is "LLMs produce bad code"
  - deltaburnt 5mo ago
    LLMs 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.
- genxy 5mo ago
  Compiler 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.
  - glimshe 5mo ago
    I've actually identified a real compiler bug that led to a compiler fix. But then, a broken clock is right twice a day :).
shagmin 5mo ago
Reminds 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".
HeyLaughingBoy 5mo ago
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. Finally 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."
eichin 5mo ago
We formalized that as "if you didn't find a kernel bug yesterday, you didn't find one today either" (while implicitly glaring at the java developer who kept blaming everything but his own code.) The funny thing is that we actually had one guy who found two kernel bugs (spread over a couple of years, but still) while hunting down weird product issues - we didn't think the kernel was perfect, just that "you need to have exhausted the possibilities in your code before considering blaming the kernel" was well supported by evidence...

It reminds me of my younger self when I encountered inexplicable behavior in my own software, “I think I found a bug in Firefox!” … “Oh, nope. I forgot to add an event handler.”

glimshe 5mo ago

The modern version of "It must be a compiler bug!"

consp 5mo ago
I thought it was cosmic rays which always cause the bitflip when you least expect it.
bagels 5mo ago
Using 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.
admissionsguy 5mo ago
The modern version is "LLMs produce bad code"
- deltaburnt 5mo ago
  LLMs 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.
genxy 5mo ago
Compiler 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.
- glimshe 5mo ago
  I've actually identified a real compiler bug that led to a compiler fix. But then, a broken clock is right twice a day :).

shagmin 5mo ago

Reminds 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".

HeyLaughingBoy 5mo ago

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. Finally 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."

eichin 5mo ago

We formalized that as "if you didn't find a kernel bug yesterday, you didn't find one today either" (while implicitly glaring at the java developer who kept blaming everything but his own code.) The funny thing is that we actually had one guy who found two kernel bugs (spread over a couple of years, but still) while hunting down weird product issues - we didn't think the kernel was perfect, just that "you need to have exhausted the possibilities in your code before considering blaming the kernel" was well supported by evidence...