| ▲ | lukan 4 days ago |
| Rowhammer, cosmic bitflip or hardware or just compiler bugs come to mind. |
|
| ▲ | kqr 3 days ago | parent | next [-] |
| The first three are hardware failures, not software failures. The latter would be a design error, not a failure. The software may need to handle hardware failures, but software that doesn't do that also doesn't fail -- it's inadequately designed. |
|
| ▲ | teddyh 4 days ago | parent | prev [-] |
| None of those are something that you as a programmer should ever worry about. |
| |
| ▲ | BoppreH 4 days ago | parent | next [-] | | Counterpoint, I have definitely taken them into consideration when designing my backup script. It's the reason why I hash my files before transferring, after transferring, and at periodic intervals. And if you're designing a Hardware Security Module, as another example, I hope that you've taken at least rowhammer into consideration. | |
| ▲ | AlotOfReading 4 days ago | parent | prev [-] | | I consider these all the time as a programmer. Particularly compiler/toolchain bugs, which are relatively common once you start looking for them. |
|