It's an intermittent problem that resolves itself within 24 hours every four years. Which is longer than the tenure of most developers at any given company.
When described like that, it's really easy to see why that happens a lot: There's zero incentive for them to fix those issues.
Coworker summed it up yesterday: every leap day problem ends the same way the following day, "dev: can't reproduce".
@Itty53@carnage4life I will bet that for many of these bugs, there is a developer that cares, has root caused the problem, and has a fix.
I'm also willing to bet there's a manager somewhere that doesn't want to introduce the fix because of regulation required testing or some other "business" reason.
@Itty53@carnage4life I can actually understand the incentives for the companies not to bother fixing these bugs... is it worth spending the money to fix when it'll fix itself tomorrow?
But it does make me wonder if this shows a potential security vulnerability in their services? To get their service to crash and potentially run a malicious packet is now known...
For some industries it's imperative, sure, but a POS gas pump? Video game crashing? No one's gonna complain too hard, they'll just go somewhere else.
Vulnerabilities are built on this kind of laziness though, you're right. But the same rule applies to attackers. Why spend all your energy on a vuln that's only open 24 hours every four years? Target, timing, capacity for things to change in four years etc makes it unreasonable.
Add comment