3 ms·
Yes. It's very similar to when you encounter compiler or operating system or hardware bug as a programmer. You are trained for years to NEVER BLAME THE LOWER L
by ajuc 5y ago
Yes. It's very similar to when you encounter compiler or operating system or hardware bug as a programmer.
You are trained for years to NEVER BLAME THE LOWER LAYERS because that makes you a worse programmer. So when it is actually their fault - you might look stupid for exhausting every other possibility before checking these basic assumptions.
But this is still a good rule, because it breaks very rarely.
- Retric 5y agoReminds me of the utter hell it was to discover the test machine had bad RAM.
- ajuc 5y agoI've had a bug in linux driver for a very shitty touchscreen we used in our embedded devices. It needed manual calibration and you had to save the calibration matrix in a config file read on system startup. They used locale-aware input function in a driver so when the locale was German (or other with "," as a decimal separator) it broke and users got kernel panic at startup :) It bricked all our devices in Germany. We worked around it, notified the device driver developers and forgot about it. A year later we shipped with new version of kernel and it broke again - because the bug was fixed in kernel and our workaround was now causing the bug :)
- hinkley 5y agoThis is part of what drove people to CI/CD. If your code is broken in the morning and the build is green, it’s probably you. If it’s red, maybe you should check other things sooner?