3 ms·
That explains how the deprecated "Power Peg" model was activated, but why was that model so flawed?
by tantalor 13y ago
That explains how the deprecated "Power Peg" model was activated, but why was that model so flawed?
- michaelt 13y agoYou may have heard people with things like backups and emergency generators saying "you have to test this stuff weekly, in case someone has broken it so it'll fail the moment you call on it." Software is the same. Knight had code that hadn't been run in 8 years. Sure, the code worked 8 years ago, but things have changed around it since then. As the problem code never ran, no-one noticed it getting broken, or had any reason to fix it if it broke in testing. Most likely the code worked fine 8 years ago, broke in the intervening 8 years, and hence was broken when activated.
- Pitarou 13y agoIf I understand this correctly, this isn't like having untested code around. It's more like leaving highly toxic medicine in the bathroom cabinet when you no longer need it, or leaving an electrically powered band saw plugged in when it's not in use.
- Dylan16807 13y agoThey roughly explained it. The counters were in a different state because of refactoring moving their updates around, so the Power Peg code had an incorrect view of reality.
- rurounijones 13y agoThere is a part of me that is strangely impressed that the code ran at all after 8 years of things changing around it. I would have expected it to just segfault or error out in some way.
- deleted 13y ago[deleted]