3 ms·
Whenever a fellow programmer or myself starts even considering that the OS, .NET-Framework, JVM etc. might be responsible for a bug, I have to smile. In that m
by mduerksen 14y ago
Whenever a fellow programmer or myself starts even considering that the OS, .NET-Framework, JVM etc. might be responsible for a bug, I have to smile.
In that moment, 2 things are almost certainly true:
1. The bug is in your code.
2. You are too tired/stressed/overfocused to see it.
So when I find myself in this state, I instantly stop working and go for a walk (or go home when its late enough).
Then, when rested, I tackle the problem again. I will find my bug, or, for the very rare case, find a way to prove that it really is the environment my code runs in.
But most importantly, I will have a sharp tool for the job.
- dfox 14y agoI used to reason exactly like this, but then in last few months occurrences of this rare cases of bugs in OS, environment or even hardware started to be little to often. Although I might be biased by spending inordinate amounts of time on these bugs (like one day each). Various X11 related bugs (well, when X server crashes, you can be pretty sure that it is not bug in _your_ code), Windows driver bugs, Windows hotfixes fixing one bug and exacerbating impact of another bug from "minor annoyance" to "does not work", RTC chip with errata longer than datasheet, weird firmware<->kernel interactions, generally failing hardware and so on.